Closed (fixed)
Project:
Blueprint
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
23 Sep 2009 at 11:02 UTC
Updated:
30 Oct 2009 at 00:00 UTC
Jump to comment: Most recent file
I had an issue with views stumbling on phptemplate_preprocess_page(&$vars)
It was resolved by changing phptemplate to blueprint...
FW from views project:
I think you shouldn't use phptemplate at all in your theme.
1. its not needed.
2. in d7 i think it is removed.
3. It was used in d5 when there was no theme registry, but theme stuff in modules, for example theme_username
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | theme_function_change.diff | 3.01 KB | designerbrent |
Comments
Comment #1
designerbrent commentedWhat exactly was the issue that you ran into with Views?
I have used views extensively with Blueprint and have yet to run into problems with Views.
All the Preprocess functions are part of Drupal 6 (http://drupal.org/node/223430). The Drupal 5 version used _phptemplate_variables(). So when this theme is upgraded to Drupal 7, we will use the new functions that are available with that release.
What I really am interested in is the problems that you are having with Views and this theme.
Comment #2
michelle@designerbrent: I don't know the exact problem he ran into but, in general, using phptemplate_* in a theme can cause strange and hard to track down problems. It is no longer allowed in D7. You should be using blueprint_* instead.
Michelle
Comment #3
designerbrent commentedHere is a patch that changes the names of all the variables from phptemplate_ to blueprint_. This should resolve the problems.
Please test it and report your findings.
Comment #4
designerbrent commentedThanks for the comments @Brico and @Michelle. This change is now committed to version 1.3