campaign monitor issue

If you have the possibility to access php.ini and enable error reporting in PHP, you should get an error message saying what went wrong. It's hard to help you without more information, but my guess would be that you should set your memory limit in PHP to 192M or more.

If the PHP process runs out of memory or any other problems and error reporting is not enabled in php.ini. It will always return a 500 internal server error header.

Have you looked in your Apache error log (if you are using Apache) and the PHP log file you can define in php.ini. When PHP goes down (WSOD) it normally writes something in the Apache error log.

Hi there, I have the same problem on my Drupal installation (on MAMP), try to save api key and client id and get a blank page. I checked my Apache error log and PHP log file but cannot find a solution. Did anyone here find it? Please I need your help.
Thanks!

We're getting the same problem. Can't save the API keys, just get a blank page.

Our memory limit is already huge, and it's instantly going to a blank page, which is unusual for a memory limit issue.

It's not giving any error or server response, just a completely blank page.

Have you tried inserting the API key and saving on a site/server with xdebug active and error reporting enabled. I have a hard time looking into this issue as I'm not able to reproduce the problem on my servers.

I had the same problem (white screen after inserting the api key) when I forgot placing the correct files (http://github.com/campaignmonitor/createsend-php) in the libraries folder.
After putting the files in the libraries folder, everything went fine…

Had same issue, not sure if it's an issue with the verbiage in README.txt file. The patch is the suggested change, I also think validation checks should be done via code but my standard way to do this validation is via hook_requirements within .install file. When writing the suggested patch for hook_requirements I started to see the reason why this wasn't implemented.

Further code investigation found the following doesn't seem to fire correctly (line 135 within campaignmonitor.class.inc):

    if (!$this->libraryPath) {
      drupal_set_message(t('The Campaign Monitor PHP integration library was not detected, please see the README for information about installing the library.'), 'error', FALSE);
    }

I have updated the readme with the patch. Thanks.

When the library is not installed I get the expected message in the administration interface.

Hi @cableman0408 - I personally didn't see that message execute on my campaign monitor admin screen. I'll take a closer look and see what reproduces the error when I have the chance.

Hello Everyone!
I have same issue
When i save the API and Client Key , i got the blank page instead of success page.
What is the problem?

Already, I bought premium account on the campaign monitor service.
Is there anyone who can help me urgently?

Thanks!

rtrb

Hi Guys, i have spent hours to debug the issue of white screen after submitting API and CLientID and found the solution.

In a nutshell, the solution is to disable any other module that is using Campaignmonitor API other then the Campainmonitor Module itself. Try disabling that conflicting module and it should work. if it still does not then you have to try to find out which module is the culprit one.

And here is how i did and you can do the same way to rectify the problem

First step is to go to your site/modules/campaignmonitor/lib/campaignmonitor.class.inc, open the file.
Trace the function "private function libraryLoad($file)" and remove the @ sign from the beginning of line 154.
So that @require_once $this->libraryPath . '/' . $file;
Becomes require_once $this->libraryPath . '/' . $file;

Now you should starting looking the errors and will see errors like "can not redeclare class cs_clients_rest" already declared in site/module/yourculpritmodule/file.php.inc.

I hope it helps, let me know if further need help.

FWIW this issue was fixed for me in the 7.x-1.0 release by simply copying the library files into sites/all/libraries/campaignmonitor. Be careful if you clone that directory from Github as per the README as it may conflict with your existing GIT repo and be left out of commits/pushes.

It would be ideal to have the page report something a little more useful than a WSOD, of for the module to not allow further configuration if the library isn't detected.

Drupal 7 is no longer supported.
Closing as outdated.