Skip to content

[com_fields] - fix show on side/admin/both#24397

Merged
HLeithner merged 3 commits intojoomla:stagingfrom
alikon:patch-116
Apr 2, 2019
Merged

[com_fields] - fix show on side/admin/both#24397
HLeithner merged 3 commits intojoomla:stagingfrom
alikon:patch-116

Conversation

@alikon
Copy link
Copy Markdown
Contributor

@alikon alikon commented Mar 28, 2019

Pull Request for Issue #23246 .

Summary of Changes

Checked if the field should be showed on the form

Testing Instructions

create edit an article custom field
set show on to adminstrator only

Expected result

the field is not showed on from site

Actual result

the field is showed on from site despite settings

@Quy
Copy link
Copy Markdown
Contributor

Quy commented Mar 28, 2019

I have tested this item ✅ successfully on 322f2c2


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

@ghost
Copy link
Copy Markdown

ghost commented Mar 29, 2019

@boomsya please test.

@HLeithner HLeithner added this to the Joomla 3.9.5 milestone Apr 2, 2019
@HLeithner HLeithner merged commit cbb30ec into joomla:staging Apr 2, 2019
@HLeithner
Copy link
Copy Markdown
Member

Thx, I tested it my self.

@alikon alikon deleted the patch-116 branch April 2, 2019 16:09
@duvi
Copy link
Copy Markdown

duvi commented Apr 15, 2019

Actually, this has broken field display.

I think the "Show on" setting should only affect where the field should be visible in the edit view - in admin, in front end or both.

However, now the field is not displayed any more in the article view if the "Show on" setting is set to "Administrator", regardless of the "Automatic display" setting under "Render options".

AndySDH added a commit to AndySDH/joomla-cms that referenced this pull request May 30, 2019
The PR was adding a check to display the custom field on the frontend based on a parameter that was meant to be a check for the edit form
HLeithner pushed a commit that referenced this pull request Jun 5, 2019
… clarity (#25062)

* Undoing PR #24397 which was a mistake

The PR was adding a check to display the custom field on the frontend based on a parameter that was meant to be a check for the edit form
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.

6 participants