Latest post by Jip JJ Jonker on Wednesday, 05 June 2024 14:23 EEST
When I create a new custom field for articles, I want to select the 'econa' field plugin. But It is not in the dropdownlist. Am I missing something? I have added a Econa filed plugin on the site before and it is there and I can open it. But I can't create a new econa field...
Joomla 4.4.5
Econa 1.8.7
Hi Jip,
Just tested under Joomla 4.4.5 and I had no issues. Can you please verify that all Econa plugins are enabled?
I am also thinking that Joomla might have a limit on custom fields list. If you have a lot of extensions with custom fields try to disable some of them to see if Econa appears in the list.
Regards
The plugins are enabled. On our demo site we upgraded to econa 2.0. I just send you an email about our problems with this. But after the update the plugin is not selectable when adding a new custom content field.
https://drive.google.com/file/d/1Dduue0u4ZCTEV48YUxjnp0ThxLvoMJOW/view?usp=drivesdk
I made a screenshot. See the link above. There one extra field (URL) that is not showing on the screenshot. As you can see the econa field is missing.
I have disabled a couple of other plugins but that did not help.
Hi Jip,
Is there a chance that the plugin "Fields - Econa" has a custom access level?
It is set to Public like the other plugins.
This is really strange. Is there any chance that it is appearing with a different name (due to translation from language files) ?
If this is not the case please provide administrator credentials in a private ticket so I can troubleshoot this.
Regards
When I switch my backend language to English the plugin does show up! The translation of the plugin makes it show up as 'Label'. I did not see that in the plugin list in the backend. ut when I select 'label' the econa plugin is set as custom field. So this is a language issue indeed.
So it seems the issue is in the file plugins/fields/econa/language/nl-NL/plg_fields_econa.ini. Line 45 should be:
I have just fixed that. The language files are those you had provided in the past (thanks again). Probably I messed it up when I transferred them to the new version.
Please let me know if you spot any other mistakes in the translation.
I think we provided the wrong translation... I changed it on the Github repository. I there are other changes needed (for the 2.o version maybe) just let me know! Thanks for your help sorting this out!
Note: An active subscription is required in order to get support for our paid extensions. For our free extensions, if you don't have an account, register and then submit your support request. In case you just want to ask a question, you can also use the contact form .
