JoomShaper’s Plan For the SP Page Builder 3.x Series - JoomShaper

JoomShaper’s Plan For the SP Page Builder 3.x Series

11 January 2022
Hits 2,609
2 min read
JoomShaper’s Plan For the SP Page Builder 3.x Series

Hello SP Page Builder fans and users! Recently, after the announcement of the SP Page Builder 4.0, there has been a lot of concern regarding the new features of SP Page Builder 4.0 and the future of the SP Page Builder 3.x series.

Therefore, we have decided to clear the air with an official response and commitment regarding the future of our much-loved SP Page Builder.

Mission Behind SP Page Builder 4.0

We created SP Page Builder with the vision of making it the most professional page-building tool available in Joomla for website creators. With each upgrade over the years, we’ve pushed it forward in terms of capability and innovation.

We are always looking ahead for innovation and every once in a while, a significant leap is required to unleash the full potential of the product. Behind SP Page Builder 4.0, there is a vision to revolutionize our users’ workflow, save valuable time, and set the foundation for the next generation Joomla page builder.

However, we understand that many of you are dissatisfied with the decision to remove the backend editor from SP Page Builder 4.0.

So, here’s our clarification.

Our Commitment to You

SP Page Builder 4.0 has a completely new architecture and we can not add backend edit support to it. However, at JoomShaper, regardless of any challenges we face, we always put our customers first. That’s why we have decided to give regular updates to the 3.x series as we have been for at least the next three years.

SP Page Builder 3.x series will continue to receive security patches, updates, and compatibility support for at least the next 3 years.

This is to ensure that you continue to have the greatest possible site-building experience as you have been. Meanwhile, we humbly request you to give SP Page Builder 4.0 a fair trial and see how you like it.

We understand your concerns as well as your enthusiasm and love towards SP Page Builder, and we fully appreciate that you may have additional questions or constructive input.

You have placed your trust in us over the years, and we cordially invite everyone to join us on this journey with your valuable trust.

Zareen Tasnim

Zareen Tasnim

Technical Content Writer
Zareen is a technical content writer at JoomShaper. She's a tech enthusiast, writer by day, programmer by night, and always a foodie at heart!

Comments (24)

C
Chris
This comment was minimized by the moderator on the site

Oops, pressed enter too soon!

I know I've been one to question the decision as I only ever use front end editing now for interactions...

However, I know from testing that there are elements to PB4 which resolve some of the reasons why I wasn't using the front end more often. In fact, one or two of these PB4 features actually solve some backend editing issues for me as well!

I still have a few queries on how PB4 will address some of the issues I have with front end editing now, where is best to ask those questions?

Kawshar Ahmed
Kawshar Ahmed    Chris
This comment was minimized by the moderator on the site

You can email us your suggestions or post on the forum. Let's see what we can do in the future to collect feature requests.
Thanks

M
meto
This comment was minimized by the moderator on the site

It would be great if you reconstruct the column building layout to have 5 columns.
This is a missing option.
We need also the option to copy and paste styles like elementor page builder

Kawshar Ahmed
Kawshar Ahmed    meto
This comment was minimized by the moderator on the site

SP Page Builder 4 Alpha 2 has both of the options.
Thanks

AP
Alexandre Ponton
This comment was minimized by the moderator on the site

Any plans to include 'draft' / 'published' version for the pages along with the ability to revert to a previous published page ? Some kind of version control.

At the moment I am stuck on a highly modified v2.5.4 PRO because I don't want to go to the process again of reversing and customizing the SP Page Builder engine.

Muntasir Sakib
Muntasir Sakib    Alexandre Ponton
This comment was minimized by the moderator on the site

It is already in our feature-list. Thanks for reminding us again.

S
Steve
This comment was minimized by the moderator on the site

If you were really concerned with your customers, you would have considered this in your design, not as an after thought. Not buying this excuse at all. Every "minor" change you make can have a significant impact on the time it takes me to do the things I already have established processes for, and I'm quite sure I'm not the only one.

How about building the product we need, not the one you think we should need. I don't give one rotten fart about the "possibilities" and "unleashing potential" when you have not one little bit of respect for your customers - as evidenced by this monstrosity...

If you were really concerned with your customers, you would have considered this in your design, not as an after thought. Not buying this excuse at all. Every "minor" change you make can have a significant impact on the time it takes me to do the things I already have established processes for, and I'm quite sure I'm not the only one.

