Upgrade to v5.0 killed my sidebery setup

[up-bpersons]

CSS styling no longer works as before, despite no change to the styles. Anyone else have this issue?

[zelch]

Are you coming from v4, or from one of the v5 release candidates?

[Elementari]

I also experienced some configuration data loss, and it caused considerable interruption of my workflow.
However the joy over the new release was much greater.

I would like to suggest that major upgrades could be rolled out as follows:
A pure "notication update" is rolled out 2 weeks prior to the actual update. The "notification update" will inform the user that a major automatic update is about to be rolled out on (date) at (time) (timezone).
The user can then disable automatic updates for Sideberry in FF Addons config (perhaps provide a quick explanation to users how to go there), thereby having full control about the update process.

I was anticipating that the v5 update would come with some config data loss so I had taken some screenshots of my configuration as a quick reference a week ago, thankfully (coincidence).

I did not experience tab data loss.

[mbnuqw]

A pure "notication update" is rolled out 2 weeks prior to the actual update. The "notification update" will inform the user that a major automatic update is about to be rolled out on (date) at (time) (timezone).
The user can then disable automatic updates for Sideberry in FF Addons config (perhaps provide a quick explanation to users how to go there), thereby having full control about the update process.

Yeah, I thought about it too late... Sorry.

[mbnuqw]

#1241 (comment)