Sitepush configurations removed after to pull

[Thanatermesis]

There's some configurations of sitepush that by some reason are deleted after to import a push, more exactly the entries for activate/deactivate plugins, and the custom tables one.

What I do is, from my 'dev' site I pull (get) some tables from the live site (they are defined in my custom-tables, more exactly some tables that are only logs of a plugin, entirely out of the wordpress own tables or sitepush-related ones), after the push is complete, these configurations are deleted from the configs

[Thanatermesis]

note: tried with sitepush installed in both websites

[rowatt]

Thanks for reporting. I have found and fixed a bug which would prevent the custom tables option from being saved. I wasn't able to replicate the activate/deactivate plugins options not being saved though.

I've updated on the dev branch here on GitHub - if you are able to see if that sorts the problem for you and report back that would be great.

[Thanatermesis]

In fact I was playing in the inverse mode and just wondering... it is "pull" really a wanted thing? because it don't really sounds like a reliable option, let me explain: to use website A to get some tables from website B, using the website A itself, will/could lead to website A locked/blocked/something, I mean, we are modifying the database (importing) in realtime while using the same website for do that.

So then I tried to do the same thing from the other website, in order to "push" tables instead of "pull" them, and it worked correctly and without removing those entries

Should be "pull" totally banned? maybe explaining how to do correctly the pull?

[rowatt]

Pulling from site B into site A should work almost the same as pushing from site B into site A. The only difference is that when pulling SitePush options and what plugins are activated should be saved.

In either case, during the actual push/pull when the DB is being updated WordPress should go into maintenance mode (like it does when you do WP updates) which prevents any changes for the short time the DB is actually being changed.