htmlBurger

This is great news!

Glad you were able to solve your issue.

Hey again,

Short answer is: no, the Carbon Fields tabs have some limitations.

They can’t be nested in other fields, and you can only have tabs on the first level. You can use them in any container you wish, but only as a replacement for the add_fields() method of the containers. You can’t nest them in other tabs, or in complex fields.

Anyway, this is probably something we’ll reconsider in a future version of the plugin.

Thanks for the idea.

This is a feature that we will probably consider implementing in a future version.

Hey again,

Yes, you can set the contents of a group to be displayed either in rows or columns.

Basically, the default layout of complex field groups is in columns, each field taking 100% width, and each next field positioned below the previous one.

But if you wish, you can position some of the fields of a group (or all of them) in a row. This can be achieved by using the set_width() method of each field. With this method you specify a percentage of the entire width that you wish this field to take.

For example, calling set_width(33) to all 3 fields in a group would position all three fields on one line. This gives you the option to position the fields in your groups as you wish – some of them can be on rows, taking 33% or 50% of the width, and some of them can be full width.

You can read more about this in the Fields -> Usage documentation article: https://carbonfields.net/docs/fields-usage/

And we’re really glad you like the plugin ??

Hey Florea,

We believe this issue is out of the Carbon Fields plugin scope. Carbon Fields post meta container uses the native WordPress meta boxes, so it makes sense for them to work just like the default post meta boxes.

I suggest that you post in the support forum of the Tabify Edit Screen plugin.

And please let us know if we can assist in any other way.

Hey Florea,

This is weird. The boxes are visible in the “Tabify edit screen” settings page for us.

Several more questions for you:
1) Are you configuring the right post type in the Tabify edit screen settings (post)?
2) Does the user you’re using have the administrator role?
3) Have you selected any particular roles in the role fields of the tab?
4) Are you using the latest version of Tabify edit screen?

Hi Florea,

While editing a post, click on the “Screen Options” in the top right portion of the screen. Are the “group1” and “group2” checkboxes enabled? Toggle them, just in case, so they get enabled.

Does the issue persist after doing this? If yes, is there any error in the browser console?

Hey,

It appears that this was a mistake in our documentation.

We’ve now updated this example in the documentation – it was missing a use Carbon_Fields\Field\Complex_Field; statement.

Also, please note that the set_layout() method is deprecated, so we’ve removed it from the example as well.

Feel free to have a look at the latest code in the example.

Hi @yoderman94,

It appears you’re using an incompatible PHP version (PHP 5.2.* or lower).

Carbon Fields supports only PHP 5.3, as you can read in its documentation and readme. So your only way around this is to use PHP 5.3 or newer.

You should note that PHP 5.2 has reached its end of life more than 5 years ago. It is not supported anymore and is potentially insecure. Using a supported version (5.5, 5.6, 7.0) is recommended.

In case you need information about the PHP supported and unsupported versions, feel free to visit:

https://php.net/supported-versions.php
https://php.net/eol.php

Hi Florea,

Can you please provide us with additional information on how your fields are setup?

It would be useful for us to have details of the exact setup of tabs and boxes you’ve added within them, so we can attempt to reproduce the issue.

Looking forward to your reply.

Glad to hear that. Have fun ??

It appears that this is because in Bedrock the WordPress core is in the /wp directory, and the wp-content is actually in a separate /app directory.

Quick fix for this: in your Bedrock config/application.php, add the following line:

define( 'Carbon_Fields\\URL', WP_CONTENT_URL . '/plugins/carbon-fields' );

This will point the Carbon Fields assets to the right URL.

Looking forward to your reply, and whether this solution worked for you.

Hey Florea,

Regarding Tabify Edit Screen compatibility: as far as we see, Carbon Fields are mostly compatible with that plugin. There is a small issue however: containers are always displayed in the page after loading, even if they are not included in the first tab.

In order to have that fixed the easy way, one would reload the first tab after everything has loaded. To do this, feel free to add this JS code to your admin code base: https://gist.github.com/tyxla/93c12725db270915ccb0

To add this code to the administration, save it in a file and enqueue it by calling wp_enqueue_script() in a function, hooked to the admin_enqueue_scripts action. Please, don’t hesitate to ask if you need further details or a more complete example.

Regarding bidirectional relationships: this is not implemented yet, but it sounds like a good feature that we might consider implementing a future version – thanks for the great idea.

Hey @taiko-media,

It appears you’re running into a JavaScript error, preventing the fields from being rendered. Is there any error in your browser console? If so, can you please send it along, so we can see what is going on?

Also, it would be useful to provide us with additional information, such as:

* The WordPress version you’re using
* List of plugins you have installed and activated
* Theme you’re using

Looking forward to your reply.

Hey Jonathan,

The term meta container is already using the default term meta, implemented in WordPress 4.4. The custom table implementation is only for WordPress installations prior to 4.4, as WordPress did not yet support term meta.

It appears that this specificity was not addressed in our documentation, however now we’ve explained it, as you can see in the updated Term Meta documentation article: https://carbonfields.net/docs/term-meta/

Thanks for reporting!