All sermons disappeared after update

Same problem here. I have combed through the settings and the knowledge base and can’t find anything about “output buffering”. Also, my sermons have disappeared.

Same here. I’m on hostgator and it doesn’t have output buffering enabled by default, and I don’t know how to turn it on, or whether even if I did it would cause other problems. What I need is an old version of the plugin to roll back to a working version, but I don’t know where to find that either.

OK, I’ve managed to roll back to 2.15.2 and all is well for now. You can find old versions by going to the plugin page here (i.e. click on sermon manager in the right column here), then on the right again click in advanced view, then scroll down to the developer section at the bottom where you will find a dropdown where you can download old versions.

Hope that helps.

Hi all,

Please update to Sermon Manager 2.15.5 (released a few moments ago), and the issue will be resolved.

What happened?

The error happened with good intentions – we wanted to disable some of Sermon Manager functionality, without breaking the whole website, for the users who do not have output buffering enabled.

What is output buffering?

Without output buffering (the default), your HTML is sent to the browser in pieces as PHP processes through your script. With output buffering, your HTML is stored in a variable and sent to the browser as one piece at the end of your script.

(source)

In simple English, output buffering allows us to take a bit of the page, process it or store it for later use, and output it at the moment we want (or we can decide to not output it at all, based on circumstances).

The output buffering is controlled by PHP, specifically, in the PHP’s configuration file named php.ini.

What happens when output buffering is disabled?

The problem occurs when the server does not have output buffering enabled, and in older versions, if we tried to use it without checking, the website would crash with an unrecoverable Fatal Error. So we basically tried to avoid that from happening, but we made a mistake somewhere in the code.

Verdict:

The check has been disabled until it is tested properly in future.

This topic will be closed for replies, but if someone has a similar issue, they can open a new topic.