SHREDDERz

Shalom,
PHP 7 does not allow for “break” statements outside of for, foreach, or switch statements. This was permissible in PHP 5.x but will now throw a fatal error. The getid3.lib.php file in the included getid3 library has “break” statement that causes a fatal error at line 285. Came across this error when clients had issues embedding their audio files in “sermons”. Eliminating line 285 led to normal function again.

Error message:

2016/07/25 12:20:51 [error] 22565#22565: *7144248 FastCGI sent in stderr:
"PHP message: PHP Fatal error:  'break' not in the 'loop' or 'switch' context in /chroot/home/domainname/public_html/wp-content/plugins/sermon-manager-for-wordpress/includes/getid3/getid3.lib.php on line 285" while reading response header from upstream,
client: 198.51.xxx.xxx,
server: domainname.org,
request: "POST /wp-admin/post.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "www.domainname.org",
referrer: "https://www.domainname.org/wp-admin/post.php?post=1030&action=edit"

Jacob

Nice work, Chad. Quick fix.

Same here. Update breaks on failed require.

Seems like it might be more honest if you post a message to your front page plugin description, changelog, and FAQ page that clearly states this is not the plugin previously associated with the same WordPress slug id.

This seems necessary due to the fact that WordPress users of the other plugin will be seeing notifications that prompt them to update to the “new version” of the plugin. This update would actually lead them to installing your plugin. There is clearly an incentive for you to do otherwise (i.e. not post the notification) but I hope you consider placing such a disclaimer in some prominent location of your plugin description.

Why is this marked resolved? Why is this WordPress plugin slug now associated with a different plugin?

Yes. It appears that the plugin is no longer associated with the WordPress file-manager slug id. What’s going on?