Here is more information to help you troubleshoot this, and it is SAD that a user has to be doing that here....

Get this:
- I have the Default Menu on the main config page set to Easydiscuss Toolbar (logical)
- I have Custom Menu setting on the main config page set to Yes, with the default selections for the respective SI extensions, so the Easydiscuss pages will have the Easydiscuss Toolbar (logical, all standard)
- On the Easydiscuss tab, I have the Login set to OFF, and yet the Login shows on the ED pages on my site.

Here comes the kicker:
- When I turn the Login option On or OFF on the EasyBlog tab, the actual Login icon on the EASYDISCUSS pages on my site does turn on or off.....

How your new update (without a changelog) can somehow create a cross connect between EasyBlog and EasyDiscuss settings is SLOPPY software development.

Also would not expect this on v 1.0.14 of this module......

But at least with the friendly help here from a subscriber, you can hopefully correct this mistake.

Sorry if I am a little critical here, but between the recurring messes that the Joomla team is making, now with the flawed update process to v4.2 for example, and the whole upgrade from 3.x to 4.x to begin with, it really takes the fun out of "updating".

I would prefer not to have to be cautious about these things.

Another thing that I REALLY dislike is the lack of posting PRIOR versions on your site.

If we find an issue, such as what happened here to me, I would FAR PREFER to be able to quickly download the prior version and get things working again as I need them to.

I am very used to router firmware update sites where the WHOLE history of prior firmware is easily available. I think not having prior Joomla extensions easily downloadable is a major disservice to your clients and an easy improvement opportunity. Changelogs and versions should go hand in hand to enable the simple fixing of "updates" that do not work.

I suppose some "updates" modify database tables, but where possible, this should be an option IMO.

Hope to see the next "update" soon.

Thx

Hi Net-Config,

Thanks for your report and criticism on the issue. I have already logged this in our tracker so the devs are aware and can push a fix.

Hi Raymond, thanks for the prompt reply and understanding I was a little cranky when this happened....

Here is a suggestion that I think works very well.

Take a look at https://www.asuswrt-merlin.net/

This site is run by a terrific engineer who improves the standard Asus firmware for many common / current routers.

He has clear download areas for pre-Beta software, Beta and Release level software.

I'm sure your team is totally familiar with such a process, so not trying to show something innovative here - just that it is a good process.

With this setup, I can decide at which level I want to participate and update routers.

I have no issue when software is Alpha or Beta to support the QA process by installing it and reporting any issues.

Those discussions for this Merlin software happen here: https://www.snbforums.com/forums/asuswrt-merlin.42/

This obviously enables a sizeable group of enthusiasts to participate and test new software in THEIR environments and with their UNIQUE settings.

I wish StackIdeas would do something similar.

I think you would have much better insight in the quality of a new version after a sizeable group of users test it and tell you what they see. Between different hosters, core Joomla versions, PHP version, other extensions, package configurations, security settings, browser versions and extensions that do all sorts of stuff, the VARIABILTY of environments in which your software runs is endless and clearly more complex than images for routers are, which is more like "software in a box".

If you had published the Toolbar software as a Beta instead of a formal version, I would have understood the possibility of issues and reported the same information, but without getting frustrated about it.

When you publish software as "ready to go - here is the new version!", I am not really that accepting of very basic problems with it. It should just work as that is the whole point.

Also, I believe you would be able to create a real community of committed and understanding users who WANT YOU to be SUCCESSFUL with your products.

Right now, unless I am missing something, I think the feedback you get comes from a more random group of people that does not engage in discussions in the manner you see on SNBFORUMS.com as shown.

With very little extra effort and some more organization and management of files, changelogs and package versions along with some forum structuring, you could create a significantly better picture for your paying customers.

For a company that publishes "community focused" software, that would make a lot of sense and using the alpha-beta-release process would be an easy way to do just that!

Have a great weekend over there!

Thx, N-C

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

Just for your information, I have locked and marked this thread as resolved to avoid confusion in the future. Please start a new thread if you have any other issues in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.