MethodTheme should not require the "Theme" parameter

or the negociation algorithm should be fixed instead.

the 'autumn' theme should ignore the 'index_html' default+front configuration

actually the reason the theme and the page are required in the ZMI is because it should be an AND not an OR.

or the negociation algorithm should be fixed instead. the 'autumn' theme should ignore the 'index_html' default+front configuration

yes, this allows for per theme rules that do not conflict with each other but on the other hand, the method theme selector would no longuer be able to impose different themes for different methods if the 'default' flag is stronger than the method theme in the negociation algorithm.

currently the logic is:

if the published object is called 'index_html', then the effective theme and page will be the ones specified (both must be specified).

that's why you can only have one 'index_html' listed.

so instead there should be several 'index_html' with different theme + page combinations, so

one could have:

method theme page 'index_html' 'default' + 'Front' 'index_html' 'autumn' + '...'

and the theme that would have been chosen otherwise (i.e. default theme, cookie, ?theme=...) would be used as a discriminator

I changed to 'enhancement' since the feature works as designed, it's just that there is a use case for which more flexibility is needed.