09-08-2018, 05:50 PM
Hi. Thank you for your prompt reply. Yes, it does make sense. I had assumed that but the existence of an index.php file in the folder threw me off. I moved the "users," "usersc" and z_us_root.php to the root.
I reverted the z_us_root.php back to its original state. I logged in and out of the admin. I added the directories back to the z_us_root file without the ../ in front of the path. I still got errors when I included folders like /css/ and /icons/. Then it hit me. They didn't contain any php pages to protect. So the PHP error about not finding a row made sense, since there were no db rows for pages that did not exist.
I had assumed US could protect directories as well, which was dumb of me. That's what .htaccess is for.
It looks ok, at least as far as pages goes. But do you think I should delete everything and reinstall in case there are problems down the line? Or is the z_us_root.php the config file and all else is good?
Thanks.
Have a great day,
Ric
I reverted the z_us_root.php back to its original state. I logged in and out of the admin. I added the directories back to the z_us_root file without the ../ in front of the path. I still got errors when I included folders like /css/ and /icons/. Then it hit me. They didn't contain any php pages to protect. So the PHP error about not finding a row made sense, since there were no db rows for pages that did not exist.
I had assumed US could protect directories as well, which was dumb of me. That's what .htaccess is for.
It looks ok, at least as far as pages goes. But do you think I should delete everything and reinstall in case there are problems down the line? Or is the z_us_root.php the config file and all else is good?
Thanks.
Have a great day,
Ric