CMS pages return 404

[snicto]

"aimeos/aimeos-laravel": "~2022.07",
"laravel/framework": "^9.2",

Pages created in CMS are not returning appropriate pages via URL. So I have created a "/contacts" page in the CMS section, however, when entering <site>/contacts 404 is returned instead.

Adding the following to web.php routes does display the pages, however, when entering the wrong URL 404 is not displayed, but a blank page is displayed instead.

Code: Select all

Route::match(['GET', 'POST'], '{path?}', '\Aimeos\Shop\Controller\PageController@indexAction')
    ->name('aimeos_page')->where( 'path', '.*' );

[aimeos]

Pages created in CMS are not returning appropriate pages via URL. So I have created a "/contacts" page in the CMS section, however, when entering <site>/contacts 404 is returned instead.

By default, the CMS pages are prefixed with "/p" to "/p/contacts" to avoid problems with Laravel auth routes.

Adding the following to web.php routes does display the pages, however, when entering the wrong URL 404 is not displayed, but a blank page is displayed instead.

The behavior has been improved in the recently released Aimeos 2022.10 LTS version.

[snicto]

Upgrading to 2022.10 resolved the issue, thx.

[VirtualSpy]

Upgrading to 2022.10 resolved the issue, thx.

snicto, may you check , does cms work for multishop in 2022.10 version

[snicto]

Upgrading to 2022.10 resolved the issue, thx.

snicto, may you check , does cms work for multishop in 2022.10 version

To extent.
If SHOP_MULTILOCALE=0
Everything works as expected.

if SHOP_MULTILOCALE=1
Pages under locales work, say "/en/p/contacts" works
However, default page "/en" is not being displayed, neither if set to a specific language or for all languages.

[aimeos]

In multi-site/multi-locale setups, CMS content that should be added to shop pages (home page is one of them) need the full URL path in URL field of the CMS page module, e.g. "/en" instead of "/"

[snicto]

In multi-site/multi-locale setups, CMS content that should be added to shop pages (home page is one of them) need the full URL path in URL field of the CMS page module, e.g. "/en" instead of "/"

Yes that works, bit confusing tho.