Closed (duplicate)
Project:
ThemeKey
Version:
6.x-1.0
Component:
Modules
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Feb 2009 at 13:50 UTC
Updated:
21 Aug 2009 at 09:03 UTC
Jump to comment: Most recent file
Comments
Comment #1
jcfiala commentedI had this problem as well, and this is what I did - I went to line 131 of themekey_base.inc, where it says:
$value = (array)$value[$part];and changed it to
$value = $value[$part];this is in the _themekey_property_field() function.
Once I made this change, it seemed to work fine, well, mostly.
Comment #2
profix898 commentedActually the difference in the properties syntax (node:type vs. type) is caused by a patch that introduced a namespace concept. We can now have each property in different contexts, i.e. node:language, user:language, global:language. I hope you get the idea. Namespaces were added to the -dev version right before the 6.x-1.0 release. Unfortunately that means older -dev versions got incompatible with the stable module version.
You will have to resave the properties settings page AND update your existing items manually (or simply recreate them). Sorry.
Comment #3
profix898 commentedComment #4
llacroix commentedIt doesn't seems to be fixed. I noticed the dev version and the stable version are the same...
I wrote a patch that fixe some issue like when you want to edit a node or comment a node and still want it to be based on node type...
I don't know if it break other things. But it is working definitively better than it was before.
Comment #5
jostrn commentedIt does! With the patched themekey i get the following error 2 times on a taxonomied node:
warning: mysqli_real_escape_string() expects parameter 2 to be string, object given in /htdocs/includes/database.mysqli.inc on line 323.Comment #6
designerbrent commentedChanging the values as jcfiala suggested in #1 worked for me.
Attached is a patch to make that work.
Comment #7
mkalkbrenner@#6,designerbrent:
Similar patch against current cvs version was already posted here:
http://drupal.org/node/434242
So I mark this issue as duplicate.