I have searched the forums and found more than a few posts related to plugins giving off the “Plugin could not be activated because it triggered a fatal error.”
I also understand there is a canned response of “contact the author”.
What I want to know is how I can figure out what the fatal error is that it is throwing. I upgraded from modphp 4.4.x to cgi php 5.2.x and when I did this aLink started throwing session errors.
I deactivated the plugin and then tried to reactivate it. When I did this it gave me the “Plugin could not be activated because it triggered a fatal error.” problem.
Now I know aLink works just fine with php 5.2.x running wordpress 2.5 because I have it running on 2 other sites. The issue here is that the two other sites were always on php 5.2.x. The one site that was on php 4, that I upgraded, is the only one giving me problems so if I could some how find an error log (no errors are showing in the apache error_log, I assume because the error is caught?).
I deleted all the wp_options related to aLink and the aLink table then tried to activate it again. It correctly created everything but still ended up throwing the error.
So any idea how I can figure out what the actual error is that it it throwing? Some way to turn on a debug log?