How about building the product we need, not the one you think we should need. I don't give one rotten fart about the "possibilities" and "unleashing potential" when you have not one little bit of respect for your customers - as evidenced by this monstrosity you're trying to force on us.

I do not care if it's not possible to put the back end editor in. You should have thought about that before you wasted your time on this crap.

Read More
D
dougdanielraught
This comment was minimized by the moderator on the site

Progress always comes with a little discomfort. But with a positive attitude and recognizing that with a little discomfort there is also great gain! Don't get caught in old in the old ways-move forward. Pagebuilder 4 is great and if anyone has random issues, you know the Joomshaper will resolve them.

S
Steve    dougdanielraught
This comment was minimized by the moderator on the site

The one thing they're good at is creating more problems to solve. Depend on that. Yes, they will resolve them, but they use US as their guinea pigs and beta testers - and I DID NOT SIGN ON FOR THAT. They regularly demonstrate no consideration or concern for their customers at all: hiding behind this tired excuse about "innovation".

Get a clue guys. Go the direction your customers are, or they will leave you behind. Innovate THAT. Work on THAT. Not doing your own thing and then trying to muscle everyone to go for it.

Muntasir Sakib
Muntasir Sakib    dougdanielraught
This comment was minimized by the moderator on the site

Thank you very much for the appreciation.

RA
Rafael Alvarez
This comment was minimized by the moderator on the site

Is nice you plan to support, but I wonder if Page Builder 4 will be compatible with pages done with v3.8.x .... ir not, all the job we are doing now on desinging new webs will not be worth, cause will it need to be re-done.

Muntasir Sakib
Muntasir Sakib    Rafael Alvarez
This comment was minimized by the moderator on the site

Upgrading to Page Builder 4 from Page Builder 3.x.x will be possible. You won't lose your work hopefully.

coconutguy
coconutguy
This comment was minimized by the moderator on the site

I’ve tried SPPB4 and I still find it a problem. Yes all the tools are there but i guess it’s the way it works. So when we give a client their website it’s like we’re giving then the entire project as well for them to modify since they will be using the very same tool. I propose certain areas can be toggle on and off for clients sake. (I hid some areas and buttons with css on v3 so that clients can only edit pages and not add any page templates or sections).

I’m not a frontend person I guess that is why I cannot adapt to it. I also do not understand why joomshaper could not keep the...

I’ve tried SPPB4 and I still find it a problem. Yes all the tools are there but i guess it’s the way it works. So when we give a client their website it’s like we’re giving then the entire project as well for them to modify since they will be using the very same tool. I propose certain areas can be toggle on and off for clients sake. (I hid some areas and buttons with css on v3 so that clients can only edit pages and not add any page templates or sections).

I’m not a frontend person I guess that is why I cannot adapt to it. I also do not understand why joomshaper could not keep the backend editor. The product (backend editor) was already there, just build a better frontend one and not scrap everything. I get the direction where you guys are going though and adding more 3 years on SPPB3 is decent, but if no considerable change is made to 4 that will ease SPPB3 backend users into 4 easily then consider a lot of us going elsewhere or dropping SPPB as a whole.

Also like Rafael said, what’s gonna happen to pages made in 3 if someone installed v4 ?

Read More
Ugur Uygur
Ugur Uygur
This comment was minimized by the moderator on the site

There's nothing can be done. We will get used to the innovation

Thank you

coconutguy
coconutguy    Ugur Uygur
This comment was minimized by the moderator on the site

As a freelancer, I am impacted but not in a big way, but just think about all those huge agencies and developers on Themeforest as well! It's a huge leap, but we will see what happens in 3 years! I have tested it myself and i've drawn the line that this is not the tool anymore for my clients unfortunately. There's still time and testing to be done on v4 and I hope those quirks will be address. I will do a proper test when the product is final!

Ugur Uygur
Ugur Uygur    coconutguy
This comment was minimized by the moderator on the site

You are right but they said this feature will not come back.

SP
Sophie Preston
This comment was minimized by the moderator on the site

If it is not possible to have backend AND front-end editing : What about making 2 different products ? one Sppage builder with back end editor only and an other one with front-end editing only? Then we can choose the one we want to use ...
I've just tried the Alpha 2 and my site was all over the place: my custom css file didn't seem to be taken into account by the page builder ...
I would rather keep on using a backend page builder

K
kweb
This comment was minimized by the moderator on the site

