Support Forum
Support Forum
Offline
I've been having trouble with my site for a couple of days, can't figure out the root cause of the problem, at first I thought it was the total cache plugin but after removing and reinstalling all my plugins I suspect the problem is Simple Press - the trouble DID start after updating to the latest SP version now I think about it.
I tried reinstalling the SP plugin from scratch and I get the following error
Plugin could not be activated because it triggered a fatal error.
I get this error even if I have no other plugins installed.
This occurs with no other plugins installed. I tried installing an older version of SP I had on my hard drive and I could install and activate that but could not upgrade it.
HELP!
Offline
A 'fatal error' should definitely put an entry in your php error log. Can you take a look and see if you can find it? And if you are referring to the latest update being 5.5.10 then changes were really minimal.
 |
YELLOW
SWORDFISH
|
Offline
I've determined the problem isn't just with SP after all. it seems a bigger issue than that, I know they were talking about blocking access to xmlrpc.php but I'm not sure they went ahead and did that... waiting to hear back from them.
Offline
there are wp plugins for disabling xmlrpc.php... not sure what they were doing...
please let us know what you hear...
Visit Cruise Talk Central and Mr Papa's World
Offline
I don't think it's related to this issue because I'm still having trouble without SP even installed but FYI this is a msg my host sent me earlier.
We also found some errors on your PHP log file:
Aug 28 13:37:27 castle.wsynth.net ool www: PHP Warning - fopen(): http:// wrapper is disabled in the server configuration by allow_url_fopen=0 - file: /mysite.net/wp-content/sp-resources/forum-plugins/plupload/library/sp-plupload-components.php - line: 936 - function: fopen
Aug 28 13:37:27 castle.wsynth.net ool www: PHP Warning - fopen(http://mysite.net/wp-content/f.....Snow-2.gif): failed to open stream: no suitable wrapper could be found - file: /mysite.net/wp-content/sp-resources/forum-plugins/plupload/library/sp-plupload-components.php - line: 936 - function: fopen
Aug 28 13:37:27 castle.wsynth.net ool www: PHP Warning - fopen(http://mysite.net/wp-content/f.....Snow-2.gif): failed to open stream: no suitable wrapper could be found - file: /mysite.net/wp-content/sp-resources/forum-plugins/plupload/library/sp-plupload-components.php - line: 936 - function: spHandleShutdown
Those errors could be contributing to these issues you're experiencing and would be a good approach to fix them all as soon as possible.
You will want to verify with the plugin author that it does not require the exec() / exec.php or url_fopen functions, as both of those have been disabled on Synthesis hosting for security reasons.
We do support CURL as an alternative to url_fopen. Your plugin author should know if they are using these functions or not.
Offline
we typically dont use fopen() because a few hosts do disable it... looks like the fopen() was added to file uploader recently when a check was added for animated gifs... but wont impact what you are doing...
have to get with @yellow-swordfish and see if we can change that..
Visit Cruise Talk Central and Mr Papa's World
Offline
So your hoisting company has suddenly decided to turn off url_fopen support? That suggests this is the case.
And that is a first! While I sort of understand why they might want to do that I haven't come across any other host doing so and especially have not come across any host just turning stuff off without giving notice that it would happen so people can remove the calls.
We are going to have talk this over this end...
|
YELLOW
SWORDFISH
|
Offline
@mr-papa - I've not come across a host doing that as I said above. But actually that is just one use. There are others. The uploader one is easy enough to just remove as a temporary fix.
|
YELLOW
SWORDFISH
|
Offline
I don't know that they suddenly turned it off... it might have been done a while ago, I have no idea.
Offline
No - it must be sudden or that error would have triggered before. Curiously - it is actually coded so that any error should be ignored and things move on but that seems to have not happened here.
I can give you a quick fix to stop it being called of you can handle a small code edit?
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)