alvarofranz

Hello Maybellyne, I appreciate your help. However, it would be great to understand why this is behaving incorrectly and what I can do to rectify it. I cannot utilize this feature if it doesn’t work properly. Thanks! ??

Looks like the correct way to get the field when it’s in a group is:

{{ post.meta('groupname').fieldname }}

So, instead of:

{{ post.banner.text }}

It’s:

{{ post.meta('banner').text }}

• This reply was modified 1 year, 3 months ago by alvarofranz.

@bcworkz Thanks again. Yes, I noticed that and it’s what got me confused. “If the items porperty is never populated, where do the terms go into the table?” But yeah, as you helped to see, they get shortcuircuited into the displaying method.

I think that’s not a note for us, rather for core devs

I would love to contribute to the core but wow, it’s a complex jungle. Touch one thing and ten may break. One could apply the “If it works don’t fix it philosophy”, but I dislike it.

For the moment playing around with a custom WP, tweaking it to change what I would change, removing what I would remove. Hopefully I can some day collaborate with something valuable but first, gotta learn!

@bcworkz That’s exactly what I was looking for. Thanks for your help.

@bcworkz Thanks again for the valuable information you provide.

@sterndata Thanks but I think the provided links are not relevant to the topic. I am talking about how to insert information into the database not about how to output it.

Of course Blocks are a nice substitute for shortcodes (which kind of is what Gutenberg is all about), but I was not talking about shortcodes.

I am talking about Meta Boxes. A Meta Box is not a Shortcode. In the case of Woocommerce Products, all those boxes that allow the user to INSERT organized data (post + post meta) into the database. That cannot be done with Gutenberg blocks.

But to conclude, as @bcworkz said:

I’d expect similar functionality to always be available, even if it’s replaced by something beyond meta boxes.

@joyously A better name would be one that does not make it seem like this is the right place to make requests.

Current name and description:

Requests and Feedback Forum
“Feature requests and criticism”

Since this is not anymore the place to make requests (because things evolved) it could simply be called “Criticism” to debate about ideas before jumping into opening a GH issue.

Thanks @joyously for your help and good intentions. It would be nice to rename this forum [Requests and Feedback] to make it clearer. If you know where I can ask for this, I will do that. Evolution is nice. Accompained by upgrading old to new it’s even better!

• This reply was modified 3 years, 6 months ago by alvarofranz.

Thanks @bcworkz, that’s a reasonable insight on the topic.

For more insight, consider the fact that Woocommerce itself DOES NOT use the Gutenberg editor screen fo its Product CPT. As of today, it still uses the good old interface.

Why?

Well, because there is a lot more to the Product CPT than just being able to “blockyly” design a product description.

• This reply was modified 3 years, 6 months ago by alvarofranz.

Thanks, @joyously

But the thing is, is there not a way to add the text-align CSS property right from the Gutenberg UI?. I am currently assigning a CSS class to the container and then adding the property to that class. But aligning content is a very basic functionality, that’s why I am surprised that there is no native Gutenberg way to make it happen.

Link to the GH issue: https://github.com/WordPress/gutenberg/issues/31871

Thanks for your answer, @joyously

For the sake of curiosity. Why is this Forum called “Requests” if it’s not the right place to make Requests?

Link to the GH issue: https://github.com/WordPress/gutenberg/issues/31872

• This reply was modified 3 years, 6 months ago by alvarofranz.

@bcworkz Thanks, this gets closer to the answer I was looking for. Nevertheless, “pushing” the meta boxes to the sidebar is like… “hey let’s keep them there just to have them somewhere”, but it’s not a clean solution. It also takes away A LOT of the functionality they provided. It also somehow “kills” the way WordPress was heading towards being a generic CMS, rather than a Blog oriented CMS.

I will illustrate with a real example:

I developed a project for a client where there is a Custom Post Type called “Client”. Inside the Client CPT edit screen there are different editable areas (Custom Meta boxes). Some of those areas are big boxes that contain for example private messages with client, other boxes contain data about the client that can be modified with nice dropdowns, drag and drop, etc…

The thing is, this screen didn’t even need an editor. And now with the Gutenberg ecosystem, this was just pushed to the side, which really takes away the love for WordPress for this kind of projects.

So, the question:

Is there any plan on making metaboxes great again? In a way that they can occupy the whole screen, and in a way that the Gutenberg editor can be just disabled for certain custom post types without needing to hack the core with every update?

I would like to know this, so that I can make a long-term decision regarding the use of WP for future projects.

Thanks!

@sterndata Thanks for your answer, but I think it’s not answering the actual question.

Custom Blocks are not a substitute for Metaboxes. With meta boxes you can handle CPT attributes like for a example a custom status, a control date, an option from a list, or whatever. And then you can use those meta data to actually query things.

A Custom Block seems to be just a piece of aesthetic content. One may find a way to add/update meta fields via a Custom Block and some AJAX calls, but that is just complicating things that were already working before.

The real question is:

Gutenberg killed/replaced the TinyMCE editor. Fine. But: Is there any plan regarding the old way of handling meta boxes, which are not being faced at all by Gutenberg?