Installing cmsb along sige wordpress
2 posts by 2 authors in: Forums > CMS Builder
Last Post: February 3, 2012 (RSS)
By markr - February 3, 2012
I don't know enough about wordpress to answer this...
I am redesigning a site currently using wordpress, When finished I will dump wordpress, but I want to keep the old wordpress site going while i develop the cmsb on the same server.
Have uploaded cmsb but can't see /cmsAdmin/admin.php with browser...404 Not Found.
Admin.php is there, I can access it via the control panel.
Can I run these content managers in parallel for a while?
I am redesigning a site currently using wordpress, When finished I will dump wordpress, but I want to keep the old wordpress site going while i develop the cmsb on the same server.
Have uploaded cmsb but can't see /cmsAdmin/admin.php with browser...404 Not Found.
Admin.php is there, I can access it via the control panel.
Can I run these content managers in parallel for a while?
Re: [markr] Installing cmsb along sige wordpress
By (Deleted User) - February 3, 2012
Hi markr,
It sounds like the Wordpress installation is set to redirect URL requests to the directory in which wordpress resides (more often than not, 'wordpress').
As a result, any request to "domain.com/cmsAdmin/" will actually be directed to "domain.com/wordpress/cmsAdmin/" which doesn't exist.
To fix this, you will have to edit the .htaccess file that wordpress has generated to allow requests to "domain.com/cmsAdmin/" to pass though uninterrupted.
This should allow you to run cmsAdmin in parallel with no conflicts (just remember that any requests to "domain.com/filename.ext" will still go to "domain.php/wordpress/filename.ext" - every file you want to access will need an exception so best to add an exception that will cover all the files you create - naming each file using a prefix, eg "cmsb-filename.ext", will make this easier).
Let me know if this helps,
Tom
It sounds like the Wordpress installation is set to redirect URL requests to the directory in which wordpress resides (more often than not, 'wordpress').
As a result, any request to "domain.com/cmsAdmin/" will actually be directed to "domain.com/wordpress/cmsAdmin/" which doesn't exist.
To fix this, you will have to edit the .htaccess file that wordpress has generated to allow requests to "domain.com/cmsAdmin/" to pass though uninterrupted.
This should allow you to run cmsAdmin in parallel with no conflicts (just remember that any requests to "domain.com/filename.ext" will still go to "domain.php/wordpress/filename.ext" - every file you want to access will need an exception so best to add an exception that will cover all the files you create - naming each file using a prefix, eg "cmsb-filename.ext", will make this easier).
Let me know if this helps,
Tom