Hi there!

Thanks for contacting us and sorry for your issue.

I could not log in to your admin area with the given credentials. Do you have SP Simple Portfolio there? Would you please try to uninstall, remove all instances, and then reinstall SP Simple portfolio and SP Page Builder to see if it helps?

Keeping a full backup of your site is always important before trying anything.

Best Regards

Hi there!

Sorry about that. Would you try logging in again?

To asnwer your question, I do not use SP Simple Portfolio.

Best regards.

Any updates?? May be Paul can help?

It seems like typical of Joomshaper very poor customer support.

Hi, I have the same problem, do you have a solution?

Thanks

Hello Ronny Ko,

I hope you are doing well.

Would you please trigger the error again with debug mode on.
You should then see the complete SQL and where exactly the problem was triggered.

With the origin of the error, I could check the source code.

According to chat support, version 4 should not be used productively yet.
That was the latest status from the pinned thread here in the forum.

Please be aware, version 4.0.3 also swallows the intotexts. "<hr id="system-readmore" />"

Hello Jens,

As per your request, here's the full debug output. Let us know what you find pleas.e

How do I find the versions prior to 4? And will it not break anything?

Call stack
#   Function    Location
1   ()  JROOT/libraries/vendor/joomla/database/src/Mysqli/MysqliStatement.php:141
2   Joomla\Database\Mysqli\MysqliStatement->__construct()   JROOT/libraries/vendor/joomla/database/src/Mysqli/MysqliDriver.php:1048
3   Joomla\Database\Mysqli\MysqliDriver->prepareStatement() JROOT/libraries/vendor/joomla/database/src/DatabaseDriver.php:1900
4   Joomla\Database\DatabaseDriver->setQuery()  JROOT/components/com_sppagebuilder/helpers/articles.php:384
5   SppagebuilderHelperArticles::getCategories()    JROOT/components/com_sppagebuilder/helpers/articles.php:54
6   SppagebuilderHelperArticles::getArticles()  JROOT/components/com_sppagebuilder/addons/articles/site.php:99
7   SppagebuilderAddonArticles->render()    JROOT/components/com_sppagebuilder/parser/addon-parser.php:726
8   AddonParser::getAddonHtmlView() JROOT/components/com_sppagebuilder/parser/addon-parser.php:412
9   AddonParser::viewAddons()   JROOT/components/com_sppagebuilder/views/page/tmpl/default.php:100
10  include()   JROOT/libraries/src/MVC/View/HtmlView.php:410
11  Joomla\CMS\MVC\View\HtmlView->loadTemplate()    JROOT/libraries/src/MVC/View/HtmlView.php:203
12  Joomla\CMS\MVC\View\HtmlView->display() JROOT/components/com_sppagebuilder/views/page/view.html.php:51
13  SppagebuilderViewPage->display()    JROOT/libraries/src/MVC/Controller/BaseController.php:639
14  Joomla\CMS\MVC\Controller\BaseController->display() JROOT/components/com_sppagebuilder/controller.php:80
15  SppagebuilderController->display()  JROOT/libraries/src/MVC/Controller/BaseController.php:672
16  Joomla\CMS\MVC\Controller\BaseController->execute() JROOT/components/com_sppagebuilder/sppagebuilder.php:26
17  require_once()  JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:71
18  Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}()  JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:73
19  Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch() JROOT/libraries/src/Component/ComponentHelper.php:355
20  Joomla\CMS\Component\ComponentHelper::renderComponent() JROOT/libraries/src/Application/SiteApplication.php:200
21  Joomla\CMS\Application\SiteApplication->dispatch()  JROOT/libraries/src/Application/SiteApplication.php:241
22  Joomla\CMS\Application\SiteApplication->doExecute() JROOT/libraries/src/Application/CMSApplication.php:294
23  Joomla\CMS\Application\CMSApplication->execute()    JROOT/includes/app.php:61
24  require_once()  JROOT/index.php:32

Hello Ronny Ko,

How do I find the versions prior to 4? And will it not break anything?

Best would be a Backup, to get back to SPPB 3.x.
Some users reported, they were able to go back by deinstalling 4.x and installing 3.8.
The Support stated, there is no way to get back to 3.x when upgraded to 4.x.

Unfortunately, I can't confirm either statement, as I'm currently on SPPB 3.8 and won't be switching until 4.1 at the earliest.

Quote from the Featured thread: https://www.joomshaper.com/forum/question/16053#:~:text=I%20simply%20re%2Dinstalled%20SPPB3%20over%20a%20few%20SPPB4s%20that%20white%20screened%2C%20and%20went%20back%20to%20work.

Installing SPPB3 over SPPB4 can work.

You can find SPPB 3.x in your Downloadarea.

-> https://www.joomshaper.com/downloads/extension?start=0#:~:text=SP%20Page%20Builder%20Pro,Download

Or Search for 3.8

As per your request, here's the full debug output. Let us know what you find pleas.e

Thank you very much, I'll take a look at it later today.
A quick look at the log, the addon "Article" seems to be the cause.

4   Joomla\Database\DatabaseDriver->setQuery()  JROOT/components/com_sppagebuilder/helpers/articles.php:384
5   SppagebuilderHelperArticles::getCategories()    JROOT/components/com_sppagebuilder/helpers/articles.php:54
6   SppagebuilderHelperArticles::getArticles()  JROOT/components/com_sppagebuilder/addons/articles/site.php:99
7   SppagebuilderAddonArticles->render()    JROOT/components/com_sppagebuilder/parser/addon-parser.php:726

