Thanks for the answer Mateo, I'm sorry though, I misphrased that question probably: what I wanted to do was preventing for several modules to show certain blocks or colums. I figured that out myself meanwhile: you can go to Theme in layout section, select your theme there (edit), than go to "page configuration". There go to "Create page configuration assignment", add an modulename.ini file and create a file with the same name inside the themename/config/templates folder. Afterwards go to "Page configurations" and select your ini file, choose a new page template ("NoRightcolums.htm" for example). By that your module is hooked to the template NoRightcolums and will show only left and center colums.
Maybe a sugestion for an improved usability (I'm not sure yet the new system is more intuitive than the old one though I appreciate the effort very much):
- rename the tab "page configuration" to something like "template control"
- merge "page configuration assignment" and "page configuration" table into one table
- completelly remove the blocks module and add this into the theme module functionality? the new blocks positioning is really awesome but it is in my eyes counterintuitive to have two modules that are in the end leading to the same result: how blocks (and modules look like and where.
Or maybe move the blocks module inside the layout section and rename it to "content positioning" and rename "page configuration" tab to "content templating".
But I'm not so fond of that too, to be honest, it is still not very plausible from a common sense approach.
It would be awesome if the module module (heh) edit would decide on the look of each module, what template for the module, what blocks to show up too and how the blocks look if a special look is wanted. And the blocks module could contain what block, where and what look in general.
I understand the idea of separating content and layout but its maybe not really catchy if people think naturally more in module and block terms than in content and layout. At least I do. :)
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- internetking created topic »password problem« 25. May
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- ehdwma created topic »Hide "Register new account" and change template to 3 col« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
- mdee created topic »How to implement returnpage ?« 25. May
- nestormateo responded to »Fillters in Clip« 24. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Block management feedback
-
- Rank: Registered User
- Registered: Jul 05, 2004
- Last visit: Oct 21, 2009
- Posts: 23
-
- Rank: Expert
- Registered: Nov 23, 2003
- Last visit: Dec 13, 2009
- Posts: 1487
Horian
I understand the idea of separating content and layout but its maybe not really catchy if people think naturally more in module and block terms than in content and layout. At least I do. :)
Actually it's not only catchy, it's quickly becoming standard with a lot of major scripts. It is a bit difficult to adjust to the idea if you're used to handling everything at once in one place, but once you do get your head wrapped around it you'll be amazed at how much more you can do with this structure.
It's kind of like having learned to ride a bike and thinking you can go any where and do anything in a day, and then getting your drivers license and realizing you can do that multiple times a day and to further distances... at least that's how I look at it. I wouldn't go back.
--
Under Construction!
- Moderated by:
- Support
