Hello All,

I have a component that I have created that is a very simple catalogue change log that lets people know what changes have been made to our printed catalogue.

I have made everything 'Public' but every time someone clicks on the link, the site tells them that they need to Authenticate via username and password. If you click cancel or log in (we actually have registrations turned off) it takes you to the page anyway, which is good, but people are being put off by this.

I am using Akeeba Admin Tools which I suspect may contribute to this, but I don't know for sure, or how to fix it.

Can anyone help me with this?

Many thanks,
Will

Have you tried the options button under your component? You should be able to set the access rules there.

Do you have a 'Joomla Access' Field in your Table ? (just for info)
Since 3.2 I always add this field in all Tables to be able to manage View Access Level. I used to prefill default, set to 1 (public).
Normaly, the Fronted Layout view should not ask for login...

Hi liubov,

You may be right, I have not used the 'Joomla Access' field in any of my components, this is kinda my first real component deployment, so I didn't think to use this feature.

I will admit I have limited understanding of this side of things, I will give it a go and let you know.

Cheers

I'm back with bad news, nothing worked for me regarding this issue, it actually got worse and broke the component.
I guess this why I have never used the 'Joomla access' wizards etc before, because there is no documentation of what they do, or how to make them work properly.
I am very disappointed as this component couldn't get any easier, and it doesn't work properly.

Does it work in a fresh Joomla install (without akeeba) ?
I think everything works properly in Cook.
It is just a metter of knowing how to use it.
For the docs, I know it is missing, but it is coming.

Hi Chef/Cooks,

After a long period of time I have revisited this problem I am having with J-Cook created components and this is what I have discovered.

To recap, the problem I am having is after I create a J-Cook component and install it etc, I try to access the information via the front end, I get an 'Authentication' pop up. This is caused as a result of password protecting the administrator section of our website via Akeeba Admin Tools.

This issue persists until I turn off part of our security, which is not preferable. So I searched the Admin Tools support area and I found this:

'You have protected the contents of your /administrator folder with a user ID and password. Any time a file is called from within the /administrator folder, the password is required. You have another extension which is improperly calling a back end file from the front of your site. You need to contact the author of that extension and advise them to correct this error. Until the error in the third party software is fixed, the only thing you can do is disable the /administrator password protection.'

This 'Authentication' pop up happens on ALL the components I create via J-Cook builder, even very simple components, and it is extremely disconcerting to our users/customers.

I don't understand what could be 'calling' the administrator section files/folders of our website, as I have done nothing that unusual, and I have never had this problem happen with any other Joomla! component ever.

Can anyone shed some light on this very old, ongoing problem? As I do not want to turn off security so that I can keep using J-Cook

Cheers

Hello Maheto
Very simple things are called from the frontend in the admin part.
For example, the form fields found in :
/Administrator/components/com_yourcomponent/models/fields
and this is just an example. since several files of the admin part are used from the frontend like that, lot of classes located in the administrator folder.
You do not trust the components you install . joomla?
You should at least trust the components created on Jcook and leave an exeption for your Jcook components

This is because most of all MVC classes inherit of superclasses located in the administrator folder.
If you want to avoid that, simply move these classes and helpers to the front end folder, just make sure they are properly loaded in the JLoader class of your component.
It is the way Cook is generating the files. It is probably a good question, but my convention is to have the lightest part on the front end (less files possible)