Support may also be able to help with the information provided.

Edit:

        $query
            ->select('*')
            ->from($db->quoteName('#__categories'))
            ->where($db->quoteName('extension') . ' = ' . $db->quote('com_content'))
            ->where($db->quoteName('published') . ' = ' . $db->quote(1))
            ->where($db->quoteName('access')." IN (" . implode( ',', Factory::getUser()->getAuthorisedViewLevels() ) . ")")
            ->where($db->quoteName('language')." IN (" . $db->Quote(Factory::getLanguage()->getTag()).", ".$db->Quote('*') . ")")
            ->where($db->quoteName('parent_id')." IN (" . implode( ',', $parent_id ) . ")")
            ->order($db->quoteName('lft') . ' ASC');

        $db->setQuery($query);

Update, I searched the forum for similar issues and found one.

https://www.joomshaper.com/forum/question/16988

Looks like that sppb is overriding a addon which causes the problems.

To make sure, you have the same issue, you can try and change the default template to cassiopeia by joomla it self.
If this works, the problem should be the same.

Hi Ronny Ko,

Please take my sincere apology for the unwanted delay!

Please try the solution from here: https://www.joomshaper.com/forum/question/16995

And let us know if it helps!

Best Regrads

@jens, your solution works!
Would you know of when another version of SPPB (after 4.0.3) gets released, will the file article.php be required to be patched again?

In regards to the other support staff ignoring me, I think my questions are being sent to junior support members. They have less experience and may not have access to the developers, or they are too shy to raise their hands. I know of the last 18 months, I have seen new members whereas I used to deal with Paul and Toquil who are more skilled and experienced. Have you experienced the same?

Hello Ronny,

in advance, sorry for this wall of text. :)

My experiences are about the same.
Paul and Toufiq do the best job, even if there are misunderstandings here and there.

The other employees seem to get a bit confused in the orragnisation of the requests.
As a result, requests get lost and customers get angry because there is no response.

Currently, I monitor 16 requests to see if there is a response and then respond myself if necessary.
For example: 16069

The posts of @Se, where I wanted to help because of the Indigo-Template "Joomla 3 Template, wants a update to Joomla 4", were all deleted in the meantime.
Here it is not quite clear whether these were deleted by @Se or the support.

In my opinion this forum is unsuitable for the support of problems.
This has another provider for Joomla extensions solved much better, because here tickets are created in addition to the forum posts, that no process is lost and the support staff can also close tickets if necessary.
The search also works much better, because it also takes into account the content of the posts and so already reported problems can be found by other customers without having to know the exact title.

In my opinion, Joomshaper has somewhat lost contact with the customers and the wishes and only pursues its own ideas. (17301)

A good example for this is the Google Fonts, which have to be integrated manually via Custom-CSS and manual download.
What the competitiors have already made standard since July 5, 2018.
I also had a discussion with Paul about this a year ago.
Unfortunately, this feature has not been implemented until today and probably never will be.
The fact that the Google Fonts are active by default in all templates and layouts and look destroyed without them, is not only a visual, but also from the legal aspect a problem.
Example:
You buy a car, but you are not allowed to use it, until you replace some parts your self.

Or also that for easy to solve problems, the users are only referred to old PHP versions that no longer get updates in November and Joomla itself also discontinues support. Example: 17313

The definition on the part of Joomshaper for fastest possible is according to my experience to be equated with months.
Due to the lack of a bug tracker, it's also unclear how highly prioritized certain things are that customers can understand why it's taking so long.

:) I don't want to write more about it now.
Because I'm way too annoyed with the current state and want to change it.
For example: Publish updates for the Helix3 templates that are Joomla4 and PHP8 capable.

I wish you continued success and nice days.

With kind regards

Hi Jens,

I completely share your frustrations! I know because I have been using their products since SPBB 1.xx.

I have bad news to report. While the replacment of article.php worked to address teh front page, it broke the backened of SPBB. This means that I am unable to open the main page after pressing the "Get Started" button. By the way, why would one have to keep pressing that button every single time? Should be just once.

Sadly, I am going to have to take a backup and downgrade back to 4.0.1 of SPBB. I wished I had kept prior versions so I can at least go back to 3.8.x. The new UI is eye candy but it is too disruptive to learn when one wants to be productive.

I also tried to upgrade to 4.0.4 since it was released on the 8th of September. It just wouldn't upload.

I am curious to know if you see the same issue, or not.

Hello Ronny,

unfortunately I have to tell you that I have not made an update to 4.x yet.
I had the fear after my previous experience that it will run like with the Sencha ExtJs Framework and at the earliest with version 4.1 a stable state is reached.

Unfortunately, this fear has proven true and it was a good decision not to update yet.

To help others with their problems, it is usually sufficient to use a fresh installation.

To check the problem you described, I will take an existing page with 3.8.8 into my developer environment and try to update it.

3.8.8 -> 4.0.1 -> 4.0.4

Maybe I can reproduce the problem.

If this should not succeed, would it be possibly POSSIBLE that you set up an access that I can look whether I can localize a more concrete error message and/or cause?

With kind regards

@jens,

It is possible to setup an access.

I tested the update to 4.0.1 and then to 4.0.3.
So far no problems.

Basesystem:

• Joomla 4.1.5
• SPPB 3.8.8
• Helix Ultimate Template

The fix that toufig has provided is also very small, so it's amazing that this has now broken the backend.

if (!empty('', $catid)) { was changed to if (!in_array('', $catid)) {

Please create an account for me, I will then first check where the problem is but not make any changes yet.

[email protected]