The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Well, this is not going so well… I logged in and activated the plugin this morning and now all I get is the error message. Never seen anything like this. Could I also get an FTP login? That way I can manually deactivate the plugin when working to figure out what is going on.
I have uninstalled the plugin so that the site will load at present.
Thanks, I’ll take a look at this on Monday.
Of, note… When I was commenting out the code using the WordPress plugin editor, the same would happen to me. But after a minute or two the site would come back on its own. It is curious that using the WordPress plugin editor (which has nothing to do with Connections) would cause the same issue.
Could you try something? It is possible that the memory allocated to PHP is being exhausted and that could be the root cause of the issue. Normally this results in the “white screen of death” or a memory exceeded error and not a server error. But I did notice that you are running a Windows server so the error results could be different. Can you try increasing this to 256M. That should be way more than enough.
Ok, I have this sorted for you. What it ended up being was an open_basedir error. Linux servers throw a relevant error message. It seems IIS simply throws the server 500 error, could simply be the way it is configured. Any way, not having an actual error was not too helpful. Once I figured out the source of the error I was able to make tweaks to the template scanning code to better deal with servers that open_basedir paths set.
You cannot reply to this support topic. Please open your own support topic.