Updates should not be released until properly tested. This is happening with almost every update of WPLMS which is disappointing - right after release there is always a major issue found.I'm not talking about small bugs. These are normal part of software development and always be here.
I suggest WPLMS developers should only release new updates as beta versions first and only when major bugs are fixed, release as stable versions. I used Moodle before which is a free open source software and never in 8 years there was a single issue in stable release that would break some functionality completely. WPLMS is a commercial product so instead of rushing out updates followed by releasing quick fixes and patches, then having to use custom CSS for everything, just get the beta versions out first. My custom CSS is now 5 kilometres long and will continue to grow forever this way because new styling issues (some even fixed previously) resurface.
Don't take me wrong, I love WPLMS. But it could be so much better than it already is. I want it to be the best learning CMS out there, I'm a big fan. That's why I'm writing this offering my input.
100% agree. WPLMS is a business taking clients money, and they should act like it. I've used the Enfold theme for over 3 years and never once had an issue. I look forward to their updates. WPLMS updates are like walking on egg shells with the numerous plugins. I take my business seriously. As should you WPLMS. Reinvest the money you're making into fixing product quality, please! You'll be glad you did. No more putting out fires.
You're absolutely correct and I agree with every statement. But on the other side, we get so so many queries on when are you releasing this , when this feature will be added. That we're pushed to release the features early and this is where we get the bugs. We've now started pushing updates by 24 hours. Even after the testing is complete, but as you can see in this particular case even this was not enough. However, we're still learning and some processes would need to be fixed in order to minimise these sort of bugs.
Thanks for patience & support.
Confirmed, the vibe course module 2.0.9.1 update has resolved the issue.
Put your foot down and stop scope creep. Say we plan to release that new feature in our Q3-Q4 theme update. It's a disservice to your existing customers. In the current state of operations, you're essentially pulling a money grab to sell additional users on WPLMS while breaking your existing customers infrastructure. Not cool.
.
