Title: Problem with Staging
Last modified: March 18, 2021

---

# Problem with Staging

 *  [renpersonal](https://wordpress.org/support/users/renpersonal/)
 * (@renpersonal)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/problem-with-staging/)
 * Hi Peter, I have a website with a Staging site, when i deploye the staging over
   the main site, the data publisher in the main became corrupt, the table don’t
   exist, i need to open every data publisher and reassociated de table to select
   but i lose the columns, etc.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Passionate Programmer Peter](https://wordpress.org/support/users/peterschulznl/)
 * (@peterschulznl)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/problem-with-staging/#post-14203922)
 * Hi [@renpersonal](https://wordpress.org/support/users/renpersonal/),
 * How did you transfer your publications? Did you use the Data Publisher or another
   tool?
 * Thanks,
    Peter
 *  Thread Starter [renpersonal](https://wordpress.org/support/users/renpersonal/)
 * (@renpersonal)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/problem-with-staging/#post-14204097)
 * Hi Peter, Data Publisher.
    The transfer to staging to main site is full. Then,
   the views already created in data publisher lost the connection to database.
 *  Plugin Author [Passionate Programmer Peter](https://wordpress.org/support/users/peterschulznl/)
 * (@peterschulznl)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/problem-with-staging/#post-14205405)
 * Hi [@renpersonal](https://wordpress.org/support/users/renpersonal/),
 * You can export your publications from the Data Publisher or Data Explorer. When
   you export on your source server the plugin replaces the WP table prefix and 
   schema with special markers. When you import on your destination server the markers
   are replaced with the WP table prefix and schema of your destination server.
 * LIMITATION =
    This only works if your tables are stored in your WP database!!!
 * ALTERNATIVE =
    If your tables are stored in another database you either need 
   to edit the export file, or make sure the database names are equal on both servers.
   If you cannot rename your database (due to limitations of your ISP or other) 
   you could create a remote connection in the Data Explorer that loops back to 
   your default WP database. That allows you to give both remote connections the
   same name and transfer your publications without errors.
 * SURPRISE ❓
    I checked the code and I see now that the Data Publisher export 
   does not convert the table prefix. 🙈 Remarkable no one ever reported this before!
   😐 I will fix this in the next release. As a temporary workaround you can export
   the wp_wpda_publisher table directly from the Data Explorer. That export converts
   the table prefix correctly.
 * Thanks a lot for reporting this issue 😊
    Peter

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Problem with Staging’ is closed to new replies.

 * ![](https://ps.w.org/wp-data-access/assets/icon-256x256.png?rev=3299063)
 * [WP Data Access – App Builder for Tables, Forms, Charts, Maps & Dashboards](https://wordpress.org/plugins/wp-data-access/)
 * [Support Threads](https://wordpress.org/support/plugin/wp-data-access/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-data-access/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-data-access/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-data-access/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Passionate Programmer Peter](https://wordpress.org/support/users/peterschulznl/)
 * Last activity: [5 years, 2 months ago](https://wordpress.org/support/topic/problem-with-staging/#post-14205405)
 * Status: not resolved