What is my benefit as a developer that you continue supporting 3 more years version 3? Right - no benefit. Because when I build up a page I must tell my client that his website will be outdatet in x days/year, or he needs to learn a complete new system.

I dont think that it will be that easy to just click the update button and voilà - here is your exactly same website just with page-builder 4. I remember the release of Helix Ultimate 2. I need to spent hours on every website I update because the update crashes everything. And that is what it will also be updating from 3 to 4. So me as a...

What is my benefit as a developer that you continue supporting 3 more years version 3? Right - no benefit. Because when I build up a page I must tell my client that his website will be outdatet in x days/year, or he needs to learn a complete new system.

I dont think that it will be that easy to just click the update button and voilà - here is your exactly same website just with page-builder 4. I remember the release of Helix Ultimate 2. I need to spent hours on every website I update because the update crashes everything. And that is what it will also be updating from 3 to 4. So me as a developer has the choice buildig up a website with the prefered SPPB 3 with in mind to have a mess in 3 years - or I need to use SPPB 4 as soon as possible. Eat or die....thats it....

I had a look into SPPB 4 Alpha yesterday and I stay at my opinion - it makes a lot of things more complicated.

Read More
coconutguy
coconutguy    kweb
This comment was minimized by the moderator on the site

I totally understand your frustration Kweb. I do. I have also been trying consistently to use V4 but the way it works is not intuitive. The product is not final and I take that into consideration. To me, V3 is a beast and still is and should have been used as a benchmark to create V4.

I honestly do not think at this stage, Joomshaper will bring back the backend. I also have tons of sites around with V3 as well, what are we gonna do with these ?

I love SPPB, I do, but it breaks my heart knowing such an awesome product is going in a new direction and leaving some major key functions...

I totally understand your frustration Kweb. I do. I have also been trying consistently to use V4 but the way it works is not intuitive. The product is not final and I take that into consideration. To me, V3 is a beast and still is and should have been used as a benchmark to create V4.

I honestly do not think at this stage, Joomshaper will bring back the backend. I also have tons of sites around with V3 as well, what are we gonna do with these ?

I love SPPB, I do, but it breaks my heart knowing such an awesome product is going in a new direction and leaving some major key functions behind. I would not even mind buying or paying to support V3 for a lifetime!

Read More
vallagruppen
vallagruppen
This comment was minimized by the moderator on the site

Writes regarding SP4 - Are you serious about removing the function in the backend. We have about 300 sites today based on SP Page Builder. Going away from the backend is completely super wrong.

You say you will support version 3 for 3 years. It is enough because over time you will not develop it.

Instead, make sure that version 4 has a backend function. You MUST and should listen to your customers.

Vallagruppen

Ugur Uygur
Ugur Uygur
This comment was minimized by the moderator on the site

Hi,

Elementor also has button effects and image reveal option. If you can adapt these SP I'm sure it will be great.

Regards

K
kweb
This comment was minimized by the moderator on the site

Maybe the solution would be a compromise to add a kind of "developer mode" to SPPB4. With a click you can switch to an overview like it was in the backend times, where I have the bricks and I can see all my rows, columns, addonons on one screen and I can quickmove them. A bit like switching to SOURCE on editors. Maybe a backend would not even be necessary for that and you could still follow your "intuitive" way. I dont know how this would be possible in technical way but this would calm down your long time customers a bit. Think of it - try to find a solution for the users who really...

Maybe the solution would be a compromise to add a kind of "developer mode" to SPPB4. With a click you can switch to an overview like it was in the backend times, where I have the bricks and I can see all my rows, columns, addonons on one screen and I can quickmove them. A bit like switching to SOURCE on editors. Maybe a backend would not even be necessary for that and you could still follow your "intuitive" way. I dont know how this would be possible in technical way but this would calm down your long time customers a bit. Think of it - try to find a solution for the users who really really liked the "brick view" on SPP3.

Read More
S
Santo
This comment was minimized by the moderator on the site

So disappointing... Backend builder was literally the best part of this page builder. Listen to your customers!!!

Dmitry Goncharov
Dmitry Goncharov
This comment was minimized by the moderator on the site

Stop being hysterical already. SPPB4 is a great product and does not need any admin panel.

As they say in Russia: "Bad dancer and eggs interfere!"

There are no comments posted here yet

Sign up for our newsletter

Don’t miss any updates of our new templates and extensions and all the astonishing offers we bring for you.