10 February 2011



You've worked tirelessly on your site in a development environment, and after many months it goes live. Woo! Yay! Authors and visitors are adding content. Your client loves you.

Now it's six months down the line and Phase Two has been signed off by the client. You've got a new set of features to add. You've got a team of developers lined up to collaborate to build the additions.

What do you do? You can copy the production website back to your development environment, sure. You can make changes to Symphony sections... but how do you get these back onto the production environment? You don't keep a paper list of changes, do you? What if you've got two, five or ten developers all working at the same time?

Database Synchroniser ("DB Sync") attempts to take the pain away from tracking structural changes to your database. It selectively logs the SQL queries executed when you tinker with Symphony. Export these queries, and run them against the production database. Tada!


Discuss this Extension


2.7.10 Unsure
2.7.9 Unsure
2.7.8 Unsure
2.7.7 Unsure
2.7.6 Unsure
2.7.5 Unsure
2.7.4 Unsure
2.7.3 Unsure
2.7.2 Unsure
2.7.1 Unsure
2.7.0 Unsure
2.6.11 Unsure
2.6.10 Unsure
2.6.9 Unsure
2.6.8 Unsure
2.6.7 Unsure
2.6.6 Unsure
2.6.5 Unsure
2.6.4 Unsure
2.5.4 Unsure

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details