No Code Attached Yet bug
avatar RickR2H
RickR2H
26 May 2021

Steps to reproduce the issue

The accessiblemedia form field in not working. I tried to use it as a default module field and as a subform field.

In both instances when I save the module, the fields are deleted from the module backend view. When closing and opening the module again, the fields do not show. Saving the module again makes the field visible again with no images selected.

When I generate a frontend output, the default module field has no output, but the output from the subform field is an object. Saving the module again makes the output empty again.

screen shot 2021-05-26 at 12 33 17

screen shot 2021-05-26 at 12 52 31

screen shot 2021-05-26 at 12 52 58

The module to test the behavior can be downloaded from: Download

Expected result

Fields should output the required values.

Actual result

Fields are removed on save and there is no output.

System information (as much as possible)

Additional comments

Reference to PR and field:

#27712 #27712

https://docs.joomla.org/Accessiblemedia_form_field_type

avatar RickR2H RickR2H - open - 26 May 2021
avatar joomla-cms-bot joomla-cms-bot - labeled - 26 May 2021
avatar richard67
richard67 - comment - 26 May 2021

@dgrammatiko Maybe it needs similar changes for that accessible media field which were made before for the "normal" media field, if there were some?

avatar dgrammatiko
dgrammatiko - comment - 26 May 2021

Maybe it needs similar changes for that accessible media field which were made before for the "normal" media field, if there were some?

The normal media field was not initializing correctly the modal due to the fact that the JS is acting on a plain DIV (the way Boostrap modals work), if it was a custom element it wouldn't;t have that problem, ie will auto initialise on every new instance. In short, it's not this kind of problem here. From a quick look at the field I don;t see an input to save the value and I also see that the field is not using a layout (not customisable...). FWIW if someone does an audit on the current fields will be surprised on how many fields are not compatible with subforms ?‍♂️

avatar richard67
richard67 - comment - 26 May 2021

@dgrammatiko Thanks for the quick feedback.

avatar brianteeman
brianteeman - comment - 26 May 2021

See #32663

avatar richard67
richard67 - comment - 26 May 2021

@brianteeman Does it mean this here is a duplicate report to #32663 ?

avatar brianteeman
brianteeman - comment - 26 May 2021

no it means "here is another example of a field not working" as @dgrammatiko hinted at

avatar richard67
richard67 - comment - 26 May 2021

I see.

avatar chmst chmst - change - 20 Feb 2023
Labels Added: No Code Attached Yet bug
Removed: ?
avatar chmst chmst - labeled - 20 Feb 2023

Add a Comment

Login with GitHub to post a comment