frm
Community Explorer
This is what a dev board is for (duplicate accounts for testing as well as signing up new accounts to ensure functionality of that didn't break).I might make a new member to see the view and permission are setup correctly but that as far as it goes.
You should have 2 instances at all times and copy/paste the files over after an upgrade to test new add ons and compatibility before upgrading them as they can, and often do, break things.
Better to test them out on a dev than have to roll back. Such a waste of time.
Sometimes, add ons do work, but you just haven't tested them enough to see, which kind of sucks. I had a recent add on that looked promising, tested it out, and it was working on the dev. So, I installed it on the live site. However, it took away the "quick reply" feature (as in when you type in a thread title, the message box wouldn't drop down, or the Elasticsearch similar threads wouldn't appear either), something that I didn't take notice of, but could have if I tested out forum posting, etc., more before pushing it live.
I was posting threads to test it, as it was an add on that added to threads, but I used the button to post threads too. So, it's important to check every way that could effect your forum. It's now disabled and I hope it gets fixed because it's a good add on.