FATAL ERROR on updating

[kimberleyb]

Cannot access private property plgSystembfstop::$app in /home/accessib/public_html/libraries/joomla/plugin/plugin.php on line 97

front and back end are completely shut down with the joomla 3.1.4 update

[codeling]

I have no access to a PC at the moment, I will look into it later today. Doesn't sound familiar at all though.
It should help to manually disabling the plugin by going into your Joomla site e.g. via ftp and rename or move the file plugins/system/bfstop/bfstop.php

[kimberleyb]

Thanks - that got the admin to appear but no front end - a 500 error for a missing template - but no changes to it at all, just the update that crashed - I appreciate the help

[codeling]

I suppose something went wrong in the Joomla update itself. Maybe try a manual upgrade?

[bkdr]

Hi, problem occurs when you upgrade to 3.1.4. When I reinstalled 3.1.1 there was no error. Also I had not updated to 0.9.11 so this could also cause the problem with the update. Did kimberlyk have the current version before updating? Hope this helps.

[codeling]

Unfortunately I will now not be able to look into it before Monday.
For the moment, thanks for the information!
@bkdr Did you see the same error as kimberleyb?

The error message from the initial post sounds like there is some incompatibility introduced with Joomla 3.1.4 (but I'm not familiar with the 3.1.4 or the changes it introduced so I really can't say anything specific at the moment).
The 0.9.11 version however does not contain any special adaptations regarding Joomla so I doubt that using that version will change something. Which version did you (@bkdr) use when you had problems?

[jazzmang]

Same problem occurred with me.

I had a similar problem with sites using older version of adminexile extension as well. In that case, I had to upgrade to a newer version first and then Joomla.

If I remove bfstop first, it upgrades fine. If I try to install bfstop again after 3.1.4 is installed, it breaks it again with similar results.

My sites running Joomla 2.5.x upgrade just fine to version 2.5.13 sites (and they are all using bfstop).

Seems unique to 3.1.14.

It would ha

[LLadd]

Have been testing the issue with restored backups of my site with the following results:

1. Upgrade to Joomla 3.1.4 fails with error in first post with bfstop installed if in configuration.php error reporting is set to maximum (public $error_reporting = 'maximum';), or displays blank page if error reporting is left on default. Frontend shows blank page.

2. Upgrade to Joomla 3.1.4 succeeds if bfstop is first uninstalled.

3. Installing bfstop (tested both 0.9.11 and 0.9.10.2) on Joomla 3.1.4 succeeds, but the same error is encountered as soon as the plugin is enabled in plugin manager.

Hope this helps track it down.

[codeling]

Thanks for the detailed tests, and sorry for any inconvenience this has caused!
Unfortunately I will only have time to look into this earliest on Monday.
If anybody else should have time to take a look, Pull requests are more than welcome!

[codeling]

It turns out the problem was caused by a new "feature" in Joomla 3.1.4 (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=31205).
There is a fix in master now to make bfstop work again on 3.1.4 (see the comment above). If you absolutely need the fix now, check out the descriptions in the wiki on how to get the latest development version at https://github.com/codeling/bfstop/wiki/Specific%20Versions#latest-development-snapshot). Be warned though that this version is not well tested!
The fix will in any case be included in the upcoming version 1.0.