Hi Sebastian,

Read >> https://www.joomshaper.com/documentation/sp-page-builder/integrations

1. In Joomla CMS we use name Articles, not Posts. Posts are in WordPress.
2. Integration mode just add SPPB mode for Articles, in Articles edition mode. They are not moved to Pages list. This would only create confusion.

All clear now?

Hello Paul,

Thanks for the answer, but that has already been done and the Joomla articles / posts are still not visible in the SP Page Builder. I'll send you another screenshot: <a href="/https://ibb.co/86ZrW5q"><img src="/https://i.ibb.co/zGvXyRp/screen5.png" alt="screen5" border="0"></a>

Basically, something doesn't seem to be going the way it should. I actually wanted to make it easier for myself and not load a plugin on every page. But the way things are going here so far, I'm faster and more error-free than with this page builder. For WordPress I use Elementor Pro. But I still have customers who absolutely want to continue using Joomla. I can also change it to WP if that doesn't lead to a normal result here. Already sent some links from our Joomla pages to your colleagues support so that they don't think we don't know what Joomla is. There are also websites with more than 1500 pages / articles.

Greetings Sebastian PS: It's quite a fat dog that you can't even attach screens directly as attachments here.

Oh and not to forget that the internal backend editor doesn't seem to be translated. WP has .pot files for this if the developer doesn't want to or can't do it himself. What possibilities do I have with the SP Page Builder to be able to foist that on my customers? The page builder isn't even completely translated in the standard view. It also says Pages, Categories, etc. It's just horrible to look at for the user.

As already said, integration mode is active. Posts can also be edited from the Joomla post view using the SP Page Builder. Sometimes more sometimes less. Now and then there is no page builder. Close and try again, then it usually works.

What do you mean exactly they are not moved to the sidebar? I think you mean I still don't see you under the pages in the page builder. Then what do I need the pages for? Categories etc. What if I can do everything from Joomla's posts and categories? Are these legacy issues? The hammer is when I call up the categories under the page builder, it jumps to the Joomla categories anyway. So why are they then displayed again under Page Builder and then not displayed there? All a bit confusing

We cause confusion when you then get the idea of actually creating a page/page/post using the page builder and then using the context menu on the right to say, add post to the menu. Then you see no more main menu, everything gone.

Support is only in English language, why you don't respect our support rules? :(

SPPB as like any other component has language files that can we translated by webmaster, it's much more easier than in WP, espessially if you know how Joomla works, there are .ini files.

The current translation was created for older version by community, SPPB 5 is a new. We are not native language speakers to made it in corrent way.

My suggestion is ... on German Joomla Community (FB) find somebody who uses Joomla and SPPB for year(s) and maybe he can give you a one hour online lesson how all works. It will be much more useful than reading guides and discovering on your own.

BTW

No wonder why some people still like Joomla after having bad experiences with WordPress. I have seen it many times. There are few main reasons of that.

Oops, I overlooked something, or my Google Chrome translated your answer right away and I just replied to it. Is corrected. If the answers come as quickly as the admonitions, I have no problem. It would be a lot easier if you could attach the corresponding screens and messages here.

I know where joomla has its language files and how they are managed. Only if the page builder doesn't stick to Joomla conventions, which were already the case with the 3.x versions, is that another topic again. The language files for the components and plugins are located in the /language folder, divided according to ISO en-GB or de-DE. And below the structure are the corresponding files, but not with en-GB-in front of the module or component names. The folders already provide the distinction. So for the de-DE folder I now have to add a component called en-GB.com_sppagebuilder.ini, probably because it was hard coded that way. Just easy or what?

That's why I said before, someone has to understand your logic first. And almost everyone in the German Joomla community advised against getting involved with the SP Page Builder. So it's going to be difficult to find anyone here who knows or wants to know the depths of this system, other than a few babbles. Except for an Ol..... Pf.... . :-)

I just thought it can't get that bad, let's just give it a try. So far just frustrating.

quote: No wonder why some people still like Joomla after having bad experiences with WordPress. I have seen it many times. There are few main reasons of that.

but then you have not yet had to implement a GDPR-compliant shop with Joomla. for simple websites, Joomla is still a good CMS. But Joomshopping, HikkaShop and VirtueMart, you have to struggle to get it right. Apart from the performance if you use it.

woocommerce we only take up to about 30,000 items, otherwise real shop systems are used. I don't want to run a VirtueMart seriously with more than 3,000 items. But then few filters and no attributes, otherwise you'll die right away.

other Joomla page builders don't bend the basic system that much. For example yoot..., or joompl.... or rc..... You can use Joomla as usual, there are the posts, posts, the categories, just the categories and the new media manager of Joomla is the media manager (media). They keep quiet and do what they are supposed to do. layout adjustments.

GDPR is Germany is high beyond for what purpose it was created. In one hand Google servers are bad, on other hand almost all EU politicians use iPhones (with iCould), funny thing.

WP never was created a shop platform that's why the code is not working optimally