I have a fresh install of the latest Drupal 4.7 (Drupal 4.7RC3) using FreeBSD 5.4, Apache 2.0.55, MySQL 4.0.16 and pHp 4.4.x
The only error message I have got so far is
"taxonomy_theme: module rated to higher priority (weight = -1)"
I'm not sure whether it is conflicting with the weight module or any of the other ones listed here below. I'm not even sure it is an error but it is annoying with the message poping up in the log.
nodequeue
sitemenu
tables
taxonomy_theme
urlfilter
Comments
Comment #1
profix898 commentedUnfortunately I dont understand what bug you are reporting! What is the problem? The 'error' message you posted is not really an error message. It only informs you that one module has applied a theme before taxonomy_theme. To compensate this the module weight has been decreased (as described in readme). You generally see this message only once (assumed taxonomy_theme works fine with your install).
Comment #2
gdip commentedAs I wrote "I'm not even sure it is an error" but within a couple of hours last night I got almost 100 of those messages.
That bothers me a bit and makes me think that it is not normal.
Comment #3
profix898 commentedWow! No, its not normal! What version of taxonomy_theme are you using? So your weight is at -100 or so? The latest 4.7 version is limited to -10, but generally you shouldnt even reach that. Do you notice themes not getting applied properly?
Comment #4
gdip commentedThe module has the date of Mar 31 15:06.
I don't understand "So your weight is at -100 or so?" Where do I set the weight (for this module)?
It seems like the themes are getting applied properly but I haven't had the time to test that thorougly though, yet.
Comment #5
profix898 commentedThis weight thing is confusing for many people. You can't set module weight through UI (but only directly in 'system' table). The weight field has been introduced to control the order modules are called (in 4.6 always alphabetically).
It seems like there are cases when taxonomy_theme is not applied properly (e.g. error pages, page not found, ...). I just removed that 'weight adjustment code' and set the weight to -10 always. This should be sufficient. So please try the latest cvs version. It will hopefully be the default 4.7 release code soon. Feedback very welcome ;)
Comment #6
gdip commentedI installed the latest CVS version and it doesn't seem to work at all. Drupal doesn't report any "taxonomy_theme: module rated to higher priority (weight = -1)" messages anymore either. I tried vocab-based and term-based and also a specific theme for the admin area. Nothing seems to happen.
Strange!
Comment #7
profix898 commented:( Might be caused by your previous problem. Try to reset the configuration to start with default values.
Comment #8
gdip commentedI'm starting to think that there's a more serious problem but I don't know what it is. Can I revert the changes, if any are made by this module, in the database?
The nodequeue module doesn't work either. I've checked and repaired the MySQL database but there weren't any serious errors.
Any input would be much appreciated.
Comment #9
profix898 commentedTo remove every entry related to taxonomy_theme, you need to
1. Drop 'theme_pathes' table
2. Remove all db entries containing 'taxonomy_theme_', especially
DELETE FROM {variable} WHERE name LIKE 'taxonomy_theme_%'andDELETE FROM {system} WHERE filename LIKE '%taxonomy_theme.module'I dont know what can prevent the two modules (taxonomy_theme and nodequeue) from working correctly. You can only try a fresh install (again) and add contributed modules one by one. I never tried nodequeue and I dont have trouble with taxonomy_theme either. How did you 'check and repair the MySQL database' (as you wrote)? I agree from you description it sounds a bit like DB issue.
Comment #10
gdip commentedThis is getting stranger and stranger. The table you mention doesn't exist. I have absolutely no idea why it wasn't created when I installed the module. I did not get any error messages as far as I can remember.
The table is also not created when I deinstall and then reinstall the module again.
I'll try to create the table manually and also run the db_query. Then I'll do some testing and come back.
Comment #11
gdip commentedI deleted all information in the database according to your instructions but no data is written to the theme-table which this time was created when I installed the module.
It is very puzzling indeed.
Comment #12
heine commentedchanging title
Comment #13
profix898 commentedDid you have taxonomy_theme.install in the same directory when you installed it?
Yes. Thats by design of Drupal's install system. When you deinstall the module the db entry in table 'system' is not deleted. I think this is to save you time when reinstalling a module, because all settings will still exist. You need to remove the entry and then reinstall the module and all install instructions will be executed this time. When you update a module that does not have any tables to a with-table state, you need to call update.php to executed the install instructions (I think at least. I will try this and add a note to readme before tagging cvs version for 4.7). Please check you 'system' table. It should contain a taxonomy_theme.module entry with weight column set to -10.
The table is for 'extended' options only, it contains path/theme pairs. But it is not used for term-/vocab-/--- based method data. Say we have the following situation: 'Extended' assignment of themes enabled and sth typed into a textarea (e.g. node/5 in bluemarine). After hitting save nothing is added to the table!?
All general settings including the data for term-/vocab-/--- based data is saved to table 'variable'.
Setting this to 'cvs' since we are talking about the cvs now, right?!
Comment #14
mrmachine commentedI am experiencing a similar problem. I too am using Drupal 4.7 RC3, but with PHP 5, MySQL 4.1.18-standard, Apache 1.3.34 (Unix).
I'd been using the 4.7 version of this module, but then (hoping to fix a blocks problem) upgraded to the CVS version. At first, it didn't create the "theme_pathes" table, and nothing worked, but then i read about this issue, and tried uninstalling the module, deleting all relevant MySQL tables and install again.
After installing and enabling it, it didn't show up in the admin menu, so i ran update.php, and selected "1" from the 'taxonomy_theme" update menu. These are the messages that were printed:
This created the "themes_pathes" table in MySQL, but i still can't access the 'taxonomy_theme' administration section (it just takes me to a page with no options, but with 'save' and 'reset to defaults' buttons).
I'm thinking I should just go back to the non-cvs version, which was working quite well except for non-default themes not obeying block rules.
Comment #15
gdip commentedFirst of all - Thank you for taking the time and being so patient and also explaining things in a way so I understand :-))
"Did you have taxonomy_theme.install in the same directory when you installed it?"
Yes.
"Please check you 'system' table. It should contain a taxonomy_theme.module entry with weight column set to -10."
It is set to 0 (zero) and I tried to change the setting both from Webmin and from the terminal. I cannot change the value which is strange. This I don't understand.
"After hitting save nothing is added to the table!?"
Node (eg. node/854) and theme (eg. marvin) are added so that seem to work but when I access that node it still shows the default theme (changed theme a couple of times to make sure the changes were made in the table too).
"Setting this to 'cvs' since we are talking about the cvs now, right?!"
Yes!!
Comment #16
profix898 commented@mrmachine:
"it didn't show up in the admin menu"
It should be mentioned that I moved taxonomy_theme option from admin>settings>taxonomy_theme to admin>themes/taxonomy_theme. When you goto the old page by typing the url you get a blank page with buttons only. If taxonomy_theme does not show up under themes, this is generally a cache issue. Have you disabled the module before the update? This is very recommended. (It didnt have time to update the readme. Sorry for confusion.)
"which was working quite well except for non-default themes not obeying block rules"
Can you explain that a little more? Blocks configuration page is not getting themed by taxonomy_theme. Otherwise the block settings are not switched when you click on a theme. There was a fix for 4.7 so it should work with latest version.
@gdip:
Weigth entry in 'system' must be set to < -1, e.g. -10, otherwise taxonomy_theme wont work. What prevents you from changing this value? You tried to change it directly in db and it still is set to 0? How that?
Comment #17
profix898 commentedAha. Drupal ate the rest of my comment :( (it didnt like smaller sign)
Weigth entry in 'system' must be set to -1 or smaller (e.g. -10), otherwise taxonomy_theme wont work. What prevents you from changing this value? You tried to edit it directly in db and its still set to 0? How that?
@mrmachine: Try to flush the cache and your menu should be regenerated.
Comment #18
mrmachine commentedcool - that did it! thanx for the speedy reply!
i'm using taxonomy_theme to apply a particular theme to everything within /taxonomy_menu/4*, which works fine. But I've also got a block which I've configured to only show up within /taxonomy_menu/4* - when taxonomy_theme is disabled, the block shows up, but not when it is enabled. Also, I had disabled the "Browse Archive" block, but it still showed up when i was within /taxonomy_menu/4* until i went into the block's configuration and specifically disabled it from showing up on those pages.
Comment #19
gdip commentedI do try to edit directly in the db but for some reason it doesn't want to save my value. Maybe this is the core of the issue? I'll dig into this deeper and come back...
Comment #20
gdip commentedI think I finally found the error (it seems to work now).
The weight column in the system table was created as tinyint and unsigned which means it doesn't accept negative values. That was the reason why I couldn't enter '-10' as a value.
I upgraded from 4.6 to 4.7rc3 and everything seemingly went fine. I don't know whether the weight column was unsigned in 4.6 and then the upgrade script didn't contain this change. This could mean trouble for everyone upgrading from 4.6 to 4.7 and who wants to use Taxonomy Theme.
I'm not sure whether anyone responsible for the Drupal upgrade script reads this. Maybe the question should be raised somewhere else as this issue could have negative impact for many people.
Comment #21
profix898 commentedGood to hear you got it working finally.
You should definitely post an issue to Drupal's issue queue (http://drupal.org/project/issues/drupal). And I think you should
mark it critical. This must be fixed before 4.7 is released.
Comment #22
heine commentedIssue + patch submitted at http://drupal.org/node/59596