I have WSOD happening with a custom module which has the target form in its own file. I'm using the 6.x-2.0 version.
This is a bug which was marked as fixed in the 6.x-2.0 branch, but still not released: #480472: ahah_helper_render doesn't include required page file properly

Could you please make a bugfix release?

Comments

Assigned:Unassigned» Wim Leers
Status:Active» Fixed

Apparently the real original issue was #415560: ['#ahah_helper']['#file'] is non-existent!. But wholeheartedly agreed. Done: http://drupal.org/node/888824

Thanks a lot!

Status:Fixed» Closed (fixed)

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

Status:Closed (fixed)» Needs review
StatusFileSize
new14.08 KB
new306 bytes
new345 bytes

requesting a new release from the 2.x-dev branch to resolve some more bugs present in version 2.1.
here's why...

the version in the CVS is identical to the 2.x-dev published... except the CVS it is dated from May, while the published is dated from Jully. this confused me at first, but it's okay.

however, the 2.1 version (which has bugs) is dated from August, and supersedes as the recommend version because a) it is a stable version and b) it is newer. so if you don't want bugs, you replace with the 2.x-dev version, but then you get reports of outdated module versions.

to resolve this, the 2.x-dev would have to be refreshed or a new 2.2 version would have to be published.

so i took the liberty of editing the .info files from the 2.x-dev version (which is stable and works fine IMO) and transform it into a 2.2 version. the tar.gz and info files are bellow.

So did you add these lines to the files or how were they generated?

; Information added by drupal.org packaging script on 2010-09-22
version = "6.x-2.2"
core = "6.x"
project = "ahah_helper"
datestamp = "1285224800"

Is it correct to only put them?

i generated the timestamps (23-sep-2010) with an online tool and then replaced that timestamp and the version.
no code changes, nothing else.

i don't know how the timestamps are generated when the module is published, but it guess that is dealt with automatically.

for a quick fix, just replace the module with the contents of the tar.gz file.

but it's up to the developer to publish the new version.

Status:Needs review» Closed (fixed)

I just published a new release http://drupal.org/node/1214872 with all reviewed fixes included.