Community guidelines
Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.
Vadym Member
@b.da · Joined 4 years ago · 90 posts · 0 topics · 26 reputation
Badges
Recent posts
-
Update to Grav v1.7.50.2 destroys Admin panel
· 8 months ago
@kilowahn, check if the index.php file exists in the root folder. @basicchip, had the same issue on XAMPP after updating GRAV.
-
Translation placeholders in theme blueprint fields
· 8 months ago
Thanks for your contribution to the community, Hugh! I also initially thought that creating a custom field would be unjustifiable if it meant having to override the default form field particle. Howeve
-
Translation placeholders in theme blueprint fields
· 9 months ago
@hughbris, a simple example of a custom text field (with support for complex translation), seems to work correctly, maybe it will be useful for you. Field template path to templates => THEME_TEMPL
-
Translation placeholders in theme blueprint fields
· 9 months ago
Hi @hughbris, dug a bit, and this is indeed a current limitation, specifically here. As an alternative, you can create a custom field or extend/override an existing one.
-
Http to https redirect issue
· 9 months ago
@Slartibartfast, check the following parameter in admin Configuration > System > Advanced > Miscellaneous Section > Force SSL (Yes/No)
-
Switch not working in blueprints
· 10 months ago
What about Elements Field, it does exactly what is needed in this case. @mosam, example based on your markup below :backhand_index_pointing_down: <details> <summary>Conditional Example<
-
How to reuse a complete modular section (layout, media, fields) across multiple pages?
· 11 months ago
@christiana83, you can try the following: place all your content and configurations in the frontmatter (headers), simple example below: {% set theme_config = config.theme %} {% set cta = page.find(the
-
Stuck! Manifest.json returns 403
· 11 months ago
@pamtbaau: The .htaccess in the root folder of Grav has the same restrictions. @pamtbaau, yes, it's in the same commit. Not an expert in this part either, although everything seems clear here. I just
-
Stuck! Manifest.json returns 403
· 11 months ago
@penworks, if that's your file path, you just need to change the file extension manifest.webmanifest instead of manifest.json. In my case{{ url('theme://images/manifest.webmanifest', true) }}
-
Stuck! Manifest.json returns 403
· 11 months ago
@penworks, I had the same issue, you can use the .webmanifest extension insteed, Grav blocks .json files in web server configs.