The attached add-on files may be out of date. Please visit Devot-ee for the latest versions.
Hi,
Extension Tabbee allows you to display Publish form tabs on per-group basis.
For example, if you have two member groups - Editors and Contributors, and you want “Options” tab to be accessible only by Editors, you now can do it!
This is another great idea. I have discovered a bug though.
I wanted to use this to hide the “options” tab for a member group. But if I hide the options tab for an “author” member group and an “author” changes anything and saves, the entry reverts back to the default status instead of the custom status assigned by a group that has permission to view the options tab. This doesn’t happen with “Tabbee” disabled or even just the tab not hidden. This is an MSM site if that’s a factor.
This is another great idea. I have discovered a bug though. I wanted to use this to hide the “options” tab for a member group. But if I hide the options tab for an “author” member group and an “author” changes anything and saves, the entry reverts back to the default status instead of the custom status assigned by a group that has permission to view the options tab. This doesn’t happen with “Tabbee” disabled or even just the tab not hidden. This is an MSM site if that’s a factor.
I tried to replicate the issue, but without success. Here what I did in MSM site:
1) created a new status group and assigned it to the weblog; 2) went Admin > Weblog Administration > Weblog Management > Edit Weblog Preferences > Administrative Preferences and set “Default Status” to one of the just created custom statuses; 3) in extension’s “Tabbee” options set that “Options” tab of the Publish form should be hidden; 4) posted a new entry; it was submitted with the same status as was set in Administrative Preferences as “Default Status”; 5) updated this entry; it was again submitted with the same status as was set in Administrative Preferences as “Default Status”.
Perhaps the steps to reproduce the bug should be somehow different?
This is another great idea. I have discovered a bug though. I wanted to use this to hide the “options” tab for a member group. But if I hide the options tab for an “author” member group and an “author” changes anything and saves, the entry reverts back to the default status instead of the custom status assigned by a group that has permission to view the options tab. This doesn’t happen with “Tabbee” disabled or even just the tab not hidden. This is an MSM site if that’s a factor.I tried to replicate the issue, but without success. Here what I did in MSM site: 1) created a new status group and assigned it to the weblog; 2) went Admin > Weblog Administration > Weblog Management > Edit Weblog Preferences > Administrative Preferences and set “Default Status” to one of the just created custom statuses; 3) in extension’s “Tabbee” options set that “Options” tab of the Publish form should be hidden; 4) posted a new entry; it was submitted with the same status as was set in Administrative Preferences as “Default Status”; 5) updated this entry; it was again submitted with the same status as was set in Administrative Preferences as “Default Status”. Perhaps the steps to reproduce the bug should be somehow different?
I have statuses: Open, Front Page, Pending and Closed. The default is set to “Pending”. I have Member Groups “Author” and “Editor”. If “Author” creates entry which is defaulted to “Pending” with tab hidden, and “Editor” opens and saves that entry as status “Open” or “Front Page” – then if “Author” opens his entry and saves, that entry will change to “Pending” (the default).
Additional info: I also have Entry Versioning enabled. Maybe that is related too. “Authors” do not have permission to edit others entries. “Editors” do.
Hi smartpill,
I have statuses: Open, Front Page, Pending and Closed. The default is set to “Pending”. I have Member Groups “Author” and “Editor”. If “Author” creates entry which is defaulted to “Pending” with tab hidden, and “Editor” opens and saves that entry as status “Open” or “Front Page”—then if “Author” opens his entry and saves, that entry will change to “Pending” (the default).
A good catch.
Grab the version 1.1. In it I fixed this bug and a couple related bugs:
1) no date being submitted when “Date” tab is hidden; 2) no default category submitted in case Category Rights extension is installed.
Hi smartpill,I have statuses: Open, Front Page, Pending and Closed. The default is set to “Pending”. I have Member Groups “Author” and “Editor”. If “Author” creates entry which is defaulted to “Pending” with tab hidden, and “Editor” opens and saves that entry as status “Open” or “Front Page”—then if “Author” opens his entry and saves, that entry will change to “Pending” (the default).A good catch. Grab the version 1.1. In it I fixed this bug and a couple related bugs: 1) no date being submitted when “Date” tab is hidden; 2) no default category submitted in case Category Rights extension is installed.
Thanks for looking at this issue. I just installed and tested 1.1 and am still having the same problem. For me, even if the Author himself set the status to “Open” and then I hide the tab, when I check the status as another user or unhide the status, it did indeed change the status to the default “Pending”.
Hi smartpill,
Thanks for looking at this issue. I just installed and tested 1.1 and am still having the same problem. For me, even if the Author himself set the status to “Open” and then I hide the tab, when I check the status as another user or unhide the status, it did indeed change the status to the default “Pending”.
Found that exp_extensions table was not updated.
Grab the version 1.1.1, upload it, then uninstall and install extension, and it should begin to work correctly.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.