Zikula Community

• michiel
  
  

  • Rank: Softmore
  • Registered: Apr 17, 2004
  • Last visit: May 16, 2010
  • Posts: 164

  Posted: Dec 31, 2008 - 07:37 PM

  Hi,
  
  I have upgraded my site from 1.0.2 to 1.1.0 and now I get the following message when in log in as admin
  
  “ You can safly remove the modulestyleshet plugin from your theme. It is obsolete since Zikula 1.1.0. The adding of stylesheet files has been automated and does not need user interface.”
  
  I uses Blank theme and looked in the theme directory but can’t find the file I have to remove.
  
  For so far the upgrade worked fine
  Zikula rocks

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Dec 31, 2008 - 07:44 PM

  This statement is in the templates (templates/head.htm and templates/modules/admin.htm). You can remove the
  

  Code

  <!--[modulestylesheet xhtml=true]-->

  in there (in admin.htm there are some params as well), which is now called automatically. The plugin is not in BlankTheme, but in the Core system (prob pnRender/plugins). BlankTheme should be updated for 1.1 later on, but is not done yet
  
  
  
  edited by: espaan, Jan 01, 2009 - 08:46 AM
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• ROCOAFZ
  
  

  • Rank: Softmore
  • Registered: Dec 12, 2002
  • Last visit: Oct 21, 2009
  • Posts: 178

  Posted: Jan 02, 2009 - 06:52 AM

  Having this issue as well on my homepage only.... and only when all 3 columns are present. I can't find it anywhere. I removed it from head.htm and admin.htm. Also it only happens to registered users and admins.
  
  Ours www.attackforcez.com is based on BlankTheme. Any ideas?

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Jan 02, 2009 - 07:12 AM

  I had the problem because on of the modules I was using made the call in it's templates. Check the block templates and module templates for the stuff being displayed.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• ROCOAFZ
  
  

  • Rank: Softmore
  • Registered: Dec 12, 2002
  • Last visit: Oct 21, 2009
  • Posts: 178

  Posted: Jan 02, 2009 - 07:33 AM

  i checked but will recheck again. I think i covered all of them but it was late. Besides a direct call.. Could there be something else that points it? like a call to something else that points to the modulestylesheet. Also i found that if i remove the function.modulestylesheet plugin entirely... bad things happen.

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Jan 02, 2009 - 11:32 AM

  Clear the compiled templates and cache in the pnRender admin area.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Jan 02, 2009 - 11:40 AM

  you may delete all the content of the modulestylesheet function until we if there's a template still calling it...
  not the function, just leave it empty like the following code:
  

  Code

  function smarty_function_modulestylesheet($params, &$smarty)
  {
  }

  
  
  This is the dirty way to get rid of the alert if have no idea from where it's being called...
  not recommended but... an alert is annoying
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• michiel
  
  

  • Rank: Softmore
  • Registered: Apr 17, 2004
  • Last visit: May 16, 2010
  • Posts: 164

  Posted: Jan 02, 2009 - 01:43 PM

  Hi,
  Thx to Eric I solved the problem quickly
  But I use Blank Theme and It was exacly in the place eric described
  
  Thx

  • 
  •  
• gudmann
  
  

  • Rank: Softmore
  • Registered: Mar 14, 2003
  • Last visit: Apr 19, 2010
  • Posts: 116

  Posted: Jan 29, 2009 - 01:07 PM

  What a crappy alert. Is there no way around this without having to delete random code? Not exactly a user-friendly upgrade.
  I have deleted a lot of lines mentioning modulestylesheet. Not working. Still have the alert.

  • 
  •  
• jaenosjelantru
  
  

  • Rank: Moderator
  • Registered: Mar 15, 2005
  • Last visit: May 30, 2010
  • Posts: 1077

  Posted: Jan 29, 2009 - 01:20 PM

  It's a very user friendly upgrade. In your opinion, it may not be a very ADMIN friendly upgrade, but others don't agree.
  
  Since this is an open source project, how about you have a better attitude about it and try recommending something better than trouncing all over the hard work of other volunteers? How would you go about notifying users of code no longer needed they are utilizing in their theme?

  • 
  •  
• gudmann
  
  

  • Rank: Softmore
  • Registered: Mar 14, 2003
  • Last visit: Apr 19, 2010
  • Posts: 116

  Posted: Jan 29, 2009 - 08:49 PM

  This alert is in no way friendly. Not for users, not for admins. This is my opinion. There is no hint in the alert where this code is which you have to remove. All I know is that it is somewhere in some file in my theme. After deleting all instances of code that involves "modulestylesheet" and then some more, I still get the alert.
  
  I am possibly misunderstanding something. Postnuke and Zikula are open source and I am thankful for that. When you mention that a alert like this is admin-friendly I start to wonder if the aim with Zikula is that it can only be administered by admins who are advanced PHP-programmers. If so it´s not for the masses. I am not one of the advanced coders, but if I am pointed in the direction of a error I usually end by solving the problem. This alert does not point in any direction other than "theme" and therefore I´m lost.

  • 
  •  
• gudmann
  
  

  • Rank: Softmore
  • Registered: Mar 14, 2003
  • Last visit: Apr 19, 2010
  • Posts: 116

  Posted: Jan 29, 2009 - 10:19 PM

  Is it possible that some themes simply don´t work with version 1.1.0 even though they worked fine with 1.0.2?
  
  The upgrade went fine. I still get the alert if I use the theme I had, but changing to another theme it´s ok. Is there a way around this without having to use another theme?

  • 
  •  
• jaenosjelantru
  
  

  • Rank: Moderator
  • Registered: Mar 15, 2005
  • Last visit: May 30, 2010
  • Posts: 1077

  Posted: Jan 30, 2009 - 12:12 AM

  You just have to find all instances of it in your theme.
  
  THere is another post here in the forum that describes other places to look.
  
  I agree it's not best, but I'm also unawae of a better way to notify than that.

  • 
  •  
• Teb
  
  

  • Rank: Team Member
  • Registered: Feb 27, 2005
  • Last visit: Apr 12, 2010
  • Posts: 665

  Posted: Jan 30, 2009 - 12:45 AM

  Quote

  THere is another post here in the forum that describes other places to look.

  Indeed:
  You probably have (at least) one default Main Menu as a block. There is a modulestylesheet call in there too.
  
  See Upgrading to 1.1.0 >…> needs removed????: Edit system/Blocks/pnblocks/menu.php and follow instructions below.
  

  Teb

  So you could choose to replace it with this code.

  
  
  --
  -- Teb
  -- Dutch Zikula Community
  
  Support questions in a Personal Message will be ignored. Use the forums at all times!

  • 
  •  
• gudmann
  
  

  • Rank: Softmore
  • Registered: Mar 14, 2003
  • Last visit: Apr 19, 2010
  • Posts: 116

  Posted: Jan 30, 2009 - 02:34 AM

  I fixed the problem. Started again from scratch and for some reason I only had to remove two lines in master.htm document in my Xanthia 3.0 theme. Those were calls to the modulestylesheet.
  Thanks...

  • 
  •  
•  
•  

Users on-line

• rgasch

This list is based on users active over the last 60 minutes.