Hi,
Both with version 7.x-1.0-beta3 as with the latest 7.x-1.x-dev i get a WSOD on:
admin/config/services/campaignmonitor/lists
and
admin/config/services/campaignmonitor/states

I tried with libraries version 7.x-1.0 as 7.x-2.0-alpha1

Using Drupal 7.8.
Nothing added to watchdog.
No errors in the httpd logs.

Any ideas?
TIA
Johan.

Comments

johanbeckers’s picture

johanbeckers commented

Seems that this module is causing even more problems.
When I try to create a new block: WSOD.
When I disable the campaignmonitor module everything is back to normal.

If anyone can give a hand here. I'm lost in the dark.
Thanks in advance,
Johan.

cableman0408’s picture

cableman0408 commented

Do you get any error messages in your web-server (Apache) log files. WSOD might suggest that you PHP process has failed.

How much memory do you give PHP in php.ini ?

johanbeckers’s picture

johanbeckers commented

Hi, Thanks for your reply!

Settings:
memory_limit = 128M
max_execution_time = 3600

Apache log: nothing

Any ideas :)

cableman0408’s picture

cableman0408 commented

I have not been able to recreate this issue... which version of PHP are you running ?

sxnc’s picture

sxnc commented

I actually had the same Problem here, did you check wether or not the Library contents inside the "campaignmonitor" folder are complete? If you did it locally following the README file and pushed it to a dev server, there's a good chance that git ignored the contents.

cableman0408’s picture

cableman0408 commented

I have fixed a problem with the lists page, which can return a WSOD if API keys have not be entered yet. But I'm not sure that this is related to the error mentioned here.

johanbeckers’s picture

johanbeckers commented
Status: Active » Fixed

Hi all ...
Sorry for my late reply, other project took my time.

However, the problem is solved and was due to the fact that not all files from github were in my libraries folder.
Tip: maybe a little check could be build that displays an error instead of a WSOD :)

Thanks for the help and hints!

Status: Fixed » Closed (fixed)

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