Forum Replies Created
-
AuthorPosts
-
FED
ParticipantWe tried using the 2 plugins, Meta Box and Meta Box AIO and it still has the problem.
The issue is that the WYSIWYG interface never loads. It just becomes a simple bare text box. It also is extremely slow.
Older versions we have seem to work.
1) Do you have any idea what might be causing that?
2) Where can we get older versions of the plugins? Maybe we can try rolling them back to older versions that might work.
October 12, 2024 at 2:46 AM in reply to: ✅WYISWG editor do not work inside nested group on some instances #46667FED
Participant+1 this. We're seeing the same thing.
FED
ParticipantSomewhat related: Is there any way to access older versions of MB Group? Were seeing way more serious issues like this more recently than we have in the past, and I'd like to roll back. However, I can't. We are installing via Composer (that's a known issue) but I also can't find anywhere to download the the older versions of the plugin.
FED
ParticipantWe are still (years later!!!) seeing significant performance impacts due to this problem and we have not found a solution.
FED
ParticipantClarification - this is for radio buttons, not switches
FED
ParticipantThat was totally it. Thank you so much for the help!
FED
ParticipantHi there, is there any update on this issue? I'm trying to use the same feature, but for text, and I'm seeing the same behavior.
$meta_boxes[] = array( 'id' => 'media_credit', 'title' => 'Media Credit', 'post_types' => array( 'attachment' ), 'media_modal' => true, 'fields' => array( array( 'name' => 'Media Credit', 'id' => $prefix . 'media_credit', 'type' => 'text', ), ) );FED
ParticipantHi, due to the sensitive nature of the website I support, I can't provide access like this. Could I hop on a video call and walk you through some of the admin? Would that be useful?
FED
ParticipantI don't know why, but this just started working, so you can ignore this!
FED
ParticipantWorks beautifully!
Thanks!
FED
ParticipantThe other thing I'm noticing is that I'm always seeing the JS error in the admin with Disable Gutenberg turned on, even if I'm on an admin page without any meta boxes.
I was able to address the JS error and the switch meta box not working by wrapping the block starting at line 240 with a check to make sure
$scopeis defined.if ( window.hasOwnProperty.$scope ) { // Try broader scope if field is in a cloneable group. if ( ! isGutenbergElement( logic[0] ) && ! dependentFieldSelector && $scope.hasClass( 'rwmb-group-clone' ) ) { $scope = getScope( $field, true ); selectorCache = getSelectorCache( $scope ), dependentFieldSelector = getSelector( logic[0], selectorCache ); } }FED
ParticipantThank you for looking into this!
This is weird. I'm using the Disable Guttenberg plugin and that's where I'm seeing the issue. When I use Guttenberg, I don't see the problem. I'll try and figure out what's going on. It might be something custom I'm doing.
FED
ParticipantThat is a small piece of a MUCH larger and more complex set of metaboxes, with custom classes in some cases. Here's most of the relevant code.
I rolled back to 1.6.4 and the JS error disappears and the metaboxes work as expected. I haven't tried 1.6.5 yet.
Thanks!
FED
ParticipantThank you!!
FED
ParticipantThanks! Now it seems my nested conditionals aren't behaving, but cloning is much faster!!
This is the console error:
conditional-logic.js?ver=1.5:342 Uncaught TypeError: conditions.forEach is not a function at getWatchedElements (conditional-logic.js?ver=1.5:342) at init (conditional-logic.js?ver=1.5:521) at conditional-logic.js?ver=1.5:528 at dispatch (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.9.8:3) at r.handle (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils&ver=4.9.8:3)Referring to this block:
// Outside conditions. conditions.forEach( function ( logics ) { logics.forEach( function ( logic ) { if ( typeof logic.when === 'undefined' ) { return; } logic.when.forEach( addWatchedElement, null ); } ); } ); -
AuthorPosts