CMS Made Simple Forums

Hi there,

We are in the process of migrating hosting providers. The current live host server has CMSMS installed in the root directory and the new test host server has it installed in a subfolder directory.

I copied over the database and files without issue. I then configured the config.php file for the changed paths and database connection information. I lastly added the subfolder path in the .htaccess file to include the subfolder's name.

With all of the above said and done, the default CMS page does not load when I type in the URL plus the subpath. Instead, it brings up a subpath that is designated for subdomain purposes. For example, if I typed in "http://www.mysite.com/subpath I get what would normally come up if I typed in subdomain.mysite.com/subpath. If I type in any page via its alias in the URL, it loads fine - only the default page does not load.

In my server's error log I get the following currently:
client denied by server configuration: /xx/xx/xx/xx/uploads/feusers/index.php, referer: "http://xx.com/xx/a/architects.

So there are really two issues here: 1) default page is not working and 2) subdomains are not working right, but that is an add-on (FrontEndUsers) and I would probably have to post that question elsewhere.

Thank you very much. I look forward to hearing responses on this.

Regards,
-Mike

I would put the install folder back in then run yoursite.com/install/index.php then on...

STEP 5 DON'T CREATE TABLES OR INSTALL DEFAULT CONTENT

This will recreate all the paths in config.php...

Hi Dr.CSS. Thank you for your reply. I followed your instructions and downloaded an install package of the same CMS version (as there was no install folder in the inherited file structure from the previous host - they must have deleted it).

I came across a few write errors to a few folders and the config.php file which I fixed and then there were a few warnings which I talked to GoDaddy (the new host) and we tried to change a few settings, but with no success.

Here are the warnings I receive:

1)You have exec, passthru, shell_exec, system, proc_open, curl_exec, curl_multi_exec, parse_ini_file, show_source Checking PHP disable functions
Warning: this is a list of functions disabled on your server.
2)Check for PHP Open Basedir
Open basedir restrictions are in effect. You may have difficulty with some addon functionality with this restriction.
3)Checking if session.save_path is writable
Open basedir restrictions appear to be in effect. If you have SESSION problems and ini_set works, you can try to enable sessions with cookies adding: ini_set('session.use_only_cookies', 1); to top of config.php

So after the attempts of fixing the above issues, I proceeded to the next install steps and made sure to uncheck the boxes you mentioned and the install succeeded. I then tried to go to the home page and I was brought to the same subfolder path. I noticed that the URL was different this time and saw that in the config.php, $config['url_rewriting'] was set to "'none'" so I changed it back to "'mod_rewrite'" so that the URL looks as it did (with subpaths instead of query strings).

What should I try next?

The server error log still states the client denied by server configuration error.

Thank you,
-Mike

Oh, also, I did a checksum test using the checksum file in the install folder of the download I did and I receive a whole slew of "This resource is a directory!" across the board except for 1 error which states "This resource does not exist! /xx/xx/xx/xx/', $line, 2); // split it into fields."

Thanks,
-Mike

I found another thing: I was playing around the CMS pages and tested out making another page the default page to see if that new page would appear naturally if I just typed in the URL and sure enough it did. So I looked into the expected home page and I saw that there was some smarty code that stated "{autologin}."

I removed this code and the home page works again, however, the subdomain just points to the home page now and not the destined a/architects page it's meant to go to.

Ok so I "solved" this issue by creating an identically named domain on another server and copying the CMS to the root directory there. The wildcard subdomain on the primary server points to this new server which has a dedicated IP for this identically named domain. The domain name being the same as it originally was when the CMS was installed seems to play a part in this resolution as well.

So thanks for the help. Hopefully this can help others as well.

Thanks,
-Mike