I have tested this item 🔴 unsuccessfully on b996b09

@brianteeman This option only reflects the settings in the module. Article parameters are not respected. This could be a feature we can add in the future. @drmenzelit What do you suggest?

@brianteeman This option only reflects the settings in the module. Article parameters are not respected.

Yes that is how it should work but it does not.

My point is that the setting in the content component are preventing the setting in the module from working.

check it out yourself.

1. set the content component options to hide readmore title
2. set the module to show readmore title

expected behaviour - module shows the readmore title
actual behaviour - module does not show the readmore title

This line is getting the params from the article - it should be getting the params from the module

@brianteeman please test again.

other than comments about the class names this works correctly

Thanks Rick!

One small inconsistency

The module now shows > Read more ... Title.

While the component shows > Read more: Title

Without displaying the title it works both the same

Good spot
Without the title it should be using JGLOBAL_READ_MORE
With the title is should be using JGLOBAL_READ_MORE_TITLE

Thanks for the feedback! Hopefully fixed now.

I have tested this item ✅ successfully on e00e280

I have tested this item ✅ successfully on e00e280

RTC

I think it would be better to do this the way that @rdeutz has done with #43457 - that way you can still use the layout etc

Removed my positive test as I think this is doing it the wrong way

@brianteeman please test the new version.

I have tested this item ✅ successfully on a81d79c

@RickR2H I've allowed myself to fix the merge conflict which was caused by your other, merged PR #44132 in file "modules/mod_articles/tmpl/default_items.php". What remains is the unresolved conversation above.

Back to pending as the test by @JeroenMoolenschot has been invalidated by a later change which was not just a branch update. I will restore @brianteeman 's test result as that was just invalidated by a branch update (with a merge conflict resolved by me but that is not relevant for the test result). But the inresolved conversation should be resolved, and it needs a 2nd human test.

I have not tested this item.

Removing my test as the active makes no sense

@Quy could you please test again?

I merged this because the latest changes were removing the unrelated active status and the actual code in this PR was successfully tested before. Thank you @RickR2H for your contribution.