I have started testing the Editorial theme version 2.3.8, and the first problem I have encountered with 1.8.0-beta.7 is in the metadata.html.twig file (line 36). Here’s the error:
The “filter” filter expects a sequence/mapping or “Traversable”, got “null” in “partials/page-bits/metadata.html.twig” at line 36
This is line 36:
{% for item in theme_config.social if item.name|lower == 'twitter' %}
If I change it to:
{% for item in theme_config.social|default([]) if item.name|lower == 'twitter' %}
or wrap it in an if condition:
{% if theme_config.social is defined and theme_config.social is not null %}
it works correctly.
I don’t know if this is a problem in Grav 1.8, or if in this version, validations for null values are stricter. In Grav 1.7 if theme_config.social is null, it works.
Trying to port over my my site to the Grav Beta, but running into issue where the page only display text and my images. It doesn’t display the theme images or any css. Log does not show any errors.
What I have done was replaced all folders and files inside user folder in the beta with my existing folder. When trying to view the site, it only display my text and images. It doesn’t appear to be reading the css or something.
What is the proper way of upgrading to the beta???
I think I found my issue. The receptar theme has not been updated for quite sometime and needs the add |raw in the template folder as stated in these links. This is going take some time to find.
oh. That is strange. You are correct. The theme does have |raw as you pointed out. However, I am using a child template and have added a hand of templates files to it. Looking closely at them, it doesn’t look the same. I am wondering if I had ported these files before the last update of recepatar. I never bother to look through what has changed since nothing broke. Grav 1.8.0 certainly did..
Since today, I have searched my site and see what broke and looked off and have updated whichever files needed fixing. Hopefully, I’ve got them all.
Thanks for sharing this update! I’ll spin up a dev environment and run some tests against my current themes/plugins. Totally agree—the more of us who try out 1.8 beta, the quicker we can help iron out edge cases and get it stable for release.