The upgrade process was rather tedious, but I think I got everything disabled that I was supposed to. I'm hoping views_content was Views Content Panes with Chaos Tools. Anyway, I'm getting this error on every page load now:
user warning: Unknown column 'tm.type' in 'field list' query: SELECT tm.type, w.name, w.label, wt.tid, wt.state_name, wt.target_state_name FROM workflow_type_map tm LEFT JOIN workflows w ON tm.workflow_name = w.name LEFT JOIN workflow_states ws ON w.name = ws.workflow_name LEFT JOIN workflow_transitions wt ON ws.name = wt.state_name WHERE wt.target_state_name IS NOT NULL ORDER BY tm.type, ws.weight in sites/all/modules/workflow/workflow.module on line 561.
Strangely enough, it doesn't not appear on the workflow config home page (but does appear on sub-pages).
Comments
On a seperate note
The instructions said to disable views_content, but the status report is reporting a problem because it's disabled.
Additionally
I took a more detailed approach and enabled each one by one, then cleared the cached to see if the error appeared. It showed back up when I had all the others enabled, and then enabled OP Default Workflow.
views_content problem was
views_content problem was fixed and should be gone once you clear cache.
I will have to get back to you re: the workflow problem.
Thank you
.............................................
http://twitter.com/inadarei
workflow SQL error
Hi!
I think the error has to do with the column name being "node_type" and not "type" in lines 546 and 556 in modules/workflow/workflow.module:
It also appears some lines under this again.
Yeah! That's the fix!
This solved my problem. Good to know that the key to the solution was within the drupal error message. Sometimes, the sight of those error messages are so depressing I don't get to even read the content!!! Went into workflow.module, replaced all 'tm.type' with 'tm.node_type' (4 occurrences), cleared my cache, ran cron & voila, my clean site look was back. Thanks @grahamtk...
Chill Pill
Yep that did fix it but is it
Yep that did fix it but is it going to have some consequence? Im on a dev site so its no biggie at the moment.
Cheers for the quick fix.
Hmm .. getting another error
Hmm .. getting another error now. When I change a state and save the form, it works but throws this error on a WSOD. lol
Fatal error: Call to undefined function workflow_get_transition_id() in /vol/www/site.mesite.net/sites/all/modules/workflow/workflow.module on line 747Is the workflow feature
Is the workflow feature really needed? I don't think this site wants it, so since it's creating problems, I'm wondering if I can just disable all the modules completely.
I was also wondering what Editor's Choice was?
irakli, Any update on the
irakli,
Any update on the workflow error...??
Muhammad Qandeel Aslam
http://qandeelaslam.com
I have just upgraded from 2.2
I have just upgraded from 2.2 to 2.3RC1 and have the exact same problem with the workflow module.
user warning: Unknown column 'tm.type' in 'field list' query: workflow_hook_info /* USER : workflow_hook_info */ SELECT tm.type, w.name, w.label, wt.tid, wt.state_name, wt.target_state_name FROM workflow_type_map tm LEFT JOIN workflows w ON tm.workflow_name = w.name LEFT JOIN workflow_states ws ON w.name = ws.workflow_name LEFT JOIN workflow_transitions wt ON ws.name = wt.state_name WHERE wt.target_state_name IS NOT NULL ORDER BY tm.type, ws.weight in /path/to/sites/all/modules/workflow/workflow.module on line 561.where
USER is either the logged in user or the guest/Anonymous user
Apart from a few minor errors, the upgrade was smooth. Thanks irakli and co. for their hard work.
sTattler.com
upgrade from 2.2
updated from 2.2 also, and encountered the same workflow issue.
tried grahamtk fix, but the consequnces were that I wasn't able to publish, and I had to disable the workflow altogather.
Overall smooth process - too bad the workflow doesn't work. Thanks irakli and team for their work.
http://mainstreet.eshore.ca
Dont do that
Workflow is a simple module to use ... undo the "fix" (from above) better known as a (DONT DO IT!) Hack in the workflow module.. Then Disable the Open Publish WorkFlow Feature. Then since workflow is so damn simple, create your own workflows .. it takes a couple min.
Cheers!
why not? :)
what I did was only replacing nonexisting column-names from the query, with the existing column name?
when I did my "fix" (or hack, whichever you prefer) which only was to solve an error there are no known solution for yet (so it seems to me)
it solved the problem, and I can publish just fine.
Hope you can shed some light on why you advice as you do? replacing a misspelled nonexistent column name in a query with the not misspelled existing column name seems to me as the only possible correct fix for this query?
If you want to alter a
If you want to alter a function or aspect of another module its usually better to override it in your own code. Hacking core or contrib will create a huge headache for you when those modules require updating. You'll have to keep track and repeat any hacks ad nauseam. Drupal way is to override in your code and/or supply the "fix" to the module maintainer for inclusion.
Im sure its something simple the OP folks missed or overlooked when releasing the latest release.... it will probably be fixed at some point. Though I couldn't tell you what the prob is since I decided to create my own workflows & dump the problematic OP workflow features.
Disabling Workflow Feature did not solve it
I had the feature disabled ... I even deleted the module folder! But still I get, whenever a workflow is active. The error only went away after I disabled and uninstalled Workflow.
And when I reinstalled it - even the DEV version - it came back...so I am flummoxed.
http://gamefacewebdesign.com
Indeed .. I believe it may
Indeed .. I believe it may currently be FUBAR, I messed with it too much & dumped it. Probably going to test it again tomorrow. I did notice when installing there were large amounts of errors posted to the screen... but other than workflow everything worked quite well so I carried on for more testing. Its a really cool install profile no doubts there! This is probably something simple missed in the latest release.