thesdhotel We're looking into this issue, could you share the credentials of your site eg: URL + super admin and ftp account so we can check for you?
Bug: render_class is not displayed
WHY? Why do you keep asking for credentials to my site? You don't need them. This can be reproduced on a standard installation of Joomla. You don't need my site to see it, you can see it in your test site the same way.
I asked for the info so that when there is update from our dev team, I can update directly for you. If you don't want, it's ok.
- Edited
You can send me the link to the updated version here and I can test it 
Thank you
thesdhotel I will update here when having news from team, kindly wait.
13 days later
Hello there, any update on this issue?
thesdhotel Hello
Our developer is still working on this issue, pls give us more time.
a month later
- Edited
Hello, still no update? It has been over a month... This issue is preventing me from launching my Joomla 4 sites.
Hi,
I'm sorry for this lateness, I will remind our developer and get back to you soon.
8 days later
Hi, thesdhotel
After debugging, I figured out the reasons. You kindly replace these files then re-index your mega filter and test again.
components/com_jamegafilter/assets/js/main.js
plugins/jamegafilter/content/helper.php
support-render-joomla-custom-fields.zip
14kB
Regards,
Vanhs
Hello @vangogh,
I tested this updated code and I noticed there are issues with your helper.php code, the way you implemented it doesn't seem to be the best approach to fix the issue.
What happens now is that the json file now contains the render classes for ALL the fields assigned to the article, instead of only the fields that are set to be displayed.
The json should contain the render classes only for the fields that are set to be displayed. So only in this case:
if ($this->checkPublished('attr.' . $k . '.value') || $this->checkDisplayOnFO('attr.' . $k . '.value')) {
Just like it's done on line 692 for the ['title'], ['type'], etc.
If you look at the previous version 1.13 of the plugins/jamegafilter/content/, it was actually done that way. Can you simply revert it to the same method used in plugin version 1.13? It was working perfectly.
Let me know.
Hi, thesdhotel
Thank you for the suggestion. I will check it.
Regards,
Vanhs
@vangogh Thanks, please let me know.