Closed (fixed)
Project:
Painted Wall
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Support request
Reporter:
Created:
26 Feb 2009 at 06:09 UTC
Updated:
21 Aug 2011 at 18:14 UTC
Jump to comment: Most recent
I upgraded to the dev theme as I was told it wsa stable. However I found the following output when I installed this theme.
The change from stable to dev version is that all methods in template.php start with painted_ instead of phptemplate_ (I noticed there was an issue which prompted this change). If I rename the methods back to phptemplate_ then the errors disappear, except for the one error with the comments wrapper. Since the comment wrapper has moved to a comment.tpl.php file, I am unable to find the cause of the error.
Comments
Comment #1
Anonymous (not verified) commentedComment #2
Anonymous (not verified) commentedAll fix will be part of version 2.
Comment #3
Anonymous (not verified) commentedCommitd in 6 Beta
Comment #4
tawebworks commentedI'm running into this same bug. What do I do to fix it?
Comment #5
Anonymous (not verified) commentedTry to go to the theme page and submit it again, to refresh your theme cache
Comment #6
tawebworks commentedPlease pardon my newness... Do what? I cannot get anywhere on the site to administer it.
Comment #7
Anonymous (not verified) commentedTry to navigate to this path : /admin/build/themes
Scroll to the bottom and click on 'Save Configuration', that should clear the cache and fix your problem.
If you don't have admin access, contact the administrator, and ask them to clear the theme cache, by just submiting the form on this page.
Comment #8
tawebworks commentedThat did it.
THANK YOU VERY MUCH!!
Comment #9
Anonymous (not verified) commentedNo worries :)
If you want to avoid running into this kind of bug, you could activate the auto cache-refreshing (check 'Rebuild theme registry on every page.' here: /admin/build/themes/settings/basic ) but make sure it is unckecked when the site is live because it requires a lot of memory usage.
Only use it during development.
Also check your caching settings when live here : /admin/settings/performance
Comment #11
ernestto commentedHi, I solved the problem with couzinhub's advices. Thank you
Comment #12
sun