[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fMpeQhrJOHyPgCB1oespUwjFDibssC6xwe9oosi5antw":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"attitude_sk","https:\u002F\u002Fprofiles.wordpress.org\u002Fattitude_sk\u002F",1,10,85,30,84,"2026-04-04T21:59:09.250Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"post-metaboxes-tabs","Post Metaboxes Tabs","0.1","\u003Cp>When you have a lot of metaboxes in the post\u002Fpage edit screen, you end up scrolling which is confusing. Metaboxes\u003Cbr \u002F>\nrepresent a group of fields like Address, or Ingredients, etc. Imagine you are creating a deep CV for a person.\u003Cbr \u002F>\nSuddently you have \u003Ccode>Addresses\u003C\u002Fcode>, \u003Ccode>Contacts\u003C\u002Fcode>, \u003Ccode>Profile\u003C\u002Fcode>, \u003Ccode>Education\u003C\u002Fcode>, \u003Ccode>Skills\u003C\u002Fcode>, \u003Ccode>Languages\u003C\u002Fcode>, etc. But as you can see\u003Cbr \u002F>\n    Addresses, \u003Ccode>Contacts\u003C\u002Fcode>, \u003Ccode>Profile\u003C\u002Fcode> can be categorized as `Personal Data.\u003C\u002Fp>\n\u003Cp>This plugin lets you group metaboxes by anything, just name each metabox as \u003Ccode>Tab \u002F Box name\u003C\u002Fcode>. So the\u003Cbr \u002F>\n    Addresses metabox should be named as \u003Ccode>Personal Data \u002F Addresses\u003C\u002Fcode> and it will be grouped with \u003Ccode>Personal Data \u002F Contact\u003C\u002Fcode>\u003Cbr \u002F>\nunder \u003Ccode>Personal Data\u003C\u002Fcode> tab.\u003C\u002Fp>\n\u003Cp>Notes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Both \u003Ccode>Tab \u002F Box name\u003C\u002Fcode> and \u003Ccode>Tab\u002FBox name\u003C\u002Fcode> or \u003Ccode>Tab\u002F Box name\u003C\u002Fcode> work\u003C\u002Fli>\n\u003Cli>Built-in metaboxes are ignored (they usually sit in the sidebar and are needed all the time)\u003C\u002Fli>\n\u003Cli>Although tested on 3.2, it should work since 2.5\u003C\u002Fli>\n\u003Cli>Javascript enabled is required\u003C\u002Fli>\n\u003C\u002Ful>\n","Groups mataboxes when editing post\u002Fpage in administration backend to tabs according to metabox name pattern Tab\u002FMetabox.",2922,0,"2011-06-22T21:52:00.000Z","3.2.1","2.5","",[26,27,28,29,30],"administration","metaboxes","page","post","tabs","http:\u002F\u002Fwww.attitude.sk\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-metaboxes-tabs.0.1.zip",null,"2026-03-15T15:16:48.613Z"]