I don't understand why but I after installing the plugins gitsync had to chown the plugins dir again
chown 33:33 -R /app/data/user/plugins
unless gitsync plugin was unable to save his configuration file
all the rest in /app/data/user was fine.
maybe a sticky bit could fix this
@jdmnt I see. Did you install the plugin using the CLI or via the Grav admin UI?
Did you install the plugin using the CLI or via the Grav admin UI?
My Bad; I thought I installed through the UI but apparently not, since I installed a second GravCMS and it didn't happened.
JOduMonT last edited by JOduMonT
@girish a new version of Grav is out
I cant install plugin (such as autodate) because it required the new version
their is a way to bypass this, such as temporary removing the read-only option on the container do the update than putting it back ?
@JOduMonT ok I trick it by copying the plugin from another grav
perhaps, since I'll use extensively this apps, maybe I should propose you to take over the control of this apps no ?
yusf last edited by
@JOduMonT There's always the option of installing Grav inside a LAMP app, which should give more freedom.
@yusf or running your own version of the grav app.
@girish I was able to reproduce the issue with the permission in ./user/config/plugins by installing via the WebAdmin the theme: Quark Open Publishing so I believe sticking the permission would be a good idea
Yes I could also run my own server as I was doing before and not participating to this community
that was not at all what we were suggesting
But if you have special requirements or always immediately want to run the latest version if may be a benefit to look at the app source and simply deploy your own customised version. Your customisations and updates can then of course be made available via pull requests to the main app.
Pushed the update out for Grav CMS and the admin panel. Are you able to install the other plugin now?