Without making the consent keys part of a language file that is arbitrarily loaded on every request (i.e. en-GB.ini), this is going to happen. I think this ends up as a "won't fix" unless we store enough data with the consents to be able to arbitrarily load language files and not rely on something external having loaded the right one(s).

Being a language string of the com_privacy should not be supposed to move or copy the constant
PLG_SYSTEM_PRIVACYCONSENT_SUBJECT="Privacy Policy"
into the file:
/Joomla39/administrator/language/en-GB/en-GB.com_privacy.ini

I would expect to be natural to have that string in that file not loaded in the plugin file:
/Joomla39/administrator/language/en-GB/en-GB.plg_system_privacyconsent.ini

Even if you move that key to “fix” this for core, it doesn’t do anything to
address similar uses in potential addon plugins. So moving the key in core
might hide the problem in this specific scenario but it definitely doesn’t
fix the underlying problem.

On Tue, Sep 11, 2018 at 5:33 PM JoeforJoomla Boy notifications@github.com
wrote:

Being a language string of the com_privacy should not be supposed to move
or copy the constant
PLG_SYSTEM_PRIVACYCONSENT_SUBJECT="Privacy Policy"
into the file:
/Joomla39/administrator/language/en-GB/en-GB.com_privacy.ini

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#22136 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWfoRP_XtyT5yqKza1rHjumArRujgjFks5uaDo9gaJpZM4WkMCc
.

--

• Michael Please pardon any errors, this message was sent from my iPhone.

Well yes, at least for the 'main' and 'core' component... that would fix the problem.

CLOSED as won't fix,