No Code Attached Yet
avatar infograf768
infograf768
15 Jan 2017

Steps to reproduce the issue

Create a User custom field.
Then when editing the user in back-end, a new tab is present with the new field. (122 here is the user id)
index.php?option=com_users&view=user&layout=edit&id=122
screen shot 2017-01-15 at 17 51 52

That is fine. Frontend is also fine.

Now edit your own profile in backend (Edit Account menu item top right)
index.php?option=com_admin&view=profile&layout=edit&id=122

Expected result

The new tab and Custom field should display. At least it is my expectation.

Actual result

It does not display.
screen shot 2017-01-15 at 17 54 38

@Bakual
@laoneo

What do you think?

avatar infograf768 infograf768 - open - 15 Jan 2017
avatar joomla-cms-bot joomla-cms-bot - change - 15 Jan 2017
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 15 Jan 2017
avatar infograf768 infograf768 - change - 15 Jan 2017
Category com_fields
avatar Bakual
Bakual - comment - 15 Jan 2017

Confirming the bug.
Profile edit works in frontend but not in backend.

avatar laoneo
laoneo - comment - 16 Jan 2017

Is there any reason why this view is loaded by com_admin and not com_users? That's the issue here as we are editing a user in a different component, so the events are loaded with a totally different context.

avatar Bakual
Bakual - comment - 16 Jan 2017

Wow, didn't even notice that.
Imho, that should move to com_users. The model already extends from a user model anyway.

avatar laoneo
laoneo - comment - 16 Jan 2017

I can create a pr, so it would be ok for the 3 series to move it to com_users, no BC issue here?

avatar Bakual
Bakual - comment - 16 Jan 2017

Theoretically there are no B/C issues, practically there most likely will be.
I would copy the code from com_admin to com_users, change the links but still leave the profile view working (but deprecated) in com_admin as well. Possibly by extending the new classes in com_users to avoid duplicate code where possible.

avatar laoneo
laoneo - comment - 17 Jan 2017

Same issue as here #5162 (thanks brian teeman for the hint).

avatar laoneo
laoneo - comment - 24 Jan 2017

So we are not the first ones with this issue. Looks like nikolas has it investigated extensively. If we can leave it as it is would be nice as I'm basically running out of time to do it.

avatar Bakual
Bakual - comment - 24 Jan 2017

I'd leave the issue open but it is certainly not a release blocker and could be done later.

avatar franz-wohlkoenig franz-wohlkoenig - change - 5 Apr 2017
Status New Confirmed
avatar franz-wohlkoenig franz-wohlkoenig - change - 5 Apr 2017
Category com_fields com_fields com_users
avatar rdeutz rdeutz - assigned - 14 Apr 17
avatar AlexRed
AlexRed - comment - 2 May 2017

I can confirm the problem on Joomla! 3.7.1-dev (nightly Build)

avatar brianteeman
brianteeman - comment - 2 May 2017

@AlexRed as this is still open then of course nothing has magically changed

avatar rdeutz
rdeutz - comment - 7 May 2017

This problem will not be fixed in 3.7.1.

avatar brianteeman
brianteeman - comment - 4 Oct 2017

@laoneo I am guessing that this is because the context is not correct. Those fields are for
context="com_users.user"

avatar laoneo
laoneo - comment - 5 Oct 2017

Yes exactly.

Add a Comment

Login with GitHub to post a comment