hello.
when I updated classicPress few times I noticed a theme twenty seventeen getting reinstalled on my site.
I think some addons too.
like, why themes have to be reinstalled like that? why they can’t be separate updates?
that is the default theme and the pepper plugin is included in core as well. that is why they reinstall every time a full core update goes live (I suppose you do have nightly on because I do not recall the normal stable doing that - but nightly does to deliver latest updates in them too).
I think that should be separate even on nightly.
…they are part of core - separating them means removing them (meaning breaking change, meaning a major version like v3) - WP has default themes and plugins also. and the nightly is not really a production release but a testing one so it makes sense people get the latest updates to TEST them before they can get really released in a stable. Obviously you can use a nightly in production if you want to use all latest features included in it but it is not mean for that…
@timkaye is there any way they reinstalling of core plugin/themes can be blocked when one is on nightly to avoid having them back every day? I think it defeats the purpose but maybe something in WP-config they can add?
1 Like
The point of the nightly is to test everything. If a user doesn’t want that, then it’s not clear to me why they’d be using the nightly. Though they could manage updates by using the Easy Updates Manager plugin.
This is a feature that I am building a plugin for. it will intercept all updates, even core, and hold them in quarantine for you to test and approve or ignore. but it is going to take some time to do that, and clearly many of those decisions in regards to core are not acceptable as part of an ignore decision. but, one rule I am setting is that if you do not use a theme or plugin, then you can tell it to ignore and delete that upload.
@Venutius here the issue IS not updates or reinstalling the plugin/them ON STABLE tho. the user is clearly using a nightly build (that is dev/testing only - not production ready or stable and is used by CP contributors/people wanting to test things BEFORE making a stable release). Nightly build updates EVERY NIGHT because it has to include what our core team did during the day and deliver it to people (like me) who are testing it on staging sites to be sure what got merged the day before is working. This means you need all parts of core (that includes core, default theme and pepper plugin) to be able to test it all otherwise if people do not test everything next stable might have bugs…
So the first thing is: why are they using a nightly if they do not want that to happen to their site?
a stable does not do that and only updates when the next stable gets released… so the fix is easy: either they go stable and remove what they do not need for good and they are good or they accept that nightly works like this for reasons that are needed and at best they can try to block it from installing pepper and the theme (if possible at all)…
You instead are preparing something to manage stable versions… and that is very good I think.
1 Like
Yes, I’m not specifically targeting that process, it’s just how things need to work in order to maintain platform integrity.
1 Like
I just don’t like how stable is behind wp compatibility + the nightly seems stable enough for my needs.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.