Hi there,

Thanks for contacting us. Sorry for the inconvenience. I have checked the module editing and it works fine.

https://prnt.sc/_e75KVkY7_l5

-Thanks

Hi Toufiq,

in fact the joomshapper is running normaly on the frontend editing, and it was the only way to work in some areas, but if you try to edit some page ou or some module using the joomshapper on the backend, since you click on edit the addons disappear and you cant do nothing.

Please check it again and try to do it and you will see this result.

other thing that I noticed yestersay, using the LMS component, in the courses page, and where we have multiple lessons related, de accordion with the lessons topics is not workinh also.

I'll wait for your feedback, kind regards, Luis

Hi again,

Here it is the example:

Editing some module using the joomshapper: Step 1. Opening: https://ibb.co/tKnKmQX Step 2. Editing some addon item (for example the icons group): https://ibb.co/mh2pygb (all the addons disapeared.

The thing related with the courses/ Lessons you can see here https://ibb.co/YbsR0p4 (the link was shared as Hidden Content). As you can see the lessons accordion don't work like in the template preview example

I'll wait for your feedback and the solution to correct this

Kind regards. Luís

Initial solution:

https://prnt.sc/oMRofwr7j0oa

Lessons Accordion issue solved

Hi toufiq, thank you for the reply.

regarding the joomshapper editing at the backend its a bug right? when do you expect to corrrect? this has some impact on our work because we are already used to work and edit on the backend

regarding the joomshapper editing at the backend its a bug right?

Yes, I have added on our working board and it's high priority. Don't worry we will try to fix it soon. Thanks

Yes there is this problem.

I believe I am having the same problem. I cannot edit a text box in a module. They work fine on pages, but not modules. And I can't edit them from the front end or the back end. Is there a fix for this yet?

If I may....

Yes, there is - but we suggest waiting for an official update that should be tomorrow.

v3.8.6 - we tested RC today and SPPB module problem was already fixed.

Sorry for temporary problems. In case you cannot wait any minute longer, just install older 3.8.3 and clean browser cache.

I should be able to wait until tomorrow. Thanks for letting me know the timeframe. It really does help relieve a lot of anxiety. LOL

Any word on the SPPB 3.8.6 release timeline?

Tom, I hope tomorrow ....

In case of we can install you a fix file.

We will try to release it next Monday or Tuesday.

Hi Paul,

I am at a point where I cannot wait until Monday or Tuesday for a fix. I have 2 sites that I need to be able to edit text modules in the footer. How do I install a fix file? Or do you need access to the to websites?

Hi Paul, I've the same problem. can you please install that fix on my website? the access was shared in a hidden message in the begtini g of this topic. Please help me on that because I've stop this work for a week and I need to work on it this weekend

We will release it soon. Please stay with us. Thanks

Hi Toufiq, when is expected to release the correction? if tou dont have a date please do me the downgrade because Im with this project stoped for almost 10days

@Luis

You have already fix installed, now clear browser cache and you can edit modules, articles, pages.

Remember to update SPPB after stable version will be published soon.

ㅤ

Added on our working board. Thanks

Hello again,

Any update on the release? I have been unable to update several of my client's websites and they are getting a little impatient. Please update ASAP on a real release date.

Thanks.

Hello Guys

Please go to this location: modules/mod_sppagebuilder/fields and replace pagebuilder.php file with the attached file. You need to unzip the file and then replace.

pagebuilder.php.zip

This will fix the issue for now.

Best regards

Hi Ofi,

Problem solved, thank you very much.

ㅤ

You are welcome, guys.

Yes, Jens. We are working on the 404 issue. The next version will have this issue fixed.

ㅤ