Simple Input Tabs

[jason.dixon.email]

I have tried it together with I18N Plugin (Multilanguage). For the second language the additional tab was not showed. Maybe you can check this, because the I18N compatibility is very important for me and I think for the many multilanguage users.

Yeah I definitely want it compatible with i18n, so I'll have to check that. I have no idea why it would not be compatible... Can you expand on what you mean by tabs not showing up?
Are they not there on the page edit screen, or do they not show up on the webpage when viewed?
If they show up on the edit screen, but don't show up on the live page when viewed, can you try adding a -> to the front of the tab in the template and let me know if it shows up then?

Code:

<?php insert_page_content("->secondcontent"); ?>

Like that. Changing secondcontent for your tabname.

I agree to keep the backend as easy as possible. For the GS template creator flexible options would allow much wider use cases.
Beside the feature to create different input type fields, the possibility to give a discription text could be useful for the content editor in the backend and in special cases the default value could also help tremendously to keep it easy for for the backend user. I18N Custom Fields does show the input fields under "Page Options" (see above image) while Simple Input Tabs needs a page reload to change between "tabbed content". I would like to propose if the display of all the additional content fields is not possible just under the main edit box? If it is not "shared content" like described some post before, it would be important enough to show all the tabs/content in the page edit IMHO. Following the most simple way, this would cause less complexity (reloading or ajax tricks) and the user normally should understand: I can edit all this on this page...

Firstly, yeah it's a bit of a pain that you need to reload the page to switch tabs and I am still pondering ways to reload the editor with javascript and ajax. The reload method is to my mind the most reliable way to alter the default editors content and ensure that all data is saved successfully as it uses the CMS's own loading and saving methods, so realistically it might have to end up staying that way. It does mean that users save their data often (always a good thing ) and it also means that any changes to the template will update with each tab change (important when a new template has different tabs).

I know what you mean though, about the confusion of tabs not being all on one page. Which is why I added the "display tab location" link. So users can load up the page and see directly where each tab will place its information.

the possibility to give a discription text could be useful for the content editor in the backend and in special cases the default value could also help tremendously to keep it easy for for the backend user.

You can already do that actually. If you put in a second argument into the tag within your template:

Code:

<?php insert_page_content("secondcontent","This is the default content you will see"); ?>

It will show up as default text before they put in any content, and will always show up whenever they click on the "display tab location" link.

Is it not possible to use both plugins together (simple input tabs and i18n custom fields)? I just see it as removing a lot of flexibility when swapping the default editor with a text area for the bulk of the content. But I can see where you are coming from when you want very specific and small things having their own field.

---

Aww maaaaaan I think I have figured out what the incompatibility is between this and i18n plugin.

i18n plugin ignores the template setting saved in the pages xml file, for different languages other than the main one when displaying the page. Which means Simple Input Tabs goes looking for the template saved in the file, it works fine, but then it doesn't show up when i18n picks a new one.

NOTE: SIMPLE INPUT TABS appears to work currently with the plugin under a certain condition:

When you make a new language version of a page BEFORE you save the page, open the advanced settings drop down and choose the same template as the previous page. After this first save i18n appears to hide the template from being accessed. This should ensure that the correct template (instead of the default one) is saved with the file.

Let me know what you guys experience if you use both plugins together. This is going to be tricky to work around. But I'll see what I can do.