User tests: Successful: Unsuccessful:
In the list view of the mail templates (under System -> Templates -> Mail Templates) the list of available templates is joined against the list of active extensions we have in the system. This means that inactive extensions (plugins, components, etc.) automatically remove the mail templates from the list. Clever thing, good design, but the problem is, that we are comparing #__mail_templates.extension column against the #__extension.name column, which can contain basically anything. That column could for example contain a translatable string to translate the name of the extension into different languages and that could be different to the extensions element name like com_users. Or it is a single language site anyway and the developer simply used the translated name in that column directly. That is perfectly fine, but in this case this results in the mail templates not showing up.
The correct column to check against would be #__extensions.element, the internal key of the extension and the value that the mail templates use in the extension column.
#__extensions and edit the name column of the com_users component. Change it to User Management.No mail templates of the user component show up, even though the user component is still accessible and working fine otherwise.
The mail templates show up.
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Administration |
I have tested this item ✅ successfully on aca5793
I have tested this item ✅ successfully on aca5793
I have tested this item ✅ successfully on aca5793
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
PR-5.4-dev
|
||
RTC
RTC
I had a look how it is built with DPCalendar. For the component, the name is the same as element, both com_dpcalendar. But for the task plugin, the name attribute in the extension table is plg_task_dpcalendar while the element column has only dpcalendar. So this would break mail templates for the plugin.
I have tested this item 🔴 unsuccessfully on aca5793
I have to withdraw my successfull test. Allons and Richard are absolutely right. I tested the module and the component, but a plugin simply cannot work like that by design. Not even the core plugins would do.
I have tested this item 🔴 unsuccessfully on aca5793
I have to withdraw my successfull test. Allons and Richard are absolutely right. I tested the module and the component, but a plugin simply cannot work like that by design. Not even the core plugins would do.
I have tested this item 🔴 unsuccessfully on aca5793
I have to withdraw my successfull test. Allons and Richard are absolutely right. I tested with module and the component, but a plugin simply cannot work like that by design. Not even the core plugins would do.
| Status | Ready to Commit | ⇒ | Pending |
Back to pending due to unsuccessful human test.
Back to pending due to unsuccessful human test.
I have tested this item ✅ successfully on aca5793
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48306.