Gallery style is lost when the page is reloaded

[sal0max]

Gallery style is lost when the page is reloaded

[sal0max]

Thanks a lot for opening this issue. I didn't run into the problem, as I had page caching disabled. Good catch!

Seems like the problem is known: https://discourse.getgrav.org/t/plugins-and-caching/6795/9
However, there also seems to be no real solution to the issue. Just some hacky workarounds.

I will see what I can do to remedy this situation.

[sal0max]

Fixed in c743188.
An update should soon be available via the admin panel.

Please verify the fix and close this issue, if it worked.

[sal0max]

Did you find some time to test the updated version, @beamaria ? 😗

[beamaria]

Sorry, the issue is still there; if you don't disable the cache, the pictures are stacked...

[sal0max]

Mh, which version of the plugin do you use?
I can't replicate the issue.

[beamaria]

Version 1.0.3 with Grav 1.7.7 I found the way to replicate the issue: In advanced tab of the page put the tick beside caching and enable it: this way the images are stacked on reloading. If you don't have the tick, the issue is gone. (see attachments) Issue <img width="873" alt="issue" src="https://user-images.githubusercontent.com/11693902/109132172-70950900-774b-11eb-9dd6-6b65c22e6ecd.png"> NO issue--> OK <img width="873" alt="NO issue" src="https://user-images.githubusercontent.com/11693902/109132199-7a1e7100-774b-11eb-969f-ebe951562c05.png">

…

Il giorno 24 feb 2021, alle ore 19:57, sal0max ***@***.***> ha scritto: Mh, which version of the plugin do you use? I can't replicate the issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZG6TSZSEP7FXLNUMGBKVTTAVK2NANCNFSM4XIYZI3Q>.

[sal0max]

Alright, that helps. :)

There are two Cache settings:

1. Configuration / System / Caching / Caching
2. Pages / <Page> / Advanced / Caching
   This sets cache_enable: true in a pages frontmatter and has to be set for every page.

If only the first is set enabled, there's no problem since after my fix.
However, if both caching options are enabled, I can replicate the behavior. Thanks for the clarification.

---

I couldn't find a way to overwrite the second configuration. However, I don't think that is a real issue.
The cache enabling is done actively by an user.

So.. as I can't find a way to remedy this scenario, and the behavior only happens if a user manually enables caching on a page (which probably is rare), I will close this issue for now.

If someone else has an idea, be welcome to comment here.