Case 1:
user submits node with image in body and teaser--->workflow changes to published--->log say 'node published & saved'.
Fact: Node is not published, workflow has published state, action not working?
Case 2:
User submits node without image--->workflow changes to published--->node gets publised.
Fact: Node got published without issue
Note: This only happens with 1 certain content type...
Case 3: Change the states to there orginal names--->submit node with image--->workflow changes to published--->node gets publised..
In the first two cases the state names where changed, when i changed them back to there orginal ones, all is fine..
Since i don't know if this is a workflow issue and or a action problem, i'll post it here..
Comments
Comment #1
Bastlynn commentedWithout knowing what your configuration is, I can't really say what's going on. I'm going to need a bit more information to work with here.
Be careful not to mix up the Workflow radio box options with the standard Drupal workflow published / unpublished options.
Otherwise, screenshots or more info on your configuration would be really useful.
Comment #2
demon326 commentedHi, thanks for the respons! i'll try to explain it to you:
I have three state names:
1. Ready for review(node gets this state when its submited to the DB)
2. additional work needed
3. Published(Actions publishes the node)
-------------------------------------------------
Certain content types just won't publish the node, though the action has been completed(node has been triggerd set to 'published' and reported to be successful) but it never publishes.
after days of searching i found out that when a state name gets renamed, the system 'bugs'. on my drupal website iam using dutch for the interface and i do have a state called 'published', but drupal translates it to 'gepubliceerd' and then the problems start, some content types get published without any trouble.
Mostly because they have a image in the node and teaser, set by the imce module..
As seen above, the state got changed and the trigger happens, but the node won't get published.
In short:
Certain node types don't have the problem described above, others do have it; the problem is that the trigger won't happen, althoug the logs say that actions has set the node to be published, but it still appears offline.
For now where using the 'publish content' module as workaround, but thats no solution...
Don't even know if this is problem of the workflow, but i need to start somewhere :)
Comment #3
johnvThe response in #2 deserves some investigation.
Comment #4
johnvCan we close this issue? No one else seems to have this problem, and D6 version is not maintained anymore. D7 is very different.