bug in fields scripts #609
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#609
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce the issue
hi
When add js script (whatever in view or views) and assign that field to an admin view, it works correctly
but when assign that field to module fields params no js will be triggered!
System information (as much as possible)
Additional comments
Yes, you are indeed right, I have not finished this part, but everything is there for it to work. So I spend a few minutes to see the path needed to add, and have added it. Please test the staging branch when you get a moment... and let me know.
(THIS WAS CHANGE READ THE WHOLE THREAD)
Just a note, with modules you can only use the
view
andview-footer
meaning these:Okay I found a contradiction in the current implementation, I pushed yesterday. I think we need to change it, so the the
view
andview-footer
gets added the the module admin area, and theviews
andviews-footer
gets added to the module display area.Okay at this point it seem like it will take a bit more code, automated code...
I will see if I get time to get this done. But we are faced with some serious challenge here, since we can not directly add JS and CSS to the module admin area, and have to instead create a custom field, which must get the code in the class. Hmmm this will be tricky at a high level. Since we have a number of other conflicts, like not all fields are custom, and not all fields gets added to the module, but gets added via the component. In which case we could face massive collisions.
I will continue looking, there is one more option worth looking into, and that is to create a custom field (this is done automatically, not by you) that JCB use to just added the scripts, and do nothing else... so we combine all the scripts of all fields into this one blank field... just to load the scripts. This seems like a good work around.
@saman222, please test and let me know.
This is how it should work when you now add a field to a module.