January 6, 2012 at 3:36 am #5197TimboMember
Hello, I just purchased the estore plugin, but when i go to activate it through wordpress admin, the screen goes blank (the following appears in the address bar:
I have tried dowloading the zip file a second time and tried installing the plugin manually (as suggested elsewhere in this forum) as well as directly through wordpress (as suggested in your installation video). In both cases it crashes everything (screen goes blank) – I have tried waiting up to 10 mins, still nothing.
I am running this installation of wp (currently 3.2.1) locally under mamp.
Please advise.January 6, 2012 at 3:52 am #40442PeterMember
Local installs are hard for us to troubleshoot because there are so many factors which are dependent on your settings.
Having said that you should check your local apache server software logs or equivalent to see if you are getting any errors such 500 internal server error.
Also if you have other plugins currently active you should probably try deactivating all of them to see if this makes a difference too.January 8, 2012 at 12:56 am #40443TimboMember
I looked at my server log, and saw that i was getting this error:
sh: /usr/local/bin/zip: No such file or directory
I have then done some testing, switching off all other plugins befoire trying to activate the wp estore, and found that the one that’s causing the problem is wp emember (a plug in that you state is compatible with wp estore). Whichever of the two i activate first appears to work normally, but then as soon as i attempt to activate the second, the entire admin area displays a blank screen, even if i try to log in again. The only way i can get round this is to manually drag the offending plug in out of the folder. Then, when i refresh the plugins page, it tells me that that plugin has been deactivated, as the file no longer exists, and everything works normally again.
Even when the admin area goes kaput, the front end of the site appears to function normally. Also, I am no longer getting the error message in my apache log.
I appreciate what you are saying about my local settings, but it’s fairly common practice to develop a site locally before sending it live, so it should be possible to test all the plugins.January 8, 2012 at 1:18 am #40444wzpModerator
I’d like to clarify what @Peter said about “local installs.”
When you use a “localhost” setup to test your system, as opposed to an out-of-the-way test site on the Internet, it is difficult for us to provide support.
When you are using a test system that is on the Internet we can easily access, or if necessary log into, the system; to assist you.
When you use a “localhost” configuration, we are not able to directly access or log into the system; to assist you. Hence, we are forced into making assumptions and guessing about what the difficulties may actually be. Sometimes we get it right, sometimes not.
With that said, I’d like to make a few basic recommendations…
Because you are using a localhost, there is no real point to “uploading” the plugins. Just copy the contents of the zip files into the wp-contents/plugins directory.
I also think, that because of the error message you last described, that maybe… and I’m not 100% sure, because I can’t access your localhost, that some additional configuration settings for WordPress still need to be done.
- You must be logged in to reply to this topic.