Closed (fixed)
Project:
Drupal core
Version:
6.14
Component:
theme system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Sep 2008 at 18:50 UTC
Updated:
24 Jan 2011 at 03:32 UTC
I'm not sure this is a DA bug, and if it is not, maybe someone could tell me where to search the answer.
I have 3 sites on 1 installation: example.com , one.example.com and two.example.com . And only one.example.com shows the warning message instead of forum-vocabulary form, when i try to add/% any content type:
* warning: Missing argument 2 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
* warning: Missing argument 3 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
* warning: Missing argument 4 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
* warning: Missing argument 5 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
* warning: Missing argument 6 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
* warning: Missing argument 7 for _taxonomy_term_select() in /modules/taxonomy/taxonomy.module on line 1022.
I cant understand why the bug is only on one site, thats why i put in DA issue.
And dont have an idea how or where to fix it :(
Comments
Comment #1
agentrickardAre you doing any table prefixing? Using other modules that alter taxonomies?
This looks like it would only fail if the calling function returned FALSE from the vocabulary load.
See http://api.drupal.org/api/function/taxonomy_form/6
Comment #2
skirr@drupal.ru commentedI used my best caveage testing method and switched all 102 modules, one by one, until the DA left. There i figured out, that swithing off the Domain Theme module cures the problem.
Looks like a bug is in the theme - other themes dont have this problem. Sorry and thank you for your time.
Comment #3
agentrickardBug in the theme? How so? Very strange.
Comment #4
skirr@drupal.ru commentedJust figured it out. It was a wrong name of "base theme" in a subtheme info file. First capital letter instead of small letter. Doh!!!
Comment #5
agentrickardWeird.
Comment #6
beeradb commentedWe just ran into this. We have a base theme called "featherweight" and had it referenced as "Featherweight". Even after removing all tpl's and template.php from our theme, we had the following output on node edit forms:
And instead of input fields, we had "array" printing where taxonomy fields should have been. Possibly this has to do with it being the first element on the edit form with a custom theme or something? Just tossing that out there, I have no evidence that's the case.
Comment #7
beeradb commentedComment #8
beeradb commentedComment #9
kenorb commentedThe same problem on URL: node/add/parent-newsletter/220/222
logged as admin.
Backtrace:
Comment #10
soupp commentedCheckin theme.info file to have right (not misspelled) base theme name solved this issue for me as well. Thanks for tip!
Comment #11
jensimmons commentedI had this error. Had no idea why. Googled it. Found this thread.
Fabulous.
I'd tested out possibly using a base theme. Decided against it. Erased the base theme from the server. Forgot to edit the .info file. And got this scary error.
I assumed the problem was something with the taxonomy. With the database. With something messy and hard to fix.
No. It was just that I needed to erase the reference to the now non-existant base theme. What an easy fix. Yeah! Thanks to everyone for documenting this.
Comment #12
agentrickardThis is not a bug, then, but people misnaming themes in .info files.
That's "developer error" and not a bug. If anyone re-opens this issue, they need to be submitting a documentation patch.
Comment #13
benstallings commentedI'm not ready to submit a documentation patch, but in case someone else has the same problem I did:
I just ran into this problem with the Giordani theme, which has Marinelli as its base theme. The .info file had "marinelli" spelled and capitalized correctly. However, Marinelli was not enabled (because we were not using it). Enabling the base theme resolved the error.