Each time I try to assign the newsletter block to an area in the Administrator - Blocks Section I get the fatal error below:
Fatal error: Class 'SoapClient' not found in /modules/campaignmonitor/campaignmonitor.module on line 382
Can anyone provide some guidance as to why I might be seeing this?
Comments
Comment #1
freeswell commentedi get the same error.
Comment #2
ssherriff commentedSorry, haven't been able to work on this module for awhile, I will have a look and see what is wrong.
Comment #3
ssherriff commentedHmm, I've tried to replicate this bug, but I can't seem to, can you give me any more information? Is this a fresh install and if you are using a custom theme, can you try it with Garland to see if you get the bug then?
Comment #4
rachelove commentedI receive this error in the Drupal 6 version of the Campaign Monitor module. When I assign the "Join Newsletter" block to a region, it then gives me that SOAP error for any page I try to go to.
Comment #5
ssherriff commentedOk, I'll have a look.
Comment #6
baronmunchowsen commented+1 for this - Drupal 6 version.
I developed site on local MAMP server with no issue, and migrated to test server (dreamhost) and fatal error encountered when trying to access block administration page:
Details:
Campaign Monitor Version: 6.x-1.1
Drupal Version: 6.5
Web Server: Apache/2.0.61 (Unix) PHP/4.4.7 mod_ssl/2.0.61 OpenSSL/0.9.7e mod_fastcgi/2.4.2 DAV/2 SVN/1.4.2
>>> edit <<<
Test server doesn't have SOAP extension enabled, localhost MAMP does. I'm guessing this module is reliant on SOAP beinng enabled? :)
Comment #7
ssherriff commentedOk baron, I can see what your problem is, the host is using php 4, I'm using the SOAP capabilities of php 5 for this module, so unfortunately you'll have to have php 5. I believe most hosts do allow you to choose, especially since I think people are being encouraged to use php 5 now anyway.
By the way, love your username.
Maybe this was the problem with the others as well?
Comment #8
ssherriff commentedMarking as fixed, as I have not heard anything for awhile.
Comment #9
baronmunchowsen commentedHi ssherriff - sorry for not responding. Yes the problem was php4/php5 related and thank you very much for your assistance!
Cheers!
Comment #10
ssherriff commentedNo problem, cheers.
Closing...