Since updating to version 3.8.1 we are getting errors on our front page, specifically due to the removal of gutenverse/lib/framework/assets/js/ReactPlayer.standalone.js.map from the plugin folder.
The .js files are there but the map files appear to have vanished and I am not sure how to go about regenerating them?
WordPress 7.0
Gutenverse 3.8.1
Dont think other plugins or themes are relevant as I can see that the files are missing in the directories on the server.
The page I need help with: [log in to see the link]
Never mind, just browsed the repo and cannot see that file in any recent plugin versions so it is not the issue. Something else is breaking our CSS. The hunt continues!
SO we noticed that the main text shown over the video has lost its styling. I opened web inspector and the only errors that are showing up is a 404 for that .map file.
So I checked on the server and sure enough it didn’t exist, but when I look through trac I cannot see any .map files in that folder going back several versions of the plugin so that error may have always been there and it is a theme update that has messed up our text styling.
For the text styling, please try reapplying the styles that appear incorrect. In some cases, simply saving the values again will regenerate the styles correctly and resolve the issue.
It is strange, site looks ok in the Edit Site editor but then viewing the page it is not. I have tried to change a heading from H1 to H2 and save to refresh the page but to no avail.
We’re already aware of this bug and are currently preparing a fix.
The issue was introduced by a patch included in Gutenverse 3.8.1 that addressed the Global Font vulnerability. As a temporary workaround, you can roll back to Gutenverse 3.8.0 until the fix is released.
We apologize for the inconvenience and appreciate your patience.
Unfortunately 3.8.0 triggers a fatal error on the site and won’t load, and updating to 3.8.2 doesn’t seem to fix it either so I will just patiently wait for the fix . Thanks for getting back to me on this so quickly.
Please update Gutenverse to version 3.8.2, then go to Gutenverse Dashboard → Settings → Frontend and change the Render Mechanism to Inline.
After that, check your front page again. If the issue is resolved, you can switch the Render Mechanism back to File.
If changing it to Inline fixes the issue, it means the old CSS cache is still being used. Switching the render mechanism forces Gutenverse to regenerate the CSS files, which should resolve the problem.
Could you check the typography slug in the Editor and share a screenshot? Please let us know whether it still contains capitalized letters or if it has already been changed to all lowercase. You can find the typography slug here: https://imgur.com/7otWU1Q
Also, does the typography work correctly in the Editor?
If you’re using any CSS caching or optimization plugin on your site, please try disabling it temporarily and check if the issue persists.
This reply was modified 6 days, 18 hours ago by putra1arya.
The typography slug can be found in Gutenverse Global Typography.
In the Editor, click the Gutenverse logo next to the Save button. You’ll see Color Variables and Font Variables. Open Font Variables, then select any typography. The Typography Slug is located at the bottom of the panel.
This slug is used as the styling variable, so it must match exactly with the slug used by the block. It is case-sensitive, meaning Heading and heading are treated as different values. If the slugs don’t match, the typography style won’t be applied.
From what I can see on your site, the CSS variable is using a lowercase slug, while the block is still referencing the old slug with different capitalization. That’s why the typography isn’t being applied.
If the typography works correctly in the Editor but not on the frontend, and you’re already using the latest version of Gutenverse, the issue is most likely caused by cached files. Please clear both your browser cache and your website cache, then check the page again.
OK here is what I have tried: 1. Disable all caching plugins within WP (built in WP and CloudFlare) 2. Disable any caching on the server (NGinx cache) 3. Force refresh in 2 different browsers, and from different networks, and using private browsing windows and different devices 4. Manually changed the block name in the DB on the front page from guten-ew45Su to guten-ew45su (changing to lowercase)
I checked your site again and confirmed that you’re already using the Inline render mechanism, so this doesn’t appear to be a caching issue.
I believe the lowercase typography slug has already been saved to the database. To fix the issue, you’ll need to reassign the global typography to the affected block’s typography settings so it uses the updated slug.
Also, step 4 in your process is unnecessary. The value that needs to be changed is the typography slug, not the block name. If you created a database backup before making manual changes, I recommend restoring that backup first to avoid any potential conflicts caused by those changes.
It seems to only be the Gutenverse Heading block that is affected by this. All other blocks are working as expected.
If I delete the Heading block in each location and then make a new one, it now works. I have just gone through all of our templates and reset the headings and it is now working. Thank you for helping me narrow this down!
This reply was modified 4 days, 12 hours ago by cnapier.
