[Resolved] Regularly push developments/contents into production

[Author]

Posts

[O.M9311]

Hello,

We start a "long" development, almost only with Toolset, in agile mode, with several itterations, several versions, and therefore regular deliveries in production.
In other places (especially Drupal), I experienced this problematic under the name of Staging, with more or less efficient solutions. But the problematic was known and treated. I'm not talking about continuous integration, it's still other issues.

Basically, how to push the new features / developments and new contents into production, impacting the users as little as possible (in terms of availability, but also quality of delivery, without breaking the previous features and contents).

Example 1: I add new populated fields to a custom post type, and I delete other existing ones
Example 2: I modify 10 layouts
Example 3: I create a new custom post, I initialize it with a hundred occurrences, and I integrate it in my site with roles of access, management rules during user input
Example 4: all that preceded at the same time
...

How to integrate these new features / contents / updates in the production professionally (10 minutes max, 0 regression). The hot update would be good too 🙂 but I don't ask as much.

There are many examples, but I think the idea is clear.

In classic development, we create installation and update packages. But in classic development, we know and master the whole environment (that's what you do with your updates).

When we use a CMS, and a third party tool like Toolset, we are a bit in the dark.

How can I address this issue with Toolset / WodrPress? Are there any best practices that you recommend?

Thank you very much for your answer.

Best regards,
Mansario

[Shane]

Hello,

Thank you for contacting our support forum.

Wordpress on a whole is a little tricky to maintain 2 separate installations to deploy frequently to a live environment.

However doing some reading I was able to stumble upon the link below that should be able to help.

hidden link

Please let me know if this works.

Thanks,
Shane

[O.M9311]

Hello,

I was a little surprised by your answer. This need seems to me essential for developments a little more than basic. This is what your tools offer, and I thought I would find a natural answer by questioning you.

I did some additional research to see if there are any good practices regarding my question. For the moment, I am studying the manual synchronization solution. You also talk about it. I'm also looking at the WP Staging plugin (hidden link).

My question therefore becomes:
Are there technical specifications somewhere to tell me exactly what to synchronize when I use your tools?
I add / modify / delete a ... Custom Filed / Custom Post Type / Form / Layout / View / ... What data in which tables should I synchronize?
and are there any particular rules to respect?

Thank you for your reply!

Best regards,
Mansario

[Shane]

Hi Mansario,

Yes as you are aware keeping wordpress synced with a production environment isn't as simple as how it would be with a Git repo, where you can just push to production once everything is ok.

The wp-staging plugin is a really good option for this.

Particularly here https://wordpress.org/plugins/wp-staging/

We actually don't have a technical document for this however i've sent a screenshot of a few tables that you can sync as well.

You will also need to sync the wp-options table as this is where most of the settings in toolset are stored. If nothing else is synced you will need to sync this table

Thanks,
Shane