TOPIC: using on localhost

I installed CMandrill (2.0.1) on two different 2.5 installations on my localhost. Each time, after I entered by Mandrill API key, the options popup said I was successful, but when I closed the options popup, the component displayed a blank white screen. I changed the URL to get back to an admin page, enabled the plugin, clicked on the component dropdown of CMandrill, and again I had nothing what a blank white screen (with no HTML in the source).

Then I installed CMandrill on a 2.5 test site sitting on a web server. This time, after entering the API key, I was able to see the CMandrill dashboard as demonstrated in the video.

Does CMandrill not work on a WAMP/localhost (where Joomla's Mailer option does not work)? Or is it likely that it will if I only changed some setting?

Hey Randy,
what are you holding? Is that a gold fish? Or a jug of beer with meat in it

About CMandrill - of course that you can use it on localhost ( I do so on my dev. machine). The white screen indicates that there is a PHP error that happens, but error reporting is suppressed.

Go to your joomla's global config and set error reporting to dev. level. After that when you try to send a mail you should see the error that happens.

Cheers,
Daniel

Thanks for the explanation. I should have thought of turning up the error messages. And I'm glad I can run CMandrill as I develop on a localhost/WAMP installation.

As for my Avatar... In 2006 I was in the Amazon Rainforest on assignment for an aquarium magazine, exploring on an expedition with a research organization. I was holding up a bag of a desirable species that I netted in a tiny side stream. The river system is classified as "black water" due to the high saturation of tanins in the water - tinting it deep amber. Though the avatar does not explain the story behind it, it reminds me of the satisfaction I get from exploration and discovery.

I returned to this issue and discovered the problem - and a solution that I thought would be valuable to share.

The error occurred in a helper class at the line calling curl_init(). Apparently cURL does not work correctly on WAMP and php 5.4.3. The solution was to download a new version of php_curl.dll (I did so here: coderwall.com/p/9c_j6w ), replace my current version of this file with the new one, and restart WAMP. Additionally, I had to open php.ini and uncomment the line
extension=php_curl.dll

That solved my problem.