This issue is orphaned - how to get it back?

I've had a couple requests for a D6 version of WPro3. Unfortunately, I am swamped at this minute and can't make the upgrade. However, the module isn't terribly complicated, and anyone with experience upgrading modules from D5 to D6 should be able to update it, without much WPro experience.

Sorry, I wish I could help.

I've made an attempt at upgrading the module to D6.
Everything is successful and it loads and runs fine except for one small bug.

If collapse.js is loading on the page as well it gets stuck in a loop and the page never displays (just a white screen).
It seems that the "wysiwygpro.js" file included with the module is not working the way it should to fix this bug.

Any ideas on how to fix this problem would be helpful so I can release the D6 version working 100%.

** edit **
I probably should make a new thread for this, but, it seems that if a WPro textarea is enabled within a fieldset the page dies.
Outside it's fine, but inside, even with the "wysiwgpro.js" script it dies.

(This is referring to explicitly D6 of course)

Fixed!!!

Explanation:

When using the 'hook_element' function, Drupal includes all child elements in the variable that gets passed through.
So to solve our problem of Drupal 6 collapsible fieldsets breaking any page that has a WPro enabled textarea within a collapsible fieldset, I've wrote a function that recursively searches the array of any 'fieldset' type element for a child element with an #id that matches an enabled WPro textarea.
When found it disables the collapsible funcitonality for that specific fieldset resulting in a fully functional D6 WPro module. (if you don't mind your WPro Editor in static fieldset).

I'll post my modified files once I figure out how to roll out CVS patches. (I've never done that before)

Thanks for putting the effort in to make this work. I'm glad to have the help.

If you'd rather avoid the patch process you can attach the zipped files and I'll add them to a new D6 branch.

Out of curiosity, how many changes were required to make this work in D6?

Thanks,
Chuck

I think this is a great solution for now, but I'd still like to see a long-term solution that allows for collapsible fieldsets and WPro to work well together. I'll speak with the guys at Vizimetrics to see if they can take a look at it.

Thanks again for your help, djalloway.

I also hate doing workarounds and would love this to be fixed the correct way.
Meanwhile I have come across one last bug and it is if you have WPro enabled on the block configure page.
I will solve this and then email you a zipped file of my code as well as what / where the changes are located.

The "Wysiwyg Pro" project page now says "Access denied", and we have no way to get this issue back to where it belongs.

Weird. Retitling.

It appears the project was unpublished due to un-solvable GPL violations.