The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I have copied the site to a directory which does not have basic auth. However, when I load the page, it loads fully and then gives a basic auth. If you cancel nothing happens. If you select menus, you get the basic auth, but if you cancel nothing happens.
Is there a firefox addon you can use to load a page step by step with each file being listed, so that I can trap this basic auth? I tried firebug but didnt get far.
Neil
EDIT: Found the culprit. I have a beta directory which has a .htaccess protecting it, *but* that .htaccess is protecting a different directory one level *up*.
This shouldn't be possible. What's going on?
I tried to export and import the db but was thrown out by the size limit, so I backed up the site and the restore allowed me to select a new db, which worked (after a bit of fiddling about).
N.
I didn't know how to do that with Firebug.
EDIT: I have reconfigured the preview version main configs to point to Preview (which is what was confusing me).
Now the only thing is, *thinking aloud* how do I get Joomlawatch not to point to beta as there are no path config settings for Joomlawatch? Possible answer would be to reinstall JW, but they still both point to the same database (intentional).
As you have made a copy of the Joomla install that was in you beta directory then a lot of paths will lead to that. Perhaps you need to tweek the Joomla config in the new directory.
I have copied the site to a directory which does not have basic auth. However, when I load the page, it loads fully and then gives a basic auth. If you cancel nothing happens. If you select menus, you get the basic auth, but if you cancel nothing happens.
Is there a firefox addon you can use to load a page step by step with each file being listed, so that I can trap this basic auth? I tried firebug but didnt get far.
Neil
EDIT: Found the culprit. I have a beta directory which has a .htaccess protecting it, *but* that .htaccess is protecting a different directory one level *up*.
This shouldn't be possible. What's going on?