Thread

I have two expressionengine installations on the same hosting server. The live site is off of the root www directory and a development site is installed under a subdirectory under www. Everything works fine with the two sites, but I notice when I make a change to a core file (index.php for example) under the dev site, the message about a core file has been altered alert shows up in live site admin control panel as well as the dev site admin control panel. Why would this be, is something not configured correctly?

Hi ethetree,

That should not be happening. Could you check admin > general configuration and see what the name of your index.php file is set to.

Also open up the index.php file for both sites and double check that the system path is correct.

Sean

The index page field was actually blank in both CPs so I entered index.php and saved, but this did not resolve the issue. Both index.php files are correctly configured with the appropriate file path. Is the path stored in the DB somewhere? The only other thing I can think of is that I did copy the DB from the dev site to the live site.

Also should mention that the system folder for both sites is located on the same level as the public_html (not underneath) for each site. All config paths that I can find seem correct for both.

Ah- you’ve hit on an obscure issue- Dan sums up what’s going on here.

The path is actually stored in the database, but encoded so you’d pretty much never know that.  What you’ll want to do is clear out the bootstrap_checksums column of the exp_sites table for the dev site- and then the next time the index file is loaded, it will repopulate it with the correct path.  (I’d do it in phpmyadmin or such, but if you are at all uncomfortable with that, I can suggest a custom query.  I’d also suggest backing the table up before manually editing it.)

Does that make sense?

And as a side note- if you are removing the index.php from your urls using htaccess?  You’ll want to leave the index page field blank in the CP- otherwise index.php will be included in the autogenerated URLS on the front end.

And if you have any questions or are at all uncomfortable editing the exp_sites table as suggested?  Let me know.

The suggested DB changes did the trick.

Thanks

It is an odd issue- glad that did the trick for you!  If you run into any more problems with it, just let us know.