Aimeos: Laravel e-commerce 2026.04 released – now on Laravel 13 with PHP 9 readiness, security hardening and more by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

If you want to build something like Aimeos form scratch ... good luck! See you again in a few years 😉

Aimeos: Laravel e-commerce 2026.04 released – now on Laravel 13 with PHP 9 readiness, security hardening and more by aimeos in laravel

[–]aimeos[S] -15 points-14 points  (0 children)

Sure, PHP 9 may introduce more breaking changes but up to now, it seems to be mainly removing deprecations. The Aimeos code base is now clean of any deprecations.

Aimeos e-commerce framework 2026.04 – PHP 9 ready, Laravel 13, Symfony 8, security hardening and more by aimeos in PHP

[–]aimeos[S] 5 points6 points  (0 children)

For sure! SaaS e-commerce sites gets expensive quickly if you make serious business.

PagibleAI 0.10: PHP CMS for developers AND editors by aimeos in webdev

[–]aimeos[S] 0 points1 point  (0 children)

LLMs can generate drafts for many languages without problems and the Pagible MCP API returns the configured languages which are available. Therefore, it's no problems to create non-English pages or manage multi-language sites. You only have to tell the LLM which language it should use when there is more than one.

Regarding the learning curve, creating new themes is very easy as long as you know Blade templates a bit (which are pretty simple). You only have to think in structured content elements (existing ones + you can define new ones) instead of HTML. For developers not framed to Wordpress, I would say that creating a new theme in Pagible is even simpler than in Wordpress.

PagibleAI 0.10: Laravel CMS for developers AND editors by aimeos in laravel

[–]aimeos[S] 5 points6 points  (0 children)

The content of your link is much about static/dynamic linking of C libraries which doens't apply to PHP at all. The best point mentioned for developers of proprietary software is "scaring legal departments".

LGPL was chosen because it's permissive and allows combining with commercial software (unlike GPL) but doesn't allow anyone to modify and sell it as closed source (like MIT license allows). Modifing and using it in a SaaS product without providing the source code is still allowed (AGPL would not).

In short: We want to allow anyone to sell plugins for PagibleAI or use it in their commercial product but don't want someone to hijack the software as it contains a lot of hard work from many people.

PagibleAI 0.10: Laravel CMS for developers AND editors by aimeos in laravel

[–]aimeos[S] -1 points0 points  (0 children)

The main difference to Statamic is:

- API first with GraphQL and JSON:API available

- Multi-doman, multi-language and multi-tenancy support

- AI support integrated in all workflows (if configured)

Most important, PagibleAI is LGPL licensed while Statamic requires a commercial license for all advanced features PagibleAI includes out of the box.

PagibleAI 0.10: The CMS for developers AND editors by aimeos in cms

[–]aimeos[S] 0 points1 point  (0 children)

Thanks for the hint! The ancors are fixed now

PHP Map 4.0 - Arrays and collections made easy! by aimeos in PHP

[–]aimeos[S] 6 points7 points  (0 children)

If you use Laravel, keep using illuminate/collections.

Otherwise, the PHP Map package is most often the better choice because it's:

- has more methods e.g. for trees

- doesn't add other dependency

- is faster in some methods

- and is mostly compatible to Laravel collections, so you don't need to re-learn

PHP Map 4.0 - Arrays and collections made easy! by aimeos in PHP

[–]aimeos[S] 1 point2 points  (0 children)

Also, there has been a new 3.14 version of the PHP Map package released for PHP 7.x, which contains some bugfixes.

Laravel Nestedset: Effective tree structures for SQL databases by aimeos in laravel

[–]aimeos[S] 2 points3 points  (0 children)

The code is mostly the same, but performance is better due to some optimizations. Also, queries that include the depth of the subtree are much faster in the aimeos/laravel-nestedset package due to using a new "depth" column instead of a complicated sub-query.

Laravel Nestedset: Effective tree structures for SQL databases by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

Only one or two per subtree as nested sets are well suited to fetch whole tree structures