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

[4.2] contact fields remove layout override #37716

Merged
merged 2 commits into from
Feb 22, 2023

Conversation

brianteeman
Copy link
Contributor

com_contact has two types of fields mail and contact. mail are for fields that are added to the contact form. contact is for fields that are displayed with the contact details.

at some point in time a layout override was added for this. Its fubar and not actually needed because the rendering of the different field contexts is already handled in the views (defaulkt_form and default_custom_user_fields)

the main issues caused by these overrides is that the contact fields are not rendered the same as they would have been for an article (dt not dl) and the display of subforms is obviously completely wrong.

Steps to reproduce the issue

1. Com content

  • Create 3 text fields
  • Create 1 subform field containing the 3 text fields
  • create article and complete the fields

2. com contact - context contact

  • Create 3 text fields
  • Create 1 subform field containing the 3 text fields

3. com contact - context mail

  • Create 3 text fields
  • Create 1 subform field containing the 3 text fields
4. test
  • create contact and complete the fields
  • compare the display of the fields in the front end

Expected result

Fields are displayed the same across the two components

Actual result

com_contact has a field layout override that uses a dl etc instead of a ul AND the subform display is fubar

com_content

image

com_contact

image

image

After PR

image

Additional comments

@richard67 I cant remember if i am supposed to add these removed files to script.php or if you deal with it?

@bembelimen @roland-d to me this is a bug fix and should be in 4.1 but I suspect you will say it needs to go in 4.2?

@richard67
Copy link
Member

@richard67 I cant remember if i am supposed to add these removed files to script.php or if you deal with it?

@brianteeman I will deal with it.

@joomla-bot
Copy link
Contributor

This pull requests has been automatically converted to the PSR-12 coding standard.

@brianteeman
Copy link
Contributor Author

looks like the psr12 pull requests completely messed up this pr :(

@brianteeman
Copy link
Contributor Author

fixed the issues from the psr12 pr

@Quy
Copy link
Contributor

Quy commented Feb 8, 2023

I have tested this item ✅ successfully on ba7d87f


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

1 similar comment
@viocassel
Copy link
Contributor

I have tested this item ✅ successfully on ba7d87f


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

@richard67
Copy link
Member

RTC


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

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Feb 15, 2023
@richard67
Copy link
Member

richard67 commented Feb 15, 2023

@brianteeman Could you solve the conflict? Thanks in advance.

@brianteeman
Copy link
Contributor Author

@brianteeman Could you solve the conflict? Thanks in advance.

done as requested

@richard67
Copy link
Member

RTC is still valid because the commit after the human tests was a clean conflict resolution. The conflict was in file "render.php" and came from PR #39616 , which changed array syntax in that file which is then removed with this PR here.

@Hackwar Hackwar removed the psr12 label Feb 21, 2023
@fancyFranci fancyFranci merged commit 982be1e into joomla:4.2-dev Feb 22, 2023
@fancyFranci fancyFranci added this to the Joomla! 4.2.9 milestone Feb 22, 2023
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Feb 22, 2023
@fancyFranci
Copy link
Contributor

Thank you! :)

@brianteeman brianteeman deleted the contact_form_fields branch February 22, 2023 21:53
richard67 added a commit to richard67/joomla-cms that referenced this pull request Mar 4, 2023
richard67 added a commit to richard67/joomla-cms that referenced this pull request Mar 4, 2023
laoneo added a commit to Digital-Peak/joomla-cms that referenced this pull request May 8, 2023
@laoneo
Copy link
Member

laoneo commented May 8, 2023

This pr broke the way custom fields are rendered in mails. Now the contain the HTML code as when they get rendered in a web page. Please test #40557 which restores the old behavior while keeping the new feature from this pr when rendered in a web page.

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.

10 participants