Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI Update command places existing Pages folder when a Theme '_demo' folder is updated #2493

Closed
paulhibbitts opened this issue May 6, 2019 · 2 comments

Comments

@paulhibbitts
Copy link

As requested, this is a new issue based on a reported CLI theme update issue.

Based on several user reports, if a theme contains a "_demo" folder this content replaces the existing Pages folder (the original is copied and renamed) when a CLI update is done if the "_demo" folder has been changed. Preferably, when a theme update via CLI is done the contents of the "_demo" folder would not be copied over.

I hope the above makes things clearer, please let me know if more info would be of help.

Below is also a series of screen caps to help illustrate the issue.

Thank you very much,
Paul

Hi, @paulhibbitts . After your comments in the getgrav forum, I did my daily update routine on my servers. There was indeed a theme update. In one of the servers, I updated the theme through the Admin panel, and no pages were changed.

In another server, I used the command line interface

        bin/gpm update

Here, the update process moved the pages directory to a time-stamped new directory (pages.05-06-2019-09-00-36) and created a new pages directory with only the theme demo content.

Screenshots follow. I hope this may be useful.
DeepinScreenshot_select-area_20190506060023
DeepinScreenshot_konsole_20190506060129

Originally posted by @quartelmestre in #2225 (comment)

@rhukster rhukster added the bug label May 8, 2019
rhukster added a commit that referenced this issue May 15, 2019
@rhukster rhukster added the fixed label May 15, 2019
@paulhibbitts
Copy link
Author

Thank you very much @rhukster !

@quartelmestre
Copy link

Thanks, @rhukster !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants