@zero-24 where and how to change the view using the new override? Tried in User > Tab: Two Factor Authentication haven't found a Way to change View.

@franz-wohlkoenig you will not get an option, just override the plugin edit the override and add some text. Visit the page where the plugin is displayed (e.g. login) and see if the text is there

Changed Override html > plg_twofactorauth_totp from:

	<legend>
        <?php echo JText::_('PLG_TWOFACTORAUTH_TOTP_STEP1_HEAD') ?>
	</legend>

to

	<legend>
        My 2FA
        <?php echo JText::_('PLG_TWOFACTORAUTH_TOTP_STEP1_HEAD') ?>
	</legend>

Couldn't see "My 2FA" in "Users: Edit > Tab 'Two Factor Authentication':

Did you check in the frontend template? If we override in protostar there is no change in isis ;)

@ciar4n @C-Lodder can you check if we can redesign this page to something more decent than the 3 columns?

@zero-24 i looked at login, theres a "Secret key" new, but its the Module so i don't know where i can see the View.

You can go to your user profiel in the frontend. There is the view that you can change with that override.

@dgt41 To be fair the current layout is functional. One alternative might be to create a btn-group with 'showon' for each of the columns....

I have tested this item ✅ successfully on c3acd81

You will need to update the hathor template overrides as well

You will need to update the hathor template overrides as well

Hathor is done. Thansk for the hint @brianteeman

Any feedback on this one? Should this be tested / implemented or just closed?

With the rise of fields i think this is a good idea. But I dont think we can progress with it.

In the UI as you are presented the ability to create overrides of all plugins when you have a front end template selected - you shouldnt be able to override the installer plugins here AND the same when you have an admin template selected - you shouldnt be able to override the content plugins here.

With the current plugin architecture I dont think we have a way to determine if it is for frontend or admin though :(

Plugins aren't app specific and I would heavily downvote any code that tries to add that distinction personally. It's already goofy enough that we have the ability to create admin/site specific modules versus those being app agnostic (especially when the underlying code is in essence the same thing, check the two feed modules).

With that said though, maybe the compromise to this is a way to allow plugins to hook into this process. Because plugins are doing layouts in all sorts of different ways (at least with core there are a couple using JLayout and a couple using the tmpl directory processed with JPluginHelper), and because extension developers may have their own logic predating the plugin layout support in JPluginHelper, this might be the most flexible option.

I am just commenting on the user experience of the list of plugins presented to them.

ok closing for the reasons above. Thanks for the feedback and the testers!