David Smith

Hi @chrisatwp

Are you able to share a link or a screenshot in order that we can better understand the issue?

Alternatively are you able to share exact steps to replicate including details of your WordPress version and whether or not you have the Gutenberg Plugin active?

Many thanks

Hi @annettepixie

Let me see if I can source some input for you on this. I know someone who has worked on these components who might have some insight.

Many thanks

Hi Marie,

It looks like the other controls that offer this use custom components. An example from the Border panel is the BorderRadiusControl which has a special <LinkedButton> to toggle the multiple values on and off.

Unfortunately the border width control uses the standard <UnitControl> which doesn’t appear to offer the functionality you’re looking for.

Would you consider raising an Issue for this in the Github repo as I think it would be a valuable addition.

I just noticed that here you are trying to set a CSS property called inset.

return lodash.assign( 
    extraProps, 
    { 
        className: classnames( extraProps.className, 'has-absolute-positioning' ),
        style: {
            inset: "10px 10px auto auto"
        }
    } 
);

As far as I know that doesn’t exist in the CSS spec.

Can you try setting a really simple, valid property such as backgroundColor: red?

return lodash.assign( 
    extraProps, 
    { 
        className: classnames( extraProps.className, 'has-absolute-positioning' ),
        style: {
            backgroundColor: 'red'
        }
    } 
);

Hi @kuchenundkakao

Thanks for raising this.

It looks like you’re working with your own custom block, is that correct?

Have you tried doing the same with one of the Core blocks? I ask because it would be useful to have a reduced test case to work with as this one has lots of other logic which it would be better to omit when testing the specific requirement of altering style attributes in the blocks.getSaveContent.extraProps filter.

I’ll see what I can do to look into this. If you are able to produce a reduced test case that would be greatly appreciated.

Many thanks

• This reply was modified 3 years, 1 month ago by David Smith.

@josvelasco As promised here is a video which shows a work around to allow you to access those Nav block inner items. Unfortunately it does require some technical work but hopefully it’s manageable?

I also explain in the video why we’ve not been able to offer editing of the items within WordPress yet. Hopefully this provides some good background and context.

I’m hopeful that a better solution will be available in a future WordPress release.

No problem. Hope they get it sorted for you.

Hi @nomadarod

I don’t believe there is a way to manually choose the stacking order on mobile. That sounds like a good feature.

I checked and found this existing Issue.

https://github.com/WordPress/gutenberg/issues/26215

Hopefully it will be added in a future version.

Many thanks

David

Hi @timfransen

I’m seeing this testing on WP 5.8.2 on Blockbase Theme. I checked the logs and saw this

PHP Fatal error: Uncaught Error: Call to undefined method WP_Theme_JSON_Resolver_Gutenberg::get_user_custom_post_type_id() in /var/www/html/wp-content/themes/blockbase/inc/customizer/wp-customize-colors.php:159

That’s part of the Blockbase Theme code. As a result I recommend you reach out to their support team and ask for help as they will be best placed to assist you.

Many thanks,

David

Hi @timfransen

Sorry to hear this isn’t working as you expected.

I’d like to clarify a couple of things.

You say “navigation menu” – are you using the Navigation block or are you creating menus in the Appearance -> Menus screen?

If you are using Blockbase it’s likely it’s using a Navigation block. In which case you can simply toggle the “Open in new tab” on the link when in link editing mode.

You can see that in this screenshot.

If that doesn’t work I’d recommend reaching out to the Blockbase Theme author in the first instance to see if you can get some support as it might be something to do with the way their Theme is configured.

If this is still a problem or I misunderstood please let me know.

Many thanks,

David

@sdwire is correct. If you have time to regularly test your website when the latest version of the Plugin is out then you will get the latest features faster at the risk of some instability.

If you’d prefer a stable experience with a slower feature release cadence then disable and remove the Gutenberg Plugin. I’d probably recommending doing this carefully though as some Plugins or features you may have become used to won’t be available in WP 5.8.

Once WP 5.9 is released it will have a number of features baked in and you should be ok to disable the Plugin.

Always backup your site first and test carefully.

Many thanks

David

Hi @locksoft

I’m aware of such an issue and have been tracking it for a while in

https://github.com/WordPress/gutenberg/pull/25120

With WordPress 5.9 I’ve been very busy but I’ll see if I can round up some help to get this fixed once and for all.

It’s a tricky problem to solve but one I recognise needs solving.

Many thanks,

David

Here is an Issue I created to track these requirement.

https://github.com/WordPress/gutenberg/issues/37950

Hi @josvelasco

I worked on this block so I have some good insight here.

It was actually a deliberate decision to hide the content editor on the Navigation posts edit view. That might seem like an odd decision but unfortunately the Navigation Item blocks (which is what the content would show) has some very specific requirements in order to work properly in the editor. The main one is that all Nav items must be children of a parent Navigation block. As the Navigation block itself isn’t saved to the Navigation Post content it wouldn’t be present the thus the Nav items wouldn’t work.

We’re aware of this problem and are working on a solution which we’ll land in the Gutenberg Plugin.

Until then the best solution is to try and use a database viewing tool such as PhpMyAdmin to access post_content field of the wp_navigation post.

Find the posts table. Filter by the wp_navigation post type. Then find the Post with the ID that matches your Navigation Post. The post_content field of that post contains the Navigation block data.

I appreciate this might be tricky if you are not experienced in using a database tool. I’ll try and post a YouTube video talking you through this in the near future and I’ll drop a link here.

In the meantime, know that we are working on a solution to this problem and appreciate your patience.

Kindest,

David

Hi @dixravi

Sorry to hear you’re having trouble with the Editor.

It is opening wide than a normal Gutenberg editor,

I’m not clear from your screenshot what you’re refering to?

Perhaps it’s the full screen mode of the editor? If so you can disable it by going to the 3 dots option menu in the top right of the editor and clicking on “Fullscreen mode”.

If that’s not right and you have a different problem please reply and let me know.

All the best