Change in Behaviour between J3 & J4 for Modules...

With J3 you can put modules anywhere as it says, however while testing J4 Upgrade I realise that there is a change in Behaviour, whereby with J3 you can have a modules which is NOT ASSIGNED to any pages, and when you use the code such as {module id="321" position="slider"} the module will appear on any generated page, however now with J4 the modules is not generated unless you set the modules to "ALL PAGES", which results in the module appearing everywhere and then TWICE on the page you have the code.

Guessing that was not done intentionally, so thought you should be aware as the component does not work as we require it anymore.

Thanks

Jamie

Hi Peter

Checked and the settings are the "Same" between the V3 & V4, whereby in V3 Ignore Module Assignments is set to "YES"
and then in V4 "Ignore Module Conditions" is also set to "YES", however as above it's not appearing when not assigned on a menu.

Thanks

Jamie

Hi I downloaded and installed as below

Regular Labs Library v22.7.24614 has been successfully installed
Modules Anywhere has been successfully updated to v7.15.3-dev2391926

Sadly did not change anything.

If it helps you can see the problem here
inspiring-bouman.111-67-29-104.plesk.pag...print-hsv-aasa-event

It works on our live - V3 site here
hsvownersclubofwa.com.au/events/calendar...print-hsv-aasa-event

Cheers

Jamie

Hi Peter

I don't believe the issue is with PageBuilder, as that code is the "same" between

The modules is
-NeedtoLoginAlert

I just changed it to be shown on "ALL PAGES" and now you can see it is shown TWICE on the page
inspiring-bouman.111-67-29-104.plesk.pag...print-hsv-aasa-event

So it would appear it's the problem is with IGNORING the PAGE settings with the "Module Assignment"

I also sent FTP Details for you now.

Thanks

Jamie

aha, interesting, so the previous parsing logic dealt with my incorrect syntax, I can't remember any logic, or thinking around this too long ago now.

However as you suggested replace it with a single {module id="321"} call and it works!!

Thanks very much for that, sorry that it ended with a mistake on our side, but it was interesiting to see I guess the different parsing logic on your side as others might have mis-used the sytax also.

Thanks again

Cheers

Jamie