Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User profile form is prepated twice in frontend. #18065 #18211

Merged
merged 2 commits into from
Nov 18, 2017
Merged

User profile form is prepated twice in frontend. #18065 #18211

merged 2 commits into from
Nov 18, 2017

Conversation

Denitz
Copy link
Contributor

@Denitz Denitz commented Oct 3, 2017

Pull Request for Issue #18065

Steps to reproduce the issue

debug FieldsHelper::prepareForm() and see that it's launched twice in frontend:

Initially via PlgSystemFields->onContentPrepareForm event and see that it's launched twice in frontend.

Next FieldsHelper::prepareForm() is called again via UsersModelProfile::getForm()

Expected result

FieldsHelper::prepareForm() should be called once on user profile form display.

Actual result

Called twice

@Denitz
Copy link
Contributor Author

Denitz commented Oct 4, 2017

Who can fix AppVeyor issue with sqlite for PHP 5.6?

http://ci.joomla.org/joomla/joomla-cms/136 fails as well.

@stutteringp0et
Copy link
Contributor

This PR solves #18427 (now closed) - how can I help?

@ghost
Copy link

ghost commented Nov 2, 2017

@stutteringp0et please mark your Test as successfully:

  • open Issue Tracker
  • Login with your github-Account
  • Click on blue "Test this"-Button above Authors-Picture
  • mark your Test as successfully
  • hit "submit test result"

@stutteringp0et
Copy link
Contributor

I have tested this item ✅ successfully on 3a1b635

Fields are still rendered, FieldsHelper::prepareForm is executed only once.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18211.

@stutteringp0et
Copy link
Contributor

Done - looking forward to seeing this update in the next release. This issue was killing a feature of an extension I'm about to release.

@csthomas
Copy link
Contributor

csthomas commented Nov 2, 2017

I have tested this item ✅ successfully on 3a1b635


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18211.

@stutteringp0et
Copy link
Contributor

I was playing around with this, and with the patch applied - the user profile fields are still rendered, and work correctly for the most part - but when I tried a "color" type field, the value doesn't get stored. It works for any other custom fields I create, but not the color type. I suspect this should be raised as a separate issue - but thought I should mention it here. When I try this on a vanilla 3.8.1 the color value is stored as expected.

@ghost
Copy link

ghost commented Nov 3, 2017

@stutteringp0et can you please open a new Issue?

@ghost
Copy link

ghost commented Nov 3, 2017

RTC after two successful tests.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Nov 3, 2017
@stutteringp0et
Copy link
Contributor

Can I raise an issue based on a PR that hasn't been merged yet?

@stutteringp0et
Copy link
Contributor

Scratch my report about the color field type - I went through my settings and found that I forgot to give the user permission to change the value. Works fine now. No need for any action.

@mbabker mbabker added this to the Joomla 3.8.3 milestone Nov 18, 2017
@mbabker mbabker merged commit 2f93b76 into joomla:staging Nov 18, 2017
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Nov 18, 2017
@stutteringp0et
Copy link
Contributor

stutteringp0et commented Dec 18, 2017

@mbabker - when will this make it into the 4.0-dev branch?

@Denitz Denitz deleted the user_profile_form_prepared_twice branch January 11, 2019 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants