Marko Heijnen

I looked into the issue. I did notice that WordPress SEO changed how it loads files. Since WordPress SEO 1.2.3 my plugin can’t autodetect the metabox anymore.

About the error that is something I need to look into this week. It seems the option of this plugin has gone corrupted. I’m also hoping to add more fixes/features.

For some details look into this changeset.
https://plugins.trac.www.ads-software.com/changeset/562703

Hey,

Thanks for the notice. I will look into it later today. I’m not sure what is going on. I believe I also tested it with this plugin without any notices. I hope to fix it today so you can do your work without errors ??

Marko

Hey,

Both things are on my todo list. For the first I’m still not sure what it precise should do. I still think the placing should be done by add_meta_box(). Also when you replace it is it for only default or always that place. Also you got plugin(s) that add an extra column.

Second one can already be done by code. I added two filters ‘tabify_default_metaboxes’ and ‘tabify_default_metaboxes_’ . $post_type. Where the array that get passed along is for all the metaboxes id’s.

About this. I’m not sure if I want something in the UI. It’s hard to say now. The UI needs a lot of work and the code also. I’m hoping to get most of this done next month. My first goal is that you can do all this with code.

Don’t see this happen soon. Not sure how ACF handles it and you know my opinion about that from https://www.ads-software.com/support/topic/plugin-tabify-edit-screen-compatibility-with-other-custom-fields-plugins?replies=11 ??

I’m curious which plugins do you use to really need that. We are talking about the following url right?
/edit-tags.php?taxonomy=product_cat&post_type=product

There is no reason why you want tabs on a taxonomy page and that is also not what my plugins does and going to do

Still no clue what you talk about. You don’t see the taxonomies of WooCommerce in the admin for moving metaboxes to another tab?

I do see them. It can be that there is a bug that I don’t know about.

Hey,

You got me lost. What do you precise mean. The plugin orders meta boxes. Also metaboxes likes categories and tags

That bug you having hasn’t to do with this topic. This is about removing them at all.
Then again I use Chrome a lot and never experienced that issue.

I don’t do stuff so I can earn some money with it. I do stuff because I like them to do.

To go to a point that my plugin will work well with ACF it just cost to much time and energy for something that can break so damn easily. That doesn’t make sense to me.

I rather would see the other way around. That ACF is compatible with my plugin. I do stuff how WordPress does things so it would be more easily for ACF to fix it.

Next month I will look into most of the issues with my plugin and solve them before going into the issues with other plugins

Btw at this moment the legacy interface needs a lot more code since when you switch back to legacy interface you remove the role and everything will break. User get no role and doesn’t show up in the approved/denied users screen

first thing is not me to fix it. Also that kind of structure is just wrong. Translating a metabox is fine but for every language a new one.

Second thing is something I don’t know about. I need to look into that. I know ACF does really weird things and I was even thinking about to drop support

Well you can set the image to a value like 15000. It contrains to a site of large and that isn’t a width of 15000 for sure.

If that is the not working one it is definitely the issue of third-column since I don’t mess with the order (yet).

Well if it was categorydiv only I could understand it but with submitdiv not. So that really should be the issue with third column.

What was the name the meta from those values so I can look into it if there is something weird going on.