I'm upgrading iThinkMedia and found a couple things missing or hidden after searching quite a bit.
How do I place blocks? I know there are block position tags -- so do I need to create a block position tag for every module or item on the page? How are the blocks moved on the page? We used to be able to manage the levels in the block area. How is this accomplished now? Also, need to specify which blocks show up for each module. I don't see anyplace in the theme system where I can position the blocks. Any help/feedback would be appreciated.
Removing the ability to edit the footer through the admin interface is not a user-friendly change, before you could change the information once (good thing), propagate everywhere. It was simple and easy to use for users of the site. It now takes more time to edit each footer in the template and is even more difficult for someone who doesn't know how to or want to learn about themes to edit the files. Can this feature be added back?
--
iThinkMedia.com
Follow me on Twitter
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
Forum Activity
- 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
Upgrading Themes - Couple Questions
-
-
- Rank: Developer
- Registered: Dec 31, 1969
- Last visit: Jun 01, 2010
- Posts: 6859
Posted: Sep 10, 2008 - 04:06 AM
vworld
Removing the ability to edit the footer through the admin interface is not a user-friendly change, before you could change the information once (good thing), propagate everywhere. It was simple and easy to use for users of the site. It now takes more time to edit each footer in the template and is even more difficult for someone who doesn't know how to or want to learn about themes to edit the files. Can this feature be added back?
You're kidding right? Set a block area for the footer and put an HTML block down there.
--
Home Page | Find on Facebook | Follow on Twitter
-
- Rank: Expert
- Registered: Mar 15, 2003
- Last visit: Oct 21, 2009
- Posts: 1221
Posted: Sep 10, 2008 - 06:52 AM
But why remove the footer option in the first place?
Now any theme will have to be edited to create that block position, then instructions on the block position added to the theme etc etc..
--
Zikula Themes -
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
Posted: Sep 10, 2008 - 07:30 AM
The footer option was removed as a security decision.
(Mostly of the PHP-Nuke sites are hacked through there
)
In the BlankTheme project, we extract those common parts (HTML HEAD and theme footer) into individual templates to edit them only once.
Block positions can be a solution too
but seems like a waste of resources and efforts for a simple issue like the footer...
--
- Mateo T. -
Mis principios... son mis fines -
- Registered: Dec 31, 1969
- Last visit: Oct 21, 2009
- Posts: 786
Posted: Sep 10, 2008 - 08:08 AM
mhalbrook
vworld
Removing the ability to edit the footer through the admin interface is not a user-friendly change, before you could change the information once (good thing), propagate everywhere. It was simple and easy to use for users of the site. It now takes more time to edit each footer in the template and is even more difficult for someone who doesn't know how to or want to learn about themes to edit the files. Can this feature be added back?
You're kidding right? Set a block area for the footer and put an HTML block down there.
True, I'm not thinking out of the 'block' ;) -- just trying to find work arounds and you know old habits are hard to break.
I'd like to build a inline editing system for end users so they can edit content within the context of the site and manage the placement of blocks without having to go to the back end. We have the beginnings of that sort of system already but would like to take it to the next level -- I've seen several systems that do it very well and I'm shooting for the lowest common denominator, think of teaching your grandmother to use the system, i.e., point and click.
Anyone interested in helping?
--
iThinkMedia.com
Follow me on Twitter -
- Registered: Dec 31, 1969
- Last visit: Oct 21, 2009
- Posts: 786
Posted: Sep 10, 2008 - 08:11 AM
nestormateo
The footer option was removed as a security decision.
(Mostly of the PHP-Nuke sites are hacked through there )
In the BlankTheme project, we extract those common parts (HTML HEAD and theme footer) into individual templates to edit them only once.
Block positions can be a solution too
but seems like a waste of resources and efforts for a simple issue like the footer...
Good idea thanks for sharing how you do it. I'm just trying to streamline the process for myself and clients who need to change/update their site without much effort.
--
iThinkMedia.com
Follow me on Twitter -
- Registered: Dec 31, 1969
- Last visit: Oct 21, 2009
- Posts: 786
Posted: Sep 10, 2008 - 08:12 AM
How does everyone handle the block placement? Am I missing the forest for the trees on this one too? I hate asking questions because I feel like such an idiot but can't find it. Please point me in the right direction :)
--
iThinkMedia.com
Follow me on Twitter -
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
Posted: Sep 10, 2008 - 11:56 AM
Again, sharing the way we do in BlankTheme
by now we use a block position for each zone.
'left' and 'right' columns, and some special areas like 'navtop', 'bottoml', 'bottomr', etc...
I guess you already know that you need <--[blockposition name='NameHere']-->
for each zone where you want to put some blocks,
then create the Block Position with that Name and assign blocks there...
The footer issue solved with a block position can look like:
in the templates of your themeCode
...
<div id="footer">
<!--[blockposition name='footer']-->
</div>
...
Then go to the Blocks Admin Panel, create a new 'footer' block position
and assign to it your HTML block with the content you want...
From Zikula 2.0 we'll able to play with blockposition a little more,
and extract the blocks of that position one by one to put them where we want.
By now, it's required a blockposition for each zone...
Doubts?
--
- Mateo T. -
Mis principios... son mis fines -
- Registered: Dec 31, 1969
- Last visit: Oct 21, 2009
- Posts: 786
Posted: Sep 10, 2008 - 02:57 PM
Woo hoo, found the block placement feature exactly where it make sense but was hidden right under the placement options block there is:
"Click to show/hide advanced block placement options"
"The following options allow the display of the block to be restricted to certain modules and module functions."
It is obscure so maybe a graphic (like a small arrow (small tick)) alerting the user it is there would be helpful. Additionally, the terminology we're using is a bit 'programmer' centric, what can specifying a function type, function, and custom argument do for the designer/publisher? What do they mean and how are they applied? Can we give examples or help within the interface, i.e., just in time information/inline help? Is there a way to identify "module functions", if so where? Is it possible to have a bubble or someway for the user to get this information while creating/managing the information block? Another nice tool would be to know which module is set for the home page because often times you want specific content on the home page but not always show it on sub pages in the site. So if the module set as home could be a different color in bold or have a 'home' icon next to it then it would save a person the time/effort or looking or remembering which module is set.
- Function type(s)
- Function
- Custom Arguments
One other note, would be nice to be able to apply a permission to the block, i.e., can be viewed by _______.
--
iThinkMedia.com
Follow me on Twitter -
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
Posted: Sep 11, 2008 - 03:00 AM
As you see, i don't use the 'block placement' feature frequently
(just when a customer wants to show the block only in some specific modules...)
my way to place blocks is using block positions
The programmer centric language is because was a fast change
before release the 1.0.0 so, yes, needs to correct the terminology.
One problem here is that if i have News as my homepage
and i want to show the block in the homepage but not in News:
you can't.
The system can't see the difference because it's module based.
About permissions filter, well, i guess that many of the devs agrees
that must be managed from the permissions rules...
--
- Mateo T. -
Mis principios... son mis fines -
- Rank: Softmore
- Registered: Feb 07, 2003
- Last visit: May 31, 2010
- Posts: 404
Posted: Sep 11, 2008 - 11:00 AM
vworld
It is obscure so maybe a graphic (like a small arrow (small tick)) alerting the user it is there would be helpful.
I totally agree. -
- Registered: Dec 31, 1969
- Last visit: Oct 21, 2009
- Posts: 786
Posted: Sep 15, 2008 - 02:15 AM
nestormateo
The programmer centric language is because was a fast change
before release the 1.0.0 so, yes, needs to correct the terminology.
Not an attack, so no need to defend, Zikula/PN has always had this flaw, hope we can start changing it though. Also, would be nice to have a work around right now so if you could define the terminology for us, i.e., non programmers, then I believe we can override the language in the theme language file. If not then we'll have it fixed for the next release.
nestormateo
One problem here is that if i have News as my homepage and i want to show the block in
the homepage but not in News:you can't.
Sure you can, install the 'blank' module use that as your home page then you can create a block to show the latest news items or use the RSS feed to show the news on the homepage. Then you are only showing blocks in the "blank" module. Gives you a bit more flexibility although not as much as I would like. I like the way AutoTheme handles blocks with much finer grain control, but prefer internal system although it can be improved.
nestormateo
About permissions filter, well, i guess that many of the devs agrees
that must be managed from the permissions rules...
There could be another layer making permissions easier to apply across the platform. So root admins could create the permission structure then it gets 'hooked' into the modules you'd like to apply permissions to. This is about creating a user friendly environment for publishers not making it more difficult.
--
iThinkMedia.com
Follow me on Twitter
- Moderated by:
- Support
