Error 500 upon activation

Turante / livepress

Automatically exported from code.google.com/p/livepress

1 stars 0 forks source link

Error 500 upon activation #48

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Upgrade to latest wordpress, version 2.8.4
2. Activate plugin

What is the expected output? What do you see instead?

Expected output is for it to work.  Instead I get:

"Error 500!

/wp-admin/plugins.php
Internal Server Error!"

What version of the product are you using? On what operating system?

Version 2.1.9.  Debian Linux.

Please provide any additional information below.

This had been a working install prior to the security update to Wordpress

Original issue reported on code.google.com by adamcher...@gmail.com on 8 Sep 2009 at 9:00

GoogleCodeExporter commented 9 years ago

I just all the sudden started having this same problem after running 2.8.4 for a
couple weeks, the issue just started today.  If I disable the plugin by 
removing it
from my plugin folder things work again, but every time I activate it goes back 
to
the 500 error.

Original comment by dan...@prcnetworks.com on 11 Sep 2009 at 4:32

GoogleCodeExporter commented 9 years ago

Hello,

Sorry you are having this trouble.  Can you turn on php debugging and then give 
me
the output?  thanks!

-Tania

Original comment by tania%digsite.net@gtempaccount.com on 12 Sep 2009 at 2:37

GoogleCodeExporter commented 9 years ago

I just enabled logging and reloaded the *same* copy of the plug-in that I had 
problems with and everything is 
working fine now.  No 500 errors.  

Does something with the plugin depend on LJ's availability?

Original comment by adamcher...@gmail.com on 12 Sep 2009 at 4:41

GoogleCodeExporter commented 9 years ago

I have the same question about LJ's availability because I was having this 
problem
while Live Journal's website was running extremely slow.  Doesn't really make 
sense
why a plugin that I'm not even using (in the sense it should only communicate 
when
I'm actually posting) at the time would cause my site to go down.

Original comment by dan...@prcnetworks.com on 14 Sep 2009 at 7:52

GoogleCodeExporter commented 9 years ago

Yes, LP will stop working if LJ becomes unavailable.  But This was fixed in 
2.1.9.

Since you claim that it's still breaking, I am going to revisit the issue and 
go a
step further.  Have LP notify you that LJ is down and your attempted crosspost 
won't
be successful.

-T

Original comment by tania%digsite.net@gtempaccount.com on 9 Mar 2010 at 6:49

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 12:41

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 3:20

GoogleCodeExporter commented 9 years ago

Confirmed this is no longer a problem as of 2.1.11 / 2.1.12.

-T

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 6:10

Changed state: Ready
Added labels: Milestone-Release2.1.12

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 20 Mar 2010 at 12:49

Added labels: Milestone-Release2.2.0
Removed labels: Milestone-Release2.1.12

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 23 Mar 2010 at 1:11

Changed state: Released

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 26 Mar 2010 at 7:25

Changed state: Verified