Closed (fixed)
Project:
litejazz
Version:
5.x-1.1
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
27 Jul 2007 at 15:16 UTC
Updated:
24 Aug 2007 at 18:23 UTC
Jump to comment: Most recent file
i have installed drupal 5.2 fromo scratch and your theme litejazz with the theme settings api module. i have actived it and i am trying to change the fixed with option. it seems to work, but when a return to the same page to see if the option has changed, it doesn't work! please help me because I want a fixed width with this theme, it seems to be great, good work.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | added_messages.diff | 980 bytes | tom friedhof |
Comments
Comment #1
roopletheme commentedAre you sure that this is not a browser caching issue? We have had pretty good luck with the fixed-width feature. If you're using Internet Explorer, try forcing a cache reload by pressing Ctrl-F5. For Firefox, use a Ctrl-Shift-R. If this doesn't help, perhaps you could post a link?
Comment #2
Arraez commentedI've reinstalled drupal and now it works... I don't know what happened.
Comment #3
tom friedhof commentedI just did a fresh install of drupal 5.2 and this theme with the themeapi module. It seems that none of the theme specific settings are being saved to the db. When you submit the form you see that the form has the settings re-populated but if you refresh the same page after you submit the new settings, you'll notice that it does not keep the settings.
Comment #4
tom friedhof commentedFound out why the theme settings weren't being saved. I tried a different theme and noticed that I was getting an error about the files directory not being writable. I checked the litejazz theme and saw that messages were not being print to screen in the theme. I've attached the patch for messages to be print to screen if there are errors.
I also moved a </div> that wasn't lined up with the opening <div> tag for the breadcrumb.
Comment #5
roopletheme commentedWe had already restructured the code base before you submitted your patch. We've fixed this issue in the 0.15 release, but using a different approach. Feel free to re-open if you still have a problem.
Comment #6
roopletheme commented