I have installed and re-installed this modual. My company wants to integrate icontact with Drupal. So far, I'm having no luck.
The error i'm getting is :
The website cannot display the page
HTTP 500
Most likely causes:
The website is under maintenance.
The website has a programming error.
What you can try:
Refresh the page.
Go back to the previous page.
More information
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.
I have read through the other areas of the site about the mysterious 500 error, and I have tried everything that people have suggested to no luck.
I have tried changing the .htaccess file and deleteing it, but that didn't work.
I have tried adding bits and pieces of code, and that hasn't worked either.
I thought there were permission errors but that didn't work either.
I get that same error everytime.
If anyone knows anything that can help that would be great.
I've also emailed the hosting site which is media temple and they were no help either.
Comments
Comment #1
mediatemple commentedHi there. Sorry to see you're having trouble. Have you tried clearing the cache?
http://drupal.org/node/42055
Clearing the cache often clears up this issue on Drupal.
Comment #2
jonwithhtop commentedYes, I have tried clearing the cache a few times. hmm
I don't know what else to try. . .
Comment #3
jonwithhtop commentedMore information.
Media Temple provided this in the error log
PHP Fatal error: Call to a member function getResourceIds() on a non-object /sites/all/modules/icontact/icontact_ui/includes/icontact_ ui.accounts.inc on line 191, referer: http://www.htop.org/admin/build/modules
PHP Fatal error: Call to a member function getResourceIds() on a non-sites/all/modules/icontact/icontact_ui/includes/icontact_ ui.accounts.inc on line 191, referer: http://www.htop.org/admin
Comment #4
jonwithhtop commentedI had to register the api keys first before clicking on accounts. That fixed the issue. The api keys were listed at the bottom of the status report
Comment #6
john franklin commentedI'm sorry, no module should ever WSOD. If there is something missing, put up a warning or error message. Give the admin something to work with.
Comment #7
greenskin commentedFixed. Please try the latest dev release.
Comment #8
greenskin commentedComment #10
ryan.ryan commentedYea, if anyone else got to this thread because of a wsod when trying to save admin creds. Go to the status report page and put in the api key. The admin user login message should direct you there if it's going to pop-up when module is enabled.