Forum Replies Created
-
AuthorPosts
-
maybeadev
ParticipantThe documentation hasn't changed for the heading field - it's still showing the desc string beneath the title in the sample image:
https://docs.metabox.io/fields/heading/
So I assume that displaying it to the right of the heading is a bug and not some attempt to lay out the screen differently?
maybeadev
ParticipantHi - it's not the INPUT box but the HEADING that's the issue.
maybeadev
ParticipantHi:
I understand the desire for the default but shouldn't that be set for new installs instead of existing installs? Now it means that the update requires us to go back and change all existing code just to prevent the 100% width from taking effect.
And since this is a large breaking change shouldn't it be in a major update instead of a minor / bug-fix update?
maybeadev
ParticipantHi:
’m not looking for a hook when the settings page is loading but immediately after the settings have been saved. This is because we need to clear a cache when settings are saved. With the mb_settings_page_load we'll end up clearing the cache every time the settings page loads - which is not what we want to do. I'm looking for something that fires only once upon saving. Hopefully there's something like that?
Thanks.
maybeadev
ParticipantTo be clear, I'm not looking for a hook when the settings page is load but immediately after the settings have been saved. This is because we need to clear a cache when settings are saved. But we don't want to clear the cache every time the settings page loads!
maybeadev
ParticipantHi - is there a way we can maybe kludge together a fix for this? I doubt that the developers will get to this idea any time soon so maybe there might be a way to implement this with a modicum of JS code?
Thanks.
maybeadev
ParticipantHi - the second one - whatever tab the user is on when the post is published / updated or the page is simply refreshed using the browser refresh button: is there a way to keep that the active tab afterwards?
Thanks.
maybeadev
ParticipantHi:
Still looking to follow up on this.
Thanks!
maybeadev
ParticipantHi:
I just wanted to follow up on this to see if there's any progress.
Thanks.
maybeadev
ParticipantHi - I got some feedback from BB on this - here is what they said:
Sorry for the wait! It looks like this issue is caused by this particular line in Metabox's script.js file:
// Detect Gutenberg.
rwmb.isGutenberg = document.body.classList.contains( 'block-editor-page' );They're detecting Gutenberg using a jQuery/JS that's causing an error when the page is being redirected.
Does this help?
maybeadev
ParticipantThat's too bad. It would be really nice to be able to add a class and/or id to style the row as well.
maybeadev
ParticipantHi:
This is not a 5.5 issue - it was happening before 5.5 and site is still on 5.4.
It's definitely an issue between metabox.io and bb.
Both the Beaver Builder plugin and the Beaver Themer plugin are at their latest versions.
Here is an image of the error:
https://www.screencast.com/t/4JSd24CR2Thanks!
PS: Not receiving email notifications of replies from this forum for some reason hence the late reply.
maybeadev
ParticipantHuh. Ok, thanks very much for double-checking for me and confirming.
maybeadev
ParticipantActually, ignore this. The issue seems to be related to file extensions. I'll update this with an updated question soon.
February 3, 2020 at 9:08 AM in reply to: ✅Getting the entire options array, deleting the entire options array #18110maybeadev
ParticipantThanks!
-
AuthorPosts