[wp-trac] [WordPress Trac] #53323: Place Hello Dolly in containing folder
WordPress Trac
noreply at wordpress.org
Fri Mar 3 19:32:54 UTC 2023
#53323: Place Hello Dolly in containing folder
-------------------------------------+-----------------------------
Reporter: afragen | Owner: afragen
Type: enhancement | Status: assigned
Priority: normal | Milestone: Future Release
Component: Upgrade/Install | Version: 5.8
Severity: normal | Resolution:
Keywords: has-patch needs-testing | Focuses:
-------------------------------------+-----------------------------
Changes (by afragen):
* keywords: has-patch needs-testing reporter-feedback => has-patch needs-
testing
Comment:
Replying to [comment:17 justinahinon]:
Sorry this has taken me so long to respond
> Thank you for explaining how to test @afragen.
>
> During the test team triage on June 16th, we came through others tests
scenarios that might be worth being explored:
>
> - On an existing installation, updating WordPress Core (with the patch
applied) should leave Hello Dolly as a single file
> - On fresh WordPress installation (with the patch applied), Hello Dolly
should be in the hello-doly folder
>
> These are the scenarios we are sure about based on the explanations on
the ticket.
>
> Now, those that still need to be clarified:
> - What happen when updating the Hello Dolly that's a single file? Should
it be left in a single file or moved to the directory?
An update to a single file Hello Dolly is currently replaced with a
version in a containing folder.
> - If it is already activated on an existing install, what happens when
it's moved? Does it stay activated? Can it cause fatal error then?
Currently an update from a single file Hello Dolly to a containing folder
version will update the plugin and deactivate it. No fatal occurs.
>
> Cc @hellofromtonya @boniu91 @pbearne.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53323#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list