Posted by designsbybrandon on November 30, 2012 at 4:04pm
I am new to Drupal and have it installed on a server running CentOS with Apache in for 'production'. I copied everything over to a dev directory and duplicated the database, changed the settings.php file to point to the dev version of the database. When I make an update in Admin of my dev version the change also appears in the public version. It does not seem to do this when updating 'Content' but other changes seem to be showing in both places. How could changes be appearing in both places when the databases are separate?
Some examples of items that have magically appeard in public when made in dev:
* 2 New Image Styles [Admin -> Config -> Media -> Image Styles]
* Edits to Taxonomy terms
Comments
Did you run update.php and
Did you run update.php and flush the cache on both sites? I would manually download the settings.php from the dev site and make sure it is pointing to the right database. And finally, when you are creating or editing dev content, make certain you are actually in the dev directory. Check the URL, In the past, I have been surprised to find that I have navigated back to the main site.
A list of some of the Drupal sites I have designed and/or developed can be viewed at http://motioncity.com/drupal
I'm not upgrading drupal or
I'm not upgrading drupal or adding modules, so is a run of update.php needed? Cache has been flushed and the settings.php definatly points to the dev database on the dev version (even the login credentials for the dev database is different that those of the production version).