rmsite.blogg.se - Rf toolbox version 2.13

RF TOOLBOX VERSION 2.13 UPDATE
RF TOOLBOX VERSION 2.13 FULL
RF TOOLBOX VERSION 2.13 CODE

The strict mode should prevent forms from sending any extra fields and this was fixed into Grav 1.7. Strict mode Improvements: Inside forms, declaring validation: strict was not as strict as we hoped because of a bug.

RF TOOLBOX VERSION 2.13 UPDATE

However, if you update your existing site using bin/gpm or Admin Plugin upgrade process keeps the existing strict mode behaviour. IMPORTANT: Grav 1.7 changes the behavior of Strict Validation.

Added a new instead of in 'bottom' which is broken.

Grav 1.6 Upgrade Guide helps you to do this. In order to support this newer version of Twig, you need to update any old syntax in your Twig templates. Twig template engine has been updated to version 1.43, but it also supports Twig 2.13. TIP: Grav 1.6 Upgrade Guide has a dedicated Twig section. If either of these errors happen, check out the Troubleshooting section for the fix. Unfortunately some older themes may have a mix of files in blueprints/ and blueprint/pages, which breaks the detection and causes either missing fields in admin when editing the pages or a fatal error: Loop detected while extending blueprint file. This means that if you have page blueprints in blueprints/pages/ folder, standard blueprint locations are used, just like in plugins. Grav 1.7.8 adds support for defining any blueprint in your theme.

Page blueprints stop working or give error about a loop.

Check out the Troubleshooting section of this page for specific issues with plugins. There have also been some specific plugin issues that have already been discovered.

RF TOOLBOX VERSION 2.13 FULL

To properly address the issue, custom plugins should be updated to support both Grav Pages and Flex Pages by using PageInterface and also should explicitly Pages when required.Ĭheck out the Pages section and Admin Section of this guide for full details.

This is done by editing the FlexObjects plugin and disabling Pages (Admin). Switching back to regular Grav Pages might temporarily resolve your issue.

Also, to optimize performance, we stopped initializing pages on every admin call. In Grav 1.7 we introduced Flex Pages as the new default page management UI. Errors on Saving or Non-functioning Admin plugins.This is fixed in Grav 1.7 and this setting is doing what it is intended to do, show the translation codes in uppercase rather than the translated strings themselves.Ĭheck out the Troubleshooting section for the fix. This was buggy in previous versions of Grav and disabling it, didn't actually disable translations throughout the admin as intended. If your admin is displaying with untranslated strings in the interface, it's most likely because you have previously disabled Language Translations. Admin showing up with untranslated strings.This is automatically handled for you if you upgrade to Grav 1.7 via GPM, but if you have upgraded manually, you will need to set this value yourself.Ĭheck out the YAML section of this guide for full details. To handle this we have included an older version of the parser that is available when enabling Yaml Compatibility. If you manually update to 1.7 or upgrade in any way that does not go through the GPM self upgrade process, you should set this setting yourself.Ĭheck out the Twig section of this guide for full details.Īs we have upgraded to a newer version of Symfony framework, the YAML parser is stricter than it was in versions prior to 1.7.

RF TOOLBOX VERSION 2.13 CODE

This is a security enhancement, and if you are upgrading from a version prior to 1.7, we automatically enable Twig Compatibility setting in the system configuration to ensure your old Twig code will continue to function. This behavior is a result of the new default of auto-escaping being true in Grav 1.7.

HTML is displayed as code on your site rather than being rendered as HTML as intended.

IMPORTANT: For most people, Grav 1.7 should be a simple upgrade without any issues, but like any upgrade, it is recommended to take a backup of your site and test the upgrade in a testing environment before upgrading your live site.