I'm not sure if this has been taken out from the 'edit' tab, but even in the Worflow tab I do not have the ability to advance from the (creation) state to the other states I have setup.

Nothing about the workflow that I setup is in the 'edit' tab, and in the 'workflow' tab all I see is "Current state: (creation)" and a Submit button, along with an empty Worflow History table.

When I press the Submit button I get the following errors:
warning: Illegal offset type in isset or empty in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1150.
warning: Illegal offset type in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1151.
warning: Illegal offset type in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1154.
warning: Illegal offset type in isset or empty in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1150.
warning: Illegal offset type in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1151.
warning: Illegal offset type in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1154.

Considering I didn't have an option to select a ratio field to move from (creation) to the 'edit' state, I'd half expect an error, because I didn't tell it to advance in the workflow.

Any ideas? The installation of both Actions and Workflow went smoothly from what I could tell.

Thanks!

Comments

gschinkel’s picture

gschinkel commented

I had this same problem, but for me it just happened with content I created before assigning a workflow to the node type. This is a documented problem:

http://drupal.org/node/116205

Maybe you are experiencing the same problem? Try creating new content. Can you change the workflow states then?

d0t101101’s picture

d0t101101 commented

I'm experiencing the same problem too, except with an additional pathauto error:

* warning: Illegal offset type in isset or empty in /var/www/modules/taxonomy/taxonomy.module on line 1150.
* warning: Illegal offset type in /var/www/modules/taxonomy/taxonomy.module on line 1151.
* warning: Illegal offset type in /var/www/modules/taxonomy/taxonomy.module on line 1154.
* : Object of class stdClass could not be converted to string in /var/www/modules/pathauto/pathauto_node.inc on line 223.
* warning: Illegal offset type in isset or empty in /var/www/modules/taxonomy/taxonomy.module on line 1150.
* warning: Illegal offset type in /var/www/modules/taxonomy/taxonomy.module on line 1151.
* warning: Illegal offset type in /var/www/modules/taxonomy/taxonomy.module on line 1154.

This occurs only when taxonomy is enabled for that particular content type. Disable taxonomy (through categories), and the error goes away. The state change DOES take effect even after the above error... I receive this error with both new and old content, so i'm uncertain if the suggested fix in the last post would help.

I'll be sure to post the solution here once found. Any help would be greatly appreciated.

.

d0t101101’s picture

d0t101101 commented
Version: 5.x-1.0 » 5.x-1.1

Forgot to mention, I'm having this problem with the latest Drupal 5.1 and Workflow 5.x-1.1. All other modules are fully up to date.

.

d0t101101’s picture

d0t101101 commented

"The state change DOES take effect even after the above error"

After looking into this problem further, using views, the initial workflow state change does not take full effect at creation time (and there is no error). For example, looking at the workflow tab, upon creation the state is shown as changed from '(creation)' to 'submitted'... However this submitted state is not yet filterable using views. After opening the node, and manually setting the state again to submitted, (ie Submitted > Submitted) the view behaves as expected, allowing me to filter based on the state. Manually setting the state spits out the above error every time while taxonomy is enabled. The manual state change still works, just returns an error.

Glad to help if there are any questions.
.

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (won't fix)

Hi,

With the release of Drupal 7, Drupal 5 is no longer receiving security updates, reviews, or development from many contributed modules. Since 5 is now considered a depreciated version, you really should seriously look into upgrading to Drupal 6 or 7. The newer versions of Drupal work better, have more support, and will be safer (literally! security patches!) for your website. We are currently working on a new release for Workflow to Drupal 7. In light of that, further support for Drupal 5 issues is infeasible at the moment. Please consider upgrading to Drupal 6 or 7 in the near future - you'll be glad you did.

- Bastlynn