Preview - Node Visibility by Multisite and CSS Hover Pop-out Menus
Neither of these developments is ready for prime-time release yet, but I wanted to give a preview in the event that folks are interested. The two things I have developed are: * a node_visibility_bysite module * CSS hover-based pop-out menus The node_visibility_bysite module uses a taxonomy vocabulary together with a "selective shared table database" multisite configuration to implement a "site/sub-site" shared content platform. The CSS Hover pop-out menus are implemented with Peterned's csshover.htc script (included in the CivicSpace theme). To see these features in action (these are new sites, so there is not that much content there yet), go here: http://jeffcociviccenter.org/ http://theencoreplayers.com/ We're using this to support a "contribute once, publish at "either or both" sites for our local community Civic Center that is under construction and its musical theater touring company (that is out promoting this community-based coming attraction/resource). More general applications of this capability would be a headquarters with a branch offices/stores network, or a community organization with affiliate chapters. Using a shared taxonomy vocabulary, you can implement a flexible rule-set for where node content should be visible. Questions and suggestions welcome on- or off-list. I am especially interested in Mac and Linux reports of the CSS Hover pop-out menu behavior as I only have Windows with Firefox, Opera, and MSIE browsers for testing. --Sohodojo Jim-- http://sohodojo.com
"Sohodojo Jim" wrote:
Neither of these developments is ready for prime-time release yet, but I wanted to give a preview in the event that folks are interested. The two things I have developed are:
* a node_visibility_bysite module * CSS hover-based pop-out menus
The node_visibility_bysite module uses a taxonomy vocabulary together with a "selective shared table database" multisite configuration to implement a "site/sub-site" shared content platform. [...and...] We're using this to support a "contribute once, publish at "either or both" sites
Nice idea, and one that I could find useful.
More general applications of this capability would be a headquarters with a branch offices/stores network, or a community organization with affiliate chapters. Using a shared taxonomy vocabulary, you can implement a flexible rule-set for where node content should be visible.
Yes, very reasonable scenarios for this feature need.
Questions and suggestions welcome on- or off-list. I am especially interested in Mac and Linux reports of the CSS Hover pop-out menu behavior as I only have Windows with Firefox, Opera, and MSIE browsers for testing.
Jim, here's a Macintosh report for you (and for others who may wish to use the csshover.htc script tools for Drupal/CS). Tested both URLs for left-side fly-out menu display and click-ability. Works as expected in: FireFox 1.5 Sea Monkey 1.0 Safari 1.3.2 Camino 1.0 Failed for: Internet Explorer 5.2.3 [ LOL! ] The menu does not load, but the 'box' of its space is properly allocated, so the page layout is not affected. The left side area where the menu should appear is simply solid white. I'd say things pass with flying colors, from the Mac view. IE is not an issue, of course. It's dead in the water and has been. It's the least-used browser on the least-used OS platform (so sad ;), so I think you're okay to ignore this test as a failure. HTH, -- Gary
Gary and Dave, Thanks for the experience reports! Nedjo brought my attention to the Nice Menus module which is indeed nice. Nice Menus, however, is a "Javascript for everybody on every page" solution. The csshover.htc script approach is _only_ Javascript for MSIE as a work-around for its lack of full CSS compatibility. For most modern browsers these menus are pure CSS, no scripting. So they work even if someone has Javascript disabled. The csshover.htc file is conditionally loaded within the template header only for MSIE clients. The intent here is to be very lightweight as an admin- and user-selectable UI feature within the CivicSpace and/or PHPTemplate engine. A simple "Pop-out menus on/off" link, like the "Change text size" block that the fontsize module provides, is all that would be needed to turn this UI feature on and off at will. For those wanting more info on Peterned's csshover menus, see: http://www.xs4all.nl/~peterned/csshover.html Thanks again, Gary and Dave, for the feedback. --Sohodojo Jim-- Gary wrote:
"Sohodojo Jim" wrote:
Questions and suggestions welcome on- or off-list. I am especially interested in Mac and Linux reports of the CSS Hover pop-out menu behavior as I only have Windows with Firefox, Opera, and MSIE browsers for testing.
Jim, here's a Macintosh report for you (and for others who may wish to use the csshover.htc script tools for Drupal/CS).
Tested both URLs for left-side fly-out menu display and click-ability.
Works as expected in:
FireFox 1.5 Sea Monkey 1.0 Safari 1.3.2 Camino 1.0
Failed for:
Internet Explorer 5.2.3 [ LOL! ]
The menu does not load, but the 'box' of its space is properly allocated, so the page layout is not affected. The left side area where the menu should appear is simply solid white.
I'd say things pass with flying colors, from the Mac view. IE is not an issue, of course. It's dead in the water and has been. It's the least-used browser on the least-used OS platform (so sad ;), so I think you're okay to ignore this test as a failure.
HTH, -- Gary
dave_lange wrote:
works as expected on linux in Firefox 1.5.0.1 Konqueror 3.5.1
I'm no expert on nice-menus, but it does say this in the README: Javascript is only loaded for Internet Explorer. With browsers such as Firefox, the nice-menus will work with CSS alone without any Javascript! There are also numerous modules out there to control node visibility... Of course it's good to have options. -Dave On Sunday 02 April 2006 02:49 pm, Sohodojo Jim wrote:
Gary and Dave,
Thanks for the experience reports!
Nedjo brought my attention to the Nice Menus module which is indeed nice. Nice Menus, however, is a "Javascript for everybody on every page" solution.
The csshover.htc script approach is _only_ Javascript for MSIE as a work-around for its lack of full CSS compatibility. For most modern browsers these menus are pure CSS, no scripting. So they work even if someone has Javascript disabled. The csshover.htc file is conditionally loaded within the template header only for MSIE clients.
Dave Cohen wrote:
I'm no expert on nice-menus, but it does say this in the README:
Javascript is only loaded for Internet Explorer. With browsers such as Firefox, the nice-menus will work with CSS alone without any Javascript!
Thanks for pointing this out. I just took a look and this is true for the current CVS version of Nice Menus that is hot off the presses. The 4.6 era version is Javascript dependent (at least the one I downloaded on March 20th). Nice Menu's Jake Gordon can enlighten us further about the CVS version's compatibility with 4.6 installations.
There are also numerous modules out there to control node visibility... Of course it's good to have options.
True. However, all these modules (to the best of my knowledge) support content visibility related to users and their roles based on the current limits of the node_access mechanism. The design constraint of the node access hook system is a point of current discussion following Rob Thorne's node access lament: http://lists.drupal.org/archives/development/2006-04/msg00023.html --Sohodojo Jim-- Jim Salmons and Timlynn Babitsky Founders and Research Directors Sohodojo - http://sohodojo.com
participants (3)
-
Dave Cohen -
Lists -
Sohodojo Jim