Labels |
Added:
?
|
I can replicate now:
Open the article and leave it open.
Open a field from the ones that should appear at the bottom and save it (leave it open).
Reload the article.
Close the field and see that is should be still at the bottom from the ordering...
Still can't replicate, but maybe someone else can?
Can't confirm Issue. Fields stay in Order they have in Fields-View. Changing order is correct reflected at Article-Tab.
@franz-wohlkoenig but thats not what i described. can you follow the clicks i made? I mean leave both open...
tested again, also leave Article- and Fields-Tab open: Change Field and save, reload Article > no Change.
Difference are Count of Fields (at my end 4) and Type (Gallery, Media, 2 Integer) and maybe this causes different Behaviour.
I tested with any field and it always happened... hmmm
would help if others can test
test again using new Article, new Field – no (randomly) wrong order.
Title |
|
For me it´s not randomly, every field i edit... I´m testing with Chrome, does this matter ?
will test on Chrome – are you on Mac/Win/Linux?
I am on Mac, Chrome Version Version 56.0.2924.87 (64-bit) (latest)
also Mac, Chrome 56.0.2924.87 (64-bit) (latest) - no changes, every Field stay in order.
I'v tested it as well and con't reproduce the issue.
Title |
|
Category | ⇒ | com_fields |
Title |
|
@coolcat-creations did Issue still happen?
Title |
|
Title |
|
Priority | Medium | ⇒ | Very low |
Status | New | ⇒ | Discussion |
This is reproducible.
In your browser, open 2 tabs. Tab 1 for Fields and Tab 2 for Articles.
In Tab 2, edit an article and go to the Fields tab within the article.
In Tab 1, edit a custom field (not the first one). Click Save
and not Save & Close
button.
Switch to Tab 2 and refresh the page. The edited custom field will be the first one listed.
Can you please check if this is still an issue as it appears there was a PR addressing this.
This is still an Issue.
3.8-dev
Multilanguage Site
macOS Sierra, 10.12.6
Firefox 55 (64-bit)
I will give it another try next week to replicate the issue.
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-11 19:52:26 |
Closed_By | ⇒ | jwaisner | |
Labels |
Added:
J3 Issue
|
Closing as the conditions required to reproduce are extremely specific and only happen under that condition.
But why would you close it if it's stil a bug?
"Closing as the conditions required to reproduce are extremely specific and only happen under that condition."
That seems not to be a valid reason to close the issue. It may cause a low priority,and maybe the bug only has low impact, however, this is the wrong way to clean up the tracker.
Please re-open.
@coolcat-creations do you still have a site where you can reproduce the issue? If so, could you please check the values of the "ordering" column in the __fields table?
Status | Closed | ⇒ | New |
Closed_Date | 2020-03-11 19:52:26 | ⇒ | |
Closed_By | jwaisner | ⇒ |
Reopening since the bug apparently exists
I checked again and can't be reproduced anymore - Thank you
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-05-21 19:19:32 |
Closed_By | ⇒ | coolcat-creations |
Can't replicate this. For me the order follows exactly how I have set them in the fields manager.