After upgrading to the latest version my workflows stopped existing.
The workflows are still defined in the database, but not visible in the GUI.

Comments

egouleau’s picture

I've just installed the latest version today and i got exactly the same pb :/

nancydru’s picture

Priority: Critical » Major

Have you run update.php and cleared the cache?

dob_’s picture

Priority: Major » Critical

Yes of course.

nancydru’s picture

Priority: Critical » Major

I don't recognize "critical" as a priority in this module.

nancydru’s picture

7.x-1.0 was before my time. I tried to set up a test, but it converted fine. Can you give me a better description of what you had, please?

nancydru’s picture

Status: Active » Postponed (maintainer needs more info)

I just set this up again. I created a site with 7.x-1.0 main module and Admin UI and added a workflow (boy, was that old UI ugly!). I set up two nodes and transitioned them. Then I dropped the 7.x-1.x-dev code on top of it and ran update.php. The workflow is still there and functioning correctly.

Did you do anything different from this?

levsoroka’s picture

I am having similar issue. I have updated from 7.x-1.0 to 7.x-1.1. Running Drupal 7.16.
My workflows were still there but there is a bug on form submit. Exactly on "Save Configurations" while editing or adding new states, May be related to adding new states. I tried few times installing and uninstalling module. Cleared cache and etc thought that may be related to it. But I am still getting "Page not found error". In other words that workflow is being removed at some point.

liquidcms’s picture

Status: Postponed (maintainer needs more info) » Active

yes, update from 1.0 to 1.1 appears to be busted.

i had 1.0 working fine on a site for while, want to try og_workflow so just upgraded workflow to 1.1. the ui seems to be missing even though the workflow appears to still be here - possibly there is UI for this somewhere i haven't stumbled upon yet?

http://screencast.com/t/oJXeu9o7Z7h

levsoroka’s picture

Its up top, to the right of add new workflow link, You have it called status. Might be why its hard to distinguish

liquidcms’s picture

lol.. yup, there it is. thanks.. and looks great!!

nancydru’s picture

Yes, the UI has undergone a lot of change. The workflow names will be at the top of the page. Click on the name and you will see the rest of the stuff - but also broken out. This should actually make more sense than one big page with a confusing plethora of fields.

I do highly recommend the current dev - there are fixes and new features in it. 7.x-1.2 will roll out soon.

nancydru’s picture

@levsoroka: you haven't changed the name of the "(creation)" state, have you? That is a known problem and the current dev will not allow you to do that.

nancydru’s picture

Status: Active » Closed (works as designed)

No further update.

audealexandre’s picture

Status: Closed (works as designed) » Active

Hi,

I reopen this post because I have exactly the same problem as #7.
"My workflows were still there but there is a bug on form submit. Exactly on "Save Configurations" while editing or adding new states, May be related to adding new states. I tried few times installing and uninstalling module. Cleared cache and etc thought that may be related to it. But I am still getting "Page not found error". In other words that workflow is being removed at some point."

The only thing I have done is adding one new state (unactive) and clic on "save" and then I arrived on the error page and the workflow is not visible anywhere (but still there in the database). The other workflow I didn't modify is still there.

Thanks in advance for your help,

audealexandre’s picture

Some more info:

The problem seems really related to the adding of a new state: I created a new workflow named "test". Then I added a new state to it and when I clicked "save the configuration", I got the error 404 page, and the workflow disapeared from the UI.

nancydru’s picture

Did you change the "(creation)" state name?

audealexandre’s picture

No, not at all, I just created a new state.

audealexandre’s picture

Any idea for the resolution of the problem?

Thanks in advance,

nancydru’s picture

Not at the moment. Are you using the latest dev release?

derekw’s picture

Change your admin theme and see if they show up. I found that in Rubik the created workflow names were not floated, so they were hidden behind the Content Type mapping table. (If you view the HTML source on the page you'll see they are there.)

audealexandre’s picture

Hi, thanks for answering. I checked the source code of the html page but unfortunetely, the missing workflow ("Edition" is not present. Hereunder the html code, with the other workflow ("reservation-de-salle") still present.

<div id="page">
          <div class="tabs-secondary clearfix"></div>
    
    <div id="content" class="clearfix">
      <div class="element-invisible"><a id="main-content"></a></div>
                          <div class="region region-content">
    <div id="block-system-main" class="block block-system">

    
  <div class="content">
    <form action="/libnetaude/admin/config/workflow/workflow" method="post" id="workflow-admin-ui-types-form" accept-charset="UTF-8"><div><ul class="inline action-links"><li class="add-workflow first"><a href="/libnetaude/admin/config/workflow/workflow/add" alt="Add a new workflow" title="Add a new workflow">Ajouter un processus</a></li>
<li class="workflow-reservation-salle last"><a href="/libnetaude/admin/config/workflow/workflow/2" alt="Work with workflow-reservation-salle" title="Work with workflow-reservation-salle">workflow-reservation-salle</a></li>
</ul><div id="edit-help" class="form-item form-type-item">
  <label for="edit-help"><h3>Content Type Mapping</h3> </label>

NB: I use the default admin theme.

audealexandre’s picture

Hi,

I installed the latest dev version and the problem doesn't appear anymore (I can create a new state for a workflow). Still, the 2 workflows which were missing are still missing.... any idea of a way I can display them again (a property in the database?) ?

I will do a bit more testing later.

Thanks in advance,

Aude

nancydru’s picture

Could you dump the workflow_states table for me so I can see what's happened. I don't see how it could happen unless there are no states defined, including "(creation)".

You can also change the query at line 1032 in workflow.module

  $query = "SELECT w.wid, w.name, w.tab_roles, w.options, s.sid AS creation_state "
    . "FROM {workflows} w "
    . "INNER JOIN {workflow_states} s ON s.wid = w.wid "
    . "WHERE s.sysid = :sysid";
    ;

Change the "INNER JOIN" to "LEFT JOIN" and see what happens. Change it back when you get running again.

audealexandre’s picture

StatusFileSize
new1.58 KB
new1.79 KB

Hi,

Here the table dump (and also the workflow table). Really, all the workflows have a "creation" state. Could the problem be related to the language ? (I didn't change myself the creation state but it is translated in the table).
Unfortunately, changing to LEFT JOIN didn't change anything in the display.
For info:
- I have only activated the following modules:
workflow
workflow UI
workflow rules
workflow views
Should I test with other configurations?

Thanks again,

audealexandre’s picture

Hi, I think I found the problem (but not the cause): in the workflow_state table, the sysid field was at 0 for the creation state of the workflow which didn't appear anymore; for the creation state of the other workflows, it was at 1. So I changed the value in the table from 0 to 1 and the workflow now appears in the interface.

nancydru’s picture

That would definitely do it. I'm not happy with the "(creation)" state name being translated, but you seem to be okay with it.

I'll look at the code again to see if I can figure out why sysid is 0, but I'm guessing it was a bug in 7.x-1.1 that is now fixed. I have never seen that happen in all my testing.

nancydru’s picture

Assigned: Unassigned » nancydru
Status: Active » Fixed

I did find a circumstance that could result in the sysid value being wrong. Fix committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.