Hi,
Do you have access to the Error Log? This will likely be in your web-server’s log directory.
A 500 error indicates that the web-server or PHP died before sending the page. Error log lines produced by the request that failed should help highlight where the problem lies.
The code for 0.8.0 successfully passed Continuous Integration testing on travis-ci.org so the problem is possibly specific to your server – the Error Log should help us diagnose better.
There a lot of error logs similar to this:
2016/04/07 22:10:53 [error] 8678#0: *3594438 FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot redeclare the_section_az_widget() (previously declared in /home/domain.tld/public_html/wp-content/plugins/a-z-listing/widgets/a-z-widget.php:117) in /home/domain.tld/public_html/wp-content/plugins/a-z-listing/widgets/az-widget.php on line 121" while reading response header from upstream, client: 162.211.65.254, server: domain.tld, request: "GET /privacy-policy/ HTTP/1.1", upstream: "fastcgi://unix:/home/domain.tld/php5-fpm.sock:", host: "domain.tld"
I can also send you the full logs file, if you want. Give me your email address.
ok, I see the problem. I renamed the widget file which means you now have two copies of the file due to uploading the new 0.8.0 without removing the previous version first. Remove the file “widgets/az-widget.php” and you should be set.
Okay, actually it was WordPress.com/ Jetpack’s auto update plugins option which auto upgraded the plugin on my site, which caused the problem.
I will take a look at the problem tomorrow.
I believe the zip-file that WordPress.org was serving had both the old and new files included. I’ve now re-rolled the release to fix the zip-file download. You should hopefully now be able to upgrade without problems.
