No Code Attached Yet
avatar beejay41
beejay41
28 Oct 2022

Steps to reproduce the issue

Add a module layout override to your template. Create or change an article categories module and select your layout override from the layout dropdown on the advanced tab. Click save.

Expected result

The module should be saved.

Actual result

The error "Invalid field: layout" is displayed and the module is not saved.

System information (as much as possible)

screen shot 2022-10-28 at 13 38 48

Additional comments

If the layout is changed in the database, it operates as expected in the frontend.
This behaviour has been introduced since 3.9+, I believe. It certainly worked as expected in the past.

The same issue occurs with mod_login.

Previously reported on 3.x:
https://issues.joomla.org/tracker/joomla-cms/37491

avatar beejay41 beejay41 - open - 28 Oct 2022
avatar beejay41 beejay41 - change - 28 Oct 2022
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 28 Oct 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 28 Oct 2022
avatar ReLater
ReLater - comment - 28 Oct 2022

I can't confirm your find.

grafik

I could save all 3 modules after selecting my customlayout.

PHP 8.1.7
Linux dd51328 5.4.0-131-generic 147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64
Apache
Database type: mysql
MySQLi 10.5.16-MariaDB-1:10.5.16+maria~focal-log
Joomla 4.2.4

avatar beejay41
beejay41 - comment - 29 Oct 2022

Curious. Yes, if I select the override in Cassiopia, then it will save, but when I select the override from my own template, it fails to save.
I must be missing something in my template xml or perhaps just that my template has a period in it (folkclubs.2020)! The latter could easily explain why several on my templates exhibit this issue. I'll try changing that and report back.

avatar beejay41
beejay41 - comment - 29 Oct 2022

The period in the template name was the problem. I can't find any specific rules on template naming, but I'll avoid this in future.
It seemed like a good idea to include the year created in the name, but that was in the 1.5 era.

avatar beejay41 beejay41 - change - 29 Oct 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-10-29 10:04:01
Closed_By beejay41
avatar beejay41 beejay41 - close - 29 Oct 2022
avatar sh-si
sh-si - comment - 15 Jul 2023

I can confirm this issue.
The naming of my custom template is "nameX_nameY-v3.0.0".
If i change the template name to "nameX_nameY-v3_0_0" everything works as expected.

Is there a documentation / specification of template naming rules somewhere?

Add a Comment

Login with GitHub to post a comment