Hi Rik, a possible minor improvement of tabs
First I am finding in my case I often go to the wrong tab, row 2, I tend to think of the row as left least published to right most published, which would give the following sequence
In draft/pending, Not Published , Published
Secondly as to stickiness, sometimes I select the wrong tab on the top row, but then I select the tab I want on the second, when I realise I made a mistake on the first I go back and change my selection, only to find the bottom row has re-set. is it possible to retain the bottom rows setting when an upper row is changed
John
Comments
Comment #1
rdeboerHi John,
I feel the same about the tab selection not being remembered, it's a real errh.. sticking point.
Unfortunately it doesn't seem to be an out-of-the-box drupal feature. I need to investigate the code more.
If you've seen it used on page or in some module somewhere let me know -- may accelerate a solution!
Rik
PS: I think the order of the tabs is quite natural: you start with draft (birth), then publish (be alive) and then unpublish (retire) :-)
Comment #2
Anonymous (not verified) commentedHi Rik
as to stickiness
The problem i can see is that we can have defualt entry settings. Not knowing enough on the coding, the only way i can see of having something different is by having 2 variables, the first identifies top row the second bottom row
When we visit "Accessible content" we look at these variables and use them to determine which tabs are to be selected. if we then change tabs , we only change one variable. I dont think I have seen an example of this in action
As to sequence, because I use scheduling and the tab is labeled Not Published rather than UnPublished we have a different meaning
Not Published - just means an item isn't published
UnPublished, implies it was previously published.
So in the simpless sense an "UnPublished" item can be "Not published", but a "Not Published" item may not be "UnPublished"
I love the English language, its great when writing procedures, especially when the majority of people dont know the difference between Should and Shall :)
John
Comment #3
rdeboerI have done some research on this and have an idea of how to do it.
Working on this now as a priority, as I feel it could put people off from using the new Module Grants & Revisioning filtering tabs and is thus holding up an official release.
RdB.
Comment #4
rhouse commentedGosh Rik, going over the latest issues, the amount of stuff you are working on gives me the heeby jeebies! How do you get it all done? Just wanted to enter a vote of thanks and appreciation!
Ron.
Comment #5
rdeboerHi Ron,
Thanks for your support.
Yeah it does keep me pretty busy, and at times it's overwhelming, but it's also good fun.
I'm learning heaps: from doing fancy stuff with themes and subthemes to now getting drupal to remember a user's tab selection dynamically
Currently the menu/tab default selection is hard-coded and initialised once when you visit the Site building>>Modules page. The core approach is inflexible and not very user-friendly, especiall with the new tab structure in Module Grants it is driving me up the wall.
Need to fix it, hopefully in generic fashion (can feel another module or subtheme coming up...).
Rik
Comment #6
Anonymous (not verified) commentedHi Rik,
I will add to Ron's vote of thanks, your doing a great job, and I know what you mean about overwhelming. just over 2 years ago I had never heard of Drupal, never done any php, about 5 minuets of CSS, now i can just about get around in a fasion :)
John
Comment #7
rdeboerThis will be covered by a new module named "Smart menus", which is currently under development and approaching release time.
Comment #8
rdeboerThis is now available via the Smart tabs module, which was released today.