The scheduler fieldset and the nested publish and unpublish fieldsets are all three rendered as vertical tabs instead of the scheduler fieldset being a tab and the other two being fieldsets inside the tab (like it is in D6 with vertical_tabs installed).
Also see #1034114: How to define nested fieldsets for node type form?...
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | rubic_scheduler_broken.png | 35.11 KB | alphex |
| #10 | node-type vetical tabs fixed garland.jpg | 216.18 KB | jonathan1055 |
| #10 | node-type vetical tabs fixed stark.jpg | 246.93 KB | jonathan1055 |
| #9 | node-type vetical tabs fixed seven.jpg | 198.36 KB | jonathan1055 |
| #9 | node-type vetical tabs fixed bartik.jpg | 241.18 KB | jonathan1055 |
Comments
Comment #1
jonathan1055 commentedYes, I was about to post the same. There are three vertical tabs in the node-type admin edit form. The first two are 'publishing settings' and 'unpublishing settings' which have the correct content. The last one is 'scheduler' which is empty. Attached is a screen shot for the record.
Comment #2
eric-alexander schaefer commentedAnd this is what this looks like in D6...
Comment #3
sillygwailoAttaching a patch which at least gets the form items underneath "Scheduler settings". Marking as "needs work" since I think we'd rather have fieldsets, or at least separate out the publishing and unpublishing settings with headings.
Comment #4
jonathan1055 commentedIs this anything to do with #986298: fieldsets inside of vertical tabs on the form prepend "Show/Hide" to the titles that are displayed in the vertical tabs ?
Comment #5
eric-alexander schaefer commentedI don't know. but #1015798: Fieldsets inside vertical tabs have no title and can't be collapsed and the screenshots posted there suggest that it is possible to have fieldsets inside vertical tabs with D7.
Comment #6
sillygwailoWith the patch to core that Eric just pointed out, try the attached patch to Scheduler 7.x dev (ignoring my patch above). It results in the screenshot also attached.
Comment #7
sillygwailoWithout the patch to core, the Publishing Settings and Unpublishing Settings fieldsets will need to be uncollasped (
'#collapsed' => FALSE), otherwise they won't show up. Even in that case, without the core patch, the titles of the fieldsets won't show up.Comment #8
eric-alexander schaefer commentedLooks like we worked on it at the same time. I just found out myself.
It is basically a css problem. They designed it that way. I don't know what to do about it. O well, maybe we have to accept it for now and see if #1015798: Fieldsets inside vertical tabs have no title and can't be collapsed finds its way into 7.1
I added some code formatting changes and some cleanup. See attached patch. If there are no objections against this patch I will commit it.
We will need to come back to this problem later, because the options are not enough separated and do not tell strikingly enough if they belong to publishing or unpublishing.
Comment #9
jonathan1055 commentedI would suggest that we have the best of both your ideas. We want to make it easy to revisit and fix this when #1015798: Fieldsets inside vertical tabs have no title and can't be collapsed is committed, but also we do not want to reduce the functionality of scheduler's nice fieldsets by forcing them open. We can do this by adding our own scheduer.css file which just contains the additions in that patch and we can simply remove them when they are in D7 core. We can write our form exactly how it should be done. We then retain the ability to set the collapsed true/false for our fieldsets etc.
The attached screen grabs show this fix for Bartik and Seven. The only slight trade-off is that the Seven css should not really be added to all themes, it makes a small bit of white space at the top of the fieldset in Bartik, but that is a small price to pay, and it will dissappear when we empty out the css when the D7 core is patched.
I have re-applied the formatting re-allignment that Eric did, but I almost didn't as it just confuses things and makes the patch look more complicated. But then I thought, Eric wanted it done in his patch, so I would not undo his work ;-)
Comment #10
jonathan1055 commentedIt works fine in Garland and Stark too.
Comment #11
eric-alexander schaefer commentedBeautiful. I like it. This will be important if/when we implement more actions like promote/demote stick/unstick. If the settings for all those actions would be expanded, the list would be pretty long.
You are right about the whitespace/formatting belonging into a separate patch.
Commited.
Comment #12
jonathan1055 commentedDo we need to add scheduler.css into the files 'array' in scheduler.info?
Also what about scheduler_handler_field_scheduler_countdown.inc and scheduler_vertical_tabs.js?
I've not read up on what should go into the new style of .info file.
Regarding those two files, would it not be better if they were scheduer. instead of scheduler_? Or this that specifically to make them different?
Comment #13
eric-alexander schaefer commentedOnly files that need to be loaded by drupal go into the files array. Since scheduler.css is loaded by scheduler on demand we do not need to include it into files[].
scheduler_vertical_tabs.js is also loaded automatically if the name is MODULENAME_vertical_tabs.js
The field handler file is advertised to views via a hook and the file name is by convention.
Comment #14
jonathan1055 commentedThanks for the info. Excellent answers!
Comment #16
fizk commentedWhen was this committed?
I'm still running into this issue using 7.x.-1.0.
Please release 7x.-1.1 with this fix.
Comment #17
jonathan1055 commentedHi fizk
This original fix does appear in 7.x-1.0 - the css file is present, and that was new with this. What theme are you using? This solution only addressed the core 7.x themes bartik, seven, garland and stark. Other themes may have been fixed by it, but they were not tested.
However, a later more comprehensive patch is in #1172040: Contrib solution for non-collapsible fieldsets and missing titles which has not been committed yet. This caters for all of the above, plus Rubik, and has the capacity for correcting any other specific themes more easily.
Jonathan
Comment #18
jonathan1055 commentedUntil we know what theme you are using we can't help with any fix.
Comment #19
alphex commentedThis is broken in Rubik.
Comment #20
wbobeirne commentedHey Duran,
That issue is has been resolved over here, just waiting for RTBC and commit: http://drupal.org/node/1172040#comment-6604870