Symphony.

I've never done this but there are two steps needed:

• You need to duplicate all EN tabs entries – I think there is a duplicate entry extension that could do that job for you.
• You need to create additional entries for US tabs mapping the parent entry id with the tab name US and the child entry id (this is stored in sym_entries_data_{id of you tabs field}).

It would certainly possible to also approach this from the JavaScript side:

• You could write a script that allows dragging one tab on the other.
• This script could take the values of the dragged tab's iframe and copy its values to the target tab's iframe.

@moonoo2 this is how it works a.t.m.: the English is the fallback. So if there is no 'US' content the EN is used. However. If the US editors want 90% of the default EN content but make little changes to be more US-like/US-centric this would involve the copy-pasting.

@nils Thanks for the quick reply. Your first solution seems do-able although a bit 'scary' (brittle?). I actually like your second suggestion a lot. It would be neat if I could offer a simple "Copy English content" link/button. This would solve the editorial problem.

I do have multiple fields in my EN subsectiontabs though, so how would the content of all those fields be best copied to another tab?

Maybe I start fiddling with a simple bookmarklet first. If you have any tips…

Thanks again.

I do have multiple fields in my EN subsectiontabs though, so how would the content of all those fields be best copied to another tab?

Copy the form from the British tab's iframe and insert it into the US one (replacing the existing form). All the needed content is accessible from the top window and this is where SST is doing its scripting.

The whole tabs interface is CSS and JavaScript only – so it just like you'd work on the front-end as well.

Hey Nils, working on updating a 2.2.5 site to 2.3 and it uses a subsection manager. I've updated the Subsection Manager to beta 2. The site doesn't fully work though because when I click on a Subsection Manger to "expand" it, it errors and just keeps spinning the waiting animation.

I looked in my web inspector's network panel and found that it was trying to pull in this URL:

http://localhost/my-site/symphony/publish/work-individual/edit/[object%20Object]/

So obviously it can't find the ID number of the entry. I looked in the HTML and it seems to have the ID number in two different places?

<li data-value="172" data-drop="Name of Entry" class="instance preview">
    <input type="hidden" value="172" name="fields[gallery-of-work][]">
    <header>
        <img src="image/path.png" width="40" height="40" class="handle">
        <a href="image/path.png" class="image file handle">Name of Entry</a>
    <a class="destructor">Remove item</a></header>
    <div class="content" style="display: block; "><iframe class="loading" src="http://localhost/my-site/symphony/publish/work-individual/edit/[object Object]/"></iframe></div>
</li>

Any thoughts on what might be causing this? Thanks.

Jesse, could you please add the following to line 108 of assets/subsectionmanager.publish.js and post the result in your console when you try to open the item?

107:    // Load iframe
108:    console.log(item, item.attr('data-value'));

I added this line to 108, cleared cache, reloaded, and tried to open a subsection manager post. Unfortunately it doesn't look like it added anything new to the log. I still have the same errors that were happening before:

06/26/2012 9:07 am > UNKNOWN: SymphonyErrorPageHandler 0 - The entry you are looking for could not be found. in file /Applications/MAMP/htdocs/my-site/symphony/lib/core/class.symphony.php on line 508

I backed up my database, and started deleting fields that used extensions. Finally I came down to the TinyMCE extension and had to remove it as a text formatter. And wahlaa. It works. (For clarity, TinyMCE was just used within the parent section, not within the subsection) Is it TinyMCE's fault? Should I ask Nick?

I'd say so, yes.

Hi Nils. Am I right in thinking that subsection tabs don't currently work for 2.3? They're not working for me, and I see you mentioned it back in the thread, I just wondered if I might have an extension conflict. Thanks

Yes, it's an extension conflict: my spare time conflicting with updating this part of the extension ;)

Nils, whatever happened to filtering of Subsection entries? I've finally got round to using this feature in 2.3 and I can't seem to get it to work.

The section I'm linking to has an SBL, but I see no option to filter by it's values. How do I do this?

Cheers in advance.

Are you talking about filtering the entries displayed in the backend? I'm not sure if filtering by SBL was ever possible (my guess is no). Select boxes and tag lists should work. Adding SBL filtering shouldn't be that hard, although one would have to convert strings to ids.

Oh, so it's SB only. Damn.

Do you have any idea where abouts in the code I could implement that?

The filter selection is built here: /fields/field.subsectionmanager.php#L192-214. And the actual entry filtering is going on here: /lib/class.subsectionmanager.php#L125-210.

hello! how does subsection manager 2 works when we are inserting data from the front-end (using events)? I have to use the "insert data in two different sections" technique?

I have to use the "insert data in two different sections" technique

Yes, exactly as Brendan describes it here: https://gist.github.com/901476

I have to use the "insert data in two different sections" technique

Yes, exactly as Brendan describes it here: https://gist.github.com/901476

Only when you are creating entries in both sections simultaneously. When you create the subsection entries at first, then you only have to set the relationship from the parent entry. This can be done by setting an array value for the SSM field in the form, like

<input type="hidden" name="fields[ssm-field-handle][]" value="{@id}"/>

for each subsection entry.

In general you just have to copy the form elements from the backend into your frontend form.

(Sorry if this i covered elsewhere, in case it was I wasn’t able to find it.)

@Nils Is it a problem to upgrade from SSM1 to SSM3 directly? Or do I need the intermediate step via SSM2?

It should work just fine to upgrade from version 1 to 3 directly.
(Ich würde aber nicht meine Hand dafür ins Feuer legen …)

Ah, thanks I’m delighted to hear! (Wenn es nicht klappt kann ich Dir ja die Hand ins Feuer legen …)

Keep getting this error when i try to edit a datasource or create a new one..

Fatal error: Call to a member function fetchFields() on a non-object in /home/spartner/public_html/extensions/subsectionmanager/fields/field.subsectionmanager.php on line 843

Extension conflict? How do I get my site back working?

SOLVED

Simply resaved all my sections