Symphony.

Now I pulled this in originally using GIT, how would I update it? Is it just a case of:

git pull http://github.com/nickdunn/publish_tabs.git

Right so I have to CD into the publish_tabs directory and then do git pull

cd in the publish_tab directory and then…

git pull http://github.com/nickdunn/publish_tabs.git master

Yep that’s what I did. :)

Nick,

Great extension, very simple to use!

Quick question… When I’m creating my datasource linked to a section with this extension in use, I can add it to the output, but not group by it… Wouldn’t grouping by it in the output be prefered?

Your thoughts?

When I’m creating my datasource linked to a section with this extension in use, I can add it to the output, but not group by it

Hmm I thought I had disabled its output. There is no point in rendering the tab field in the output markup so I think it should not be selectable. Grouping would be technically impossible I’m afraid… there aren’t enough hooks to reorganise the output XML.

There isn’t actually any output, it’s just listed in the DS editor.

Shame about the grouping, it would have been great for tabbed panels front end etc…

Is there no way to append an attribute to each field’s xml node stating the panel? That would work too…

I have an issue when I’m using publish tabs together with Calendar Overlay. Seems that calendar is rendering on all tabs not only on those where it should be.

This is because the Calendar Overlay is a bit naughty and adds its HTML to the DOM outside of the field’s own <div>. If you modify publish.js of the calendar overlay it should work:

var container = field.after('<div />').next();

to

var container = jQuery('<div />').appendTo(field);

This will put the DIV it generates as a child of the field DIV, and not as a sibling.

I’ve sent Rowan a pull request: http://github.com/rowan-lewis/calendaroverlay/pull/2

EDIT: @nickdun is faster than me!

Now works great. Thanks Nick!

Nick, I changed the lines you mention in the notes, but it’s still doesn’t work for me. If I add a publish tab field on top of my section and one below with a text input field after that, the two pages in the editor are exactly the same. Everything is still in one tab.

I use SYM 2.1.1

Deifnitely this commit?

https://github.com/nickdunn/symphony-2/commit/b56efe4f84e88576af3db14cc6767781b95aba31

Do you have any JavaScript errors in your console?

Nick please change the Readme on Github to reflect the correct commit. Otherwise everyone will stumble upon this using your extension.

I’ve got a wierd thing here in Chrome.

When I first go to edit an entry I get a few rogue ‘Untitled” tabs, after refreshing a couple of times it restores itself and stays ok, until I save it and go into editing again?

On 2.1.2 and using the subsection manager on the second tab, have made the modification outlined in nick’s commit above. Any ideas… its fine in firefox =/

Attachments:

Screen shot 2010-11-10 at 11.54.43.png and Screen shot 2010-11-10 at 11.55.21.png

I think it may be a Chrome thing. I’ve not got this problem myself, but I’ve never used a browser that has so many issues…

I have all sorts of issues with it.

I’ve never used a browser that has so many issues…

IE6 ? lol.. well thanks for the response I’ll keep playing around.

heh, I meant modern…

I have some problems using publish tabs with subsection manager, in Safari and Chrome I get a javascript error that cause the page breaks, sometimes appears Untiteled tabs, sometime appears duplicatied buttons, etc…

@Ryu: Did you find where to fix it?

in Safari and Chrome I get a javascript error

What is the error?