Simple Input Tabs

[jason.dixon.email]

Hello,

Looks pretty useful at first glance – thanks! It should make things easier when explaining the site admin. to lay editors.

A couple of points:
- there's a lot of redundant Mac stuff in the distributed .zip;
- with debug on, there are several 'Uninitialized string offset' and 'Undefined index' notices from PHP in simple_input_tabs.php.

I'm using GS 3.1.2, PHP 5.3.3 and SIT 1.8c. Several other plugins are installed, but disabled.

Hmm. By redundant mac stuff, are you referring to "hidden" spotlight files or some such? I could have sworn I didn't put any in there, but I could be wrong. Files like .DS_store?

I'll have to check out your errors.

Edit to add:
Just changing (Simple Input) tabs on the Edit page marks the page content as changed, so there's a warning if the page edit is aborted, even if none of the content has been changed. This means that just going to look at/check a site page's content in the editor can lead to unnecessary pop-ups. Not a big deal, but a bit clunky.

For a new page, is there any way to get a change of page template without having to save the page first? Again, not really a big deal, except that it's necessary to have a page title before saving, which no-one will know until they get the error message. So then they enter the page title and click 'Save Page' again, not realising that their previous template change has been reset by the save error. This will take some explaining (and troubleshooting effort from the user). (Any content will also be lost, but that's not a fault of SIT.)

Yeah I know what you're saying. This was an executive decision I had to make and it may not have been the correct one.
For a reason I have yet to fully grasp. When changing the content via Javascript (ie tab switch), the process breaks the CMS's ability to check for changes on that field. So if you changed a tab then typed in something, it would not register the changes anymore in the main content field and would not warn you that content had been changed (though changes anywhere else still work fine, like changing the title etc). So I have some good news. That warning is actually added in there manually and can be easily deleted if you like.
To remove it navigate to this section at around line 478:

Code:

warnme = true;// As content changing breaks the ability to bind actions. Set warnings for tab changes.
$('#pagechangednotify').show();
$('#pagechangednotify').text('Page has unsaved changes');
$('input[type=submit]').css('border-color','#CC0000');
$('#cancel-updates').show();

If you delete all that then it will no longer warn you when changing tabs. If you delete only the "warnme = true" part then the popup will be gone and the red border around the save button and "page unsaved changes" will still turn on upon changing tabs.

There is a secondary warning too, which you can choose to leave or delete (turn off). When clicking on the magnifying glass to bring up the tab locations, and then clicking on a tab. It will warn you before redirecting the page to that tabs location. To remove that warning navigate to this part of the code at line 204:

Code:

$link_begin = '<element'.$hand.'onClick="window.opener.location.reload(true);window.opener.warnme=true;window.opener.location.href=\''.get_site_url(false).'/admin/edit.php?id=';

And remove this section from within there:

Code:

window.opener.warnme=true;

As to the template thing. Yeah I know that is a pain. There is one semi-work around, which is to use "insert_page_content();" with empty brackets for your main content as that will follow through to any other template that uses it. Should be noted that information is never really deleted, but hidden. If a page has information filled in and the template is swapped to a new one without that tab name. The info will sit there dormant until a template with the tab name is made active again. I'm thinking about adding a config screen with a "clear all unused tabs" button at some stage, just to clear out extra information.

Fear not. Sorting out that dropdown is on my todo list. Definitely. Any development tips would be great too!

Thanks a lot for the feedback! I'm glad you're liking this. Let me know if you have any more suggestions or ideas.