Marko Heijnen

I don’t change anything in WordPress itself. So it just weird. I never saw it before and I test on this cases.I don’t understand French so I wasn’t sure what I was reading ??

The only thing I can imagine is browser cache.

btw, I don’t hide the publish metabox so that can not be a problem I caused. At least from what I can see.

This can’t be an issue in this plugin. I’m pretty sure about that.

The only thing what can happen is that the some meta boxes get hidden in the screen options. That is a know issue what is also posted in the readme.txt

Maybe for a next version I will do it but you need to enable it by code.

That is the main focus at this moment to make it an API like plugin so you can easily be used in plugins and projects without the need of the UI. When that is solid I can work out the UI. The main target for a 1.0 release is the first week of june. So then the code and UI should be finalized.

It’s a good point. I do believe it’s possible.

I’m not sure if I want it to be a default option. At this moment I’m consistent that the Publish meta box is always showed and on the same spot like it is by default.
Switching from different column numbers can then be confusing.

To make that better work out I do have to build extra functionality what now only can be done with code like saying the publish box should not show on every tab but only in a tab where I moved it into. All this thinks makes it why it still on a version lower then 1.0 ??

Hey Elliot,

At this moment you make use of function add_meta_box() but you add them from the hook/action admin_head. In my opinion that is wrong and should been called from out the hook/action add_meta_boxes. When that happens my plugins (maybe others) doesn’t have to add extra code.

The code what I referred to is your own code but then in my plugin. To make it compatible with your plugin.

If that isn’t possible it would help me if the add_meta_box code in your plugin would be in a separate function. Your plugin would even be more robust since you can remove duplicated code and in my plugin I can call the function instead of copy the code from your plugin.

Marko

I looked into the code and I see I have to write some own code for it. This plugin like types should register the meta boxes in another way.

If you download the development version or implement this changeset ( https://plugins.trac.www.ads-software.com/changeset/529615 ) you can let it work for now.

I will report it as an issue to the developer of Advanced Custom Fields

Not sure what happens. There is a possibility to hook into a hook and do the stuff their. It is already implemented for the plugin: types.

It is on my planning to make it workable with such kind of plugins that don’t call add_meta_box in their normally way.

I do wonder you can see the metaboxes in the settings page.

At this moment the only way to delete a tab is to remove all the metaboxes in that tab and blank the title. Will improve this in a next version.

The edit screen stays now intact like if you don’t have the plugin.

The setting page should work now in no-js mode.

I just released the new version. Please let me know what you think about the made improvements.

Thats on my todo list for the next release this friday. Still two points open
– Be able to remove a tab when it is empty ( Will get better in future releases )
– Make the setting page work when there the user doesn’t have javascript support

I just fixed this in subversion. Will release it on friday so more fixes will apply.

Will fix that in the next release. Hopefully the end of this week.

Will fix that in the next release. Hopefully the end of this week.

This is something that I would love. I will fix this for the admin page.

The edit screen is something different. At this moment it the HTML for the tabs get generated by javascript. I will look into it if it can be placed with PHP and with CSS put on the right place.