4.0.9 Release / Rendering Layout From 4.0.8 / ***WARNING***
micduf
WARNING If you have specialwritten code for forms, toggles, etc, this code stops work totally as the rendering layout has changed from 4.0.8 to 4.0.9 so special code does not find the needed rows from 4.0.8 to 4.0.9.
Well, what a disaster this new version is, I can't believe it from a developer perspective and there is still tons of bugs that is not addressed that is causing both logical and graphical errors.
Are Joomshaper going to change the rendering or page structure and will outpu something else with each new version is a very qualified question? If that is the case you need to have a development environment where you upgrade each and every SPPB release, then rewrite and amend the code so it is working, then push it into production...
If this is true, then there is no other option than to create a custom module that contain all needed functionality (forms, buttons, custom scripts, etc) and then insert it directly in SPPB, without the risk that layout, clases, etc, get damaged or impacted.
I would like to have an answer from Joomshaper how you would approach this development behavior.
Ofi Khan
Accepted AnswerHello micduf
Apology for the inconvenience and the mess. We are aware of the issue and have recovered this. We will fix the issues on SP Page Builder 4.0.10. The update will release today. Please check your site update notification in few hours and update to the upcoming version. It will be fixed.
Best regards
micduf
Accepted AnswerIs not only a mess in your code, Joomshaper development process must be improved in many aspects, and it is very clear now that you do not work agile in the development with a strict Q/A implemented.
Please do NOT deliver ANY updates or code that has not been roughly tested INTERNALLY before release.
It is not the users and community that is going to take care of this mess for Joomshaper is your management that needs to start to address this with minimum requirement of Q/A. As the SP Pagebuilder and the Helix Ultimate framwork contains so many bugs we have installed a separate screening and test system to check the code and if it works with Joomla 4 and other components + the use of special written code that is dependent on the SP Pagebuilder.
We could not take any risks at all from now until we have solutions that is working without any errors.
I have also reported two (2) other major errors:
- 4.0.9 Release / Pages Links To A 404 Page
- 4.0.9 Release / Feature Box Error
URGENT to FIX
Could you imagine the cost of this and how this affects production environments where SP Pagebuilder and Helix Ultimate is used?
Just read what the community says, I have no words left!
> Thumbs up to Paul that is helping the community with all issues!
Ofi Khan
Accepted AnswerI understand and appreciate your feedback. Your issues have been fixed in SP Page Builder 4.0.10. Please update to the latest build and it will be working again. Again, I am sorry for the mess and trouble on behalf of the team. Hopefully, this will not be the case in the future.
micduf
Accepted AnswerWe have scrubbed 4.0.10 first in staging and added countermeasures code to avoid further tenant damages, then we have pushed the code into production, and it still works since this morning.
But there are still several bugs in the backlog that needs to be addressed with highest urgency from Joomshaper development team to harden and stabilize the code that are related to core issues.
The error that is implemented into the Feature Box reported with (4.0.9 Release / Feature Box Error) also needs to be addressed with high priority as there is no work-a-round for this at the moment.
Ofi Khan
Accepted AnswerFeature Box error has been addressed and fixed in 4.0.10. Please download it and install again.
micduf
Accepted AnswerHello,
NO, the Feature Box is not fixed, I downloaded the SPPB 4.0.10 from your website, installed it on our test tenant and the issue remain.
If you have altered the code, why do you not increment the version?
Ofi Khan
Accepted AnswerApology for the inconvenience. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.
micduf
Accepted AnswerThis case is related to the page rendering, NOT the Feature Box issue, is managed in another case and and another Jira ticket internally within our development team.