DJF Posted January 1, 2005 Posted January 1, 2005 First of all, this appears to be a great package. I found the default installation worked very well without any modifications, but in reading the INSTALL text file that came with the zipped package it states, that for security protection of the Admin panel, users should: "Do the same for the 'admin' directory but rename the directory to a unique and secret name. This directory does not have to reside inside the catalog directory, though may need to be manually configured." I have tried several times to rename the "admin" folder to my secret name, but have not been able to successfully connect to the Admin Panel afterwards. I have changed the folder name within Dreamweaver (where it updates all links to the new name) then I have manually edited every instance in every file where the default admin folder gets called (and replaced it with the new folder name) but still no success. Until I get this resolved I cannot proceed with any further setup, as security is one of my main concerns. Any suggestions? I'm all ears... Thanks.
TCwho Posted January 1, 2005 Posted January 1, 2005 after you change the name of the admin folder.... you have to update the new settings in your configure.php file there are two configure.php files, but I believe only the one originally in catalog/admin/includes/configure.php needs to be updated and then your good to go :P Drop_Shadow How Did You Hear About Us Email HTML Order Link ---- GMT -5:00
DJF Posted January 1, 2005 Author Posted January 1, 2005 after you change the name of the admin folder.... you have to update the new settings in your configure.php file there are two configure.php files, but I believe only the one originally in catalog/admin/includes/configure.php needs to be updated and then your good to go :P <{POST_SNAPBACK}> OK, Thanks for the reply, but I have already modified "catalog/admin/includes/configure.php" on line 21 to read: define('DIR_WS_ADMIN', '/admin*/'); (where * is my secret name) When I try to view the admin index page I get this: Warning: main(../../admin*/includes/configure.php): failed to open stream: No such file or directory in /home/content/html/catalog/admin*/includes/application_top.php on line 29 Warning: main(../../admin*/includes/configure.php): failed to open stream: No such file or directory in /home/content/html/catalog/admin*/includes/application_top.php on line 29 Fatal error: main(): Failed opening required '../../admin*/includes/configure.php' (include_path='.:/usr/local/lib/php') in /home/content/html/catalog/admin*/includes/application_top.php on line 29 The funny thing is that the configure.php file exists at this path location, modified as I have indicated. The application_top.php file has also been modified on line 29
TCwho Posted January 1, 2005 Posted January 1, 2005 should be /catalog/*yournewfoldername/ Drop_Shadow How Did You Hear About Us Email HTML Order Link ---- GMT -5:00
Guest Posted January 1, 2005 Posted January 1, 2005 OK, Thanks for the reply, but I have already modified "catalog/admin/includes/configure.php" on line 21 to read: define('DIR_WS_ADMIN', '/admin*/'); (where * is my secret name) When I try to view the admin index page I get this: Warning: main(../../admin*/includes/configure.php): failed to open stream: No such file or directory in /home/content/html/catalog/admin*/includes/application_top.php on line 29 Warning: main(../../admin*/includes/configure.php): failed to open stream: No such file or directory in /home/content/html/catalog/admin*/includes/application_top.php on line 29 Fatal error: main(): Failed opening required '../../admin*/includes/configure.php' (include_path='.:/usr/local/lib/php') in /home/content/html/catalog/admin*/includes/application_top.php on line 29 The funny thing is that the configure.php file exists at this path location, modified as I have indicated. The application_top.php file has also been modified on line 29 <{POST_SNAPBACK}> I just went through a similar exercise with two of my sites this morning (using Dreamweaver). It seems that, at least when I did it, the updated links all ended up with an extra "../" and an extra "includes/" in them. Also, make sure your configure file is set to the proper permissions so Dreamweaver can update it, or, better yet, update it using your Control Panel. If it's set to something like 444, it is not going to update. And don't forget to hit refresh.
DJF Posted January 2, 2005 Author Posted January 2, 2005 I just went through a similar exercise with two of my sites this morning (using Dreamweaver). It seems that, at least when I did it, the updated links all ended up with an extra "../" and an extra "includes/" in them. Also, make sure your configure file is set to the proper permissions so Dreamweaver can update it, or, better yet, update it using your Control Panel. If it's set to something like 444, it is not going to update. And don't forget to hit refresh. <{POST_SNAPBACK}> I also noticed the extra "../" and "/includes/" items. I removed the "includes/" but not the "../" Did you remove both and did it help? Do you think Dreamweaver did that? I set the permissions on the server based files to 777but it made no difference.
DJF Posted January 2, 2005 Author Posted January 2, 2005 I also noticed the extra "../" and "/includes/" items. I removed the "includes/" but not the "../" Did you remove both and did it help?Do you think Dreamweaver did that? I set the permissions on the server based files to 777but it made no difference. <{POST_SNAPBACK}> I went back and removed the extra "../" items in the application_top.php file and got a bit closer to being where I wanted to be. The errors I was getting went away but then got a "cant connect to mysql database" error. So I went into admin/includes/configure.php and realized that my mysql parameters were not there. I added them and now I am successfully running the Admin panel within my "secret" folder name, giving me the level of security I was hoping for. Thanks to everyone who responded, you helped me through it.
Guest Posted January 2, 2005 Posted January 2, 2005 I also noticed the extra "../" and "/includes/" items. I removed the "includes/" but not the "../" Did you remove both and did it help?Do you think Dreamweaver did that? I set the permissions on the server based files to 777but it made no difference. <{POST_SNAPBACK}> I see you figured it out, but to respond, yes, I think DW did that (I sure didn't). BTW, after I update the configure files, I set permissions back to 444.
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.