I am attaching a patch which fixes multiple issues (uasort errors, submit buttons disapearing, fields disappearing from manage fields), and basically results in a moderately well working version of the wizard module. This patch is not very clean and is only intended as a temporary workaround, but I wanted to get it out there for anyone who wishes to use this module until a new version is released.

CommentFileSizeAuthor
wizard_fix.patch6.23 KBkoshea

Comments

loginsvariaditos’s picture

loginsvariaditos commented

Hello. I can´t apply the patch to the module. I have tried many different options on Windows Xp, and all of them failed or just didn´t know how to make them work.

Would anyone please would care about uploading the patched module?

Thanks!

loginsvariaditos’s picture

loginsvariaditos commented

Please, please help me!! I cannot patch the module. Please upload the patched version!
Thanks a lot

ms2011’s picture

ms2011 commented

Thanks koshea! It's great to see someone else taking interest and initiative with this module.

I have read through your patch; looks good from here. Just needs to be tested.

@loginsvariaditos: read: http://drupal.org/patch

loginsvariaditos’s picture

loginsvariaditos commented

I´ve tried that. Thank you. I´m just not getting the file patched

nathanraft’s picture

nathanraft commented

Can anyone varify that they have this working properly now with the new patch?

(btw...loginsvariaditos.. Just apply it by hand.. won't take but 10 min.)

Wouter Van den Bosch’s picture

Wouter Van den Bosch commented

Hya,

I've patched my version of wizard. I can now see the field in 'manage fields' but as soon as I go into node add and click a next button, I get a white screen of death. I'll go check my logs to see what it might be caused by.

Keep you posted.

Wouter Van den Bosch’s picture

Wouter Van den Bosch commented

The error was caused by another module and was unrelated to this module (at first sight).

Hence I can confirm this patch works just fine for me.

Wouter Van den Bosch’s picture

Wouter Van den Bosch commented

Hi again,

I just installed Wizard on my online development server and got an uasort error :

warning: uasort(): The argument should be an array in /.../modules/wizard/Wizard_Form.class.php on line 66.

It might be useful to know that I went back to my local install, changed my MAMP server from PHP5 to PHP4 and got the same error. Apparently wizard has some issues with PHP4, causing it to arrive with a bad argument at line 66.

Switching to PHP5 is no issue for me, but I thought I'd just let you know.

Cheers for a fine module by the way.

koshea’s picture

koshea commented

Wouter,

I'm unable to reproduce this, but I'm not surprised (this module is really a mess, although this isn't my original work, unless something else is out I'm hoping to build a replacement from scratch after the release of D6). Could you post all the fields you have on the form, including the wizard fields as they are listed on the manage fields page for the content type? Also, if you could add a line before line 66 in Wizard_Form.class.php such that the code reads:

    // Sort FAPI form elements by weight first.
    if (!isset($this->fapi_form['#sorted'])) {
      print_r($this->fapi_form);
      uasort($this->fapi_form, '_element_sort');
      $this->fapi_form['#sorted'] = TRUE;
    }

And post the output from that print_r, that may help me track down your problem.

Thanks,
kevin

no longer active 7’s picture

no longer active 7 commented

I am also having same problem as Wouter. After applying this patch it is showing me all the fields in manage fields.

But when we go on add content type it will directly jump to step 2 instead of step 1. And in edit multistep is not working.

Anyone looking into this. Please help.

Any development for drupal 6.

Thanks in advance.

pomliane’s picture

pomliane commented
Status: Needs work » Closed (won't fix)

This version of CCK Wizard is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.