Title: blocka's Replies | WordPress.org

---

# blocka

  [  ](https://wordpress.org/support/users/blocka/)

 *   [Profile](https://wordpress.org/support/users/blocka/)
 *   [Topics Started](https://wordpress.org/support/users/blocka/topics/)
 *   [Replies Created](https://wordpress.org/support/users/blocka/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/blocka/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/blocka/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/blocka/engagements/)
 *   [Favorites](https://wordpress.org/support/users/blocka/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Syncing production and development databases](https://wordpress.org/support/topic/syncing-production-and-development-databases/)
 *  Thread Starter [blocka](https://wordpress.org/support/users/blocka/)
 * (@blocka)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/syncing-production-and-development-databases/#post-1732955)
 * [@mike](https://wordpress.org/support/users/mike/), that would be great for initial
   setup, but what about updates? Especially if you use a plugin which stores a 
   pages ID in its settings. In that case when you push your pages up, the ID will
   likely be out-of-date.
    I think the root of this problem is mixing up structure
   and content. If we could define pages *in code*, and have them useable, by wordpress
   and plugins, as if they came from the database, that would help a lot.
 * I have a wacky idea which involves the `get_pages` filter, which I have to think
   through.
 * I’m already doing something similar to activate certain wordpress settings using
   the “pre” options filter.

Viewing 1 replies (of 1 total)