It seems on many updates it is necessary to run the regeneration processes. Is it possible that the updates could kick this off automatically? When updating using MainWP one wouldn’t see the notice to regenerate CSS. Thanks.
1 Like
Related/Duplicate. Regenerate CSS in Uploads/Cwicly when theme changes
It’s ridiculous, there HAS to be a better way.
Of possible interest, Bricks just added this feature and the way they did it apparently is by adding a command to WP-CLI and calling that. It also gives them the option in the future to add more commands to WP-CLI. Perhaps an approach like that would work here?
Yeah I’d love that as well. Once you start having more pages, waiting around for the HTML to regenerate isn’t the greatest.
Yeah…I love this new feature from Bricks. Upvoted.
for the mainWP part: A function that would fire the regeneration of all 4 items would be a good solution for many.
(so after updating all websites, just fire this function in MainWP to be sure there are no problems. It the way I do it with Beaver Builder websites (BB cache))
Any chance this could be made? Thanks
Hi team,
Any update on this subject?
With a growing list of Cwicly sites to maintain, manually regenerating everything at every update is starting to get really tedious and time consuming.
I also agree that a “regeneration needed” notice would be very helpful when using WP management services (I personally use ManageWP).
1 Like
I would like to raise this topic again.
Some valid points have been raised over time.
At the end of the day, even if you take care of just a single website, it starts to get annoying at some point.
Nothing has to be forced on the user, individual settings can be implemented to cover all scenarios, if required.
Another thing that should also be considered for the future.
Even if these little inconveniences are not at the top of the team’s list. They are invitations for 1-star ratings on the repository, served on a silver platter.
Not saying this to strengthen my position, rather as an actual concern…
Hello @Marius,
Thanks for bringing this up again.
In terms of CSS regeneration, we could work towards having it automated (although this might be different for the Tailwind implementation).
The difficulty here is the fact that block markup regeneration has to be done with a JS environment (like most Gutenberg blocks).
When our blocks were fully generated dynamically, this wasn’t an issue (we had a JS version and a PHP version of the block). But Gutenberg and third-party blocks need this static markup, and dynamically generating it every page render was an issue for performance when we last tested it.
With our regeneration, we remove any need for the deprecation in Gutenberg blocks that require you to go through every page and saving it, but it comes at the cost of having to push that button manually.
The need for regeneration after Cwicly updates is decreasing, but will be necessary some of the time.
The only solution I have been able to come up with (that I hinted at previously) is providing a server environment on our end which would process all of this for users automatically. But this comes at the cost of having templates/pages with Cwicly blocks to be transmitted outside a user’s installation, which might not be desired…
If you have ideas or comments, please don’t hesitate.
Hey @Louis.
Thank you for the detailed answer.
This makes it easier to understand the required process in detail, even though I am familiar with the topic, at least superficially.
So please bear with me if my following thoughts don’t make sense in relation to the technical challenges you mentioned.
To be clear, I have no problem with a click on a button and to wait for its completion for a moment.
What I don’t like are the required actions/steps the user has to perform, like navigating first to the settings, then click each required button while waiting for the individual process has been completed, before being allowed to proceed to the next button (even though the process time has been significantly improved over several updates).
Please correct me here if I am not up to date on this and the process has changed in the meantime.
Long time ago, I asked if there are plans to streamline the process of regeneration, changing it to a single interaction. For example, from the admin bar, or directly within the notice after an update that indicates the required regeneration.
Here is also a dedicated feature request where the situation is discussed:
If at all feasible, a one-click solution would sufficiently improve this unfortunate situation.
Preferably, after an update, without having to navigate to the settings.
An additional “regenerate all” option inside the settings would be great, too!
2 Likes