CB - ImageField: forgotten parameter "fieldLayoutContentPlugins"

Hi,

The above-mentioned field contains the "fieldLayoutContentPlugins" parameter, the handling of which, I guess, got lost somewhere some time ago.
Since I have been using the mechanism of supplementing/modifying the appearance of the user's image thumbnail via a dedicated CMS Content plugin for several years, each CB update forces me to "repair" this deficiency again.

My update is to complete the code in the file /home/.../public_html/components/com_comprofiler/plugin/user/plug_cbcore/library/Field/ImageField.php
Class ImageField function _avatarHtml() po linii 789


The second issue related to the user thumbnail is the possibility of supplementing it with a tooltip with the content of the [$title] variable in the case of a thumbnail with an initial.

I hope that with this entry I will not completely remove the "fieldLayoutContentPlugins" parameter. 😱
Thank you and best regards,

Nope, it works perfectly fine. It applies exclusively to the layout parameters above it. It does not apply to the field value directly. You're welcome to make your change though, but that will not be applied to the core, sorry. You can completely replace the HTML entirely using the layout parameters. Example as follows.



[FIELD_NAME] substitutions should give the live path for image fields, but that may only apply to userdata substitutions. You can however build the path out manually as needed though.

It's also possible to use onAftergetFieldRow to modify the entire HTML of a field using CB Auto Actions if you need to extend the field with custom rendering. This gives the full HTML structure that the field will output so you'd need to traverse the DOM structure it outputs or be careful with your regexp replacements.

Ok, now everything is clear. I know where I made a mistake in my thinking.
I need to decide whether to use the current approach using the "fieldLayoutContentPlugins" parameter, with the difference that I will use the layout parameters, context 'field.layout'
and build the full structure of the "avatar" field in the Content Plugin or use the "Auto Actions" add-on you mentioned and use "onAftergetFieldRow".
In the latter case, there will be no trouble traversing the DOM of the HTML structure generated by the field because I am currently using this exact strategy.

Using "Auto Actions" seems more elegant...
Thanks for the explanation and best regards,

You also have the option of using something like CB Code Field. Basically move the storage and display to 2 separate fields. The code field lets you run and display whatever PHP you like. So you could use that to build out the field to display however you like. Once done and displaying how you wanted move the code field to a tab that's in a not shown on profile position. Next override the layout of your image field with a substitution of that code field. This would make it so the display of your image field will be that of your code field.