New Extension: MX Custom Tabs

Saw Jarrett Barnett fix. Will apply that as that is probably my problem.

Max, very nice extension for EE. Just discovered it today and am already finding good uses for it.

I have one request. It would be great if there was an option to show ONLY the custom field in a specific tab. I want to use this for an ‘authors note’ field. It would be great that if they selected that tab it would only show them the custom field(s) assigned.

Maybe you can make this a reality in a future release?

Thanks again!

Hi there,

Great extension and exactly what I was looking for.

Can someone please point me in the direction of Version: 0.7.2

The zip from http://wiseupstudio.com says version 0.7.2, but when I install, EE says that it’s still version 0.7.1.

I’m hoping that 0.7.2 fixes a problem I’m having with all my custom fields falling under one custom tab - other tabs are empty. I have about 38 custom fields I’m trying to segment into neat tabs. I’ve also disabled gypsy and still no luck. It would be great to find a solution.

Thanks, Neo EE 1.6.9

He probably just forgot to update that part of the extension docs. My install indicates the same.

Thanks Todd.

Hmm not sure then how to fix this issue. I’ve tried re-installing with no luck. All my custom fields end up under one tab

Any ideas…?

Are you using Gypsy by chance? It’s not compatible if so. Other than that, I would guess its probably some other add-on conflict.

2Neo360 Could you please provide the list(screenshot) of ext. in your system?

Hi Max,

I’ve tracked down the problem.

It seems like MX breaks the publish layout if a field type of “Date Field” is assigned to a custom field.

Hopefully you can replicate it. Apart from that it appears to work now.

Really, really useful ext.

Thanks, Neo

Hi Max, thanks for the great extension. I’ve been using for a while now, and just added a couple more fields to an FFMatrix field, and it’s started to mis-behave.

On 1 weblog it still works fine, but the same settings and with similar fields I get the following error when I create a new entry:

Fatal error: Call to a member function parent() on a non-object in /home/~blah~/extensions/ext.mx_custom_tabs.php on line 631

When I edit an existing entry from the same weblog, I get all the custom fields dumped into one for the tabs (I’ve got 2 I’ve created using your extension).

I’ve tracked it down to not working with Copee Pastee FieldType - I’ve just removed it from the FF Matrix and the problems have disappeared.

Any chance in solving? Not a problem if not, I’ll just have to do without Copee Pastee!

Had another clash, where I added another Playa field: There’s already Playa fields within the form, 2 within a tab, 1 in a Matrix field and another in the main block. I added another, and the markup went completely wonky, with the save not working.

The markup for publish form should look like this (when custom tabs works):

<div id="contentNB">
<form method="post" id="entryform"...
...hidden divs for the tabs, etc ...
<table cellspacing="0" cellpadding="0" border="0" style="width: 100%;"><tbody><tr><td class="publishBox">
...etc...
</form>
</div>

When it goes wrong, the markup looks like this:

Hence why the save doesn’t work as the main publish markup has fallen outside of the form.

Any ideas?

[Edit] Error console in Firefox shows this: Error: uncaught exception: [Exception… “Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMHTMLFormElement.removeChild]” nsresult: “0x80004003 (NS_ERROR_INVALID_POINTER)” location: “JS frame :: http://Domain.co.uk/ee-admin/index.php?S=7379619228e5564dba3ae3c1548841658a5cdcd0&C=edit&M=edit_entry&weblog_id=2&entry_id=10 :: anonymous :: line 3626” data: no]

Not that it helps much!?!

[Edit 2] This is using the latest download onyour site (v0.7.2), but the extension has the version 0.7.1 and the comment references 0.7.0.

It seems to be the Matrix field that it’s struggling with (even though it was working fine with it before).

Whereas there’s normally 2 divs for each row in the publish page (one open, one closed), the markup output by your extension breaks when trying to modify the closed div, notice the id field gets markup inserted into it instead of the name:

<div class="publishRows">
<div field_id_12="" id=">
<div class='itemWrapper' ><label for="><a>http://worthingbowlscentre.co.uk/themes/cp_global_images/expand.gif<b>  Rotating Images & Messages</b></a></div>
</div>

This should read:

<div field_id_12="" id="field_pane_off_12"...