Help for Aimeos

If you have both, portrait and landscape images, then it's indeed difficult as the Swiffy slider implementation works best if you have a predefined ratio between width and height. You can try to unset that ratio in the CSS and see if it works for you.

There was a bug in processing "cms.text" which is now fixed in the latest 2023.10 version of the aimeos/ai-cms-grapesjs package. For CMS items it makes no difference but for e.g. products, it will returns only product texts if you specify "attribute,catalog,supplier,product.text"...

Can you have a look into the logs please (Aimeos Log panel, PHP error log, web server log)?

It seems to happen mostly with a few of our supported payment providers, most often Datatrans. Don't know if the reason is related to what they do on their side.

For the frontend, you have to use the frontend JSON API: https://aimeos.org/docs/latest/frontend/jsonapi/basics/ The resource is "cms", e.g. "http://localhost:8000/jsonapi/cms" and to get the content too, you need to include the text resources: http://localhost:8000/jsonapi/cms?i...

The safest way is always to use the XML delivery service provider to push the order data to another system: https://aimeos.org/docs/latest/manual/services/#xml If both applications are totally controlled by you, you can also store the orders directly in the other application. The downside is that yo...

"cookieSameSite: none" solves the issue most of the time but not always and we don't know why.
Which other browsers are also affected? Are Firefox and Safari among them?

Do you need the CMS content in the frontend or backend?

If you start a new project, use the Aimeos standalone distribution (aimeos/aimeos) because it's the easiest way to get a running installation and already contains many additional features you don't have to care about any more. The headless distribution is useful if you want to create your own progre...

The value in "URL target" for categories and products must be a Laravel route name or TYPO3 page ID but not an URL path.
In the CMS, the URLs are relative to the base path defined for the "aimeos_page" route.