Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
views_ui.module
Priority:
Major
Category:
Bug report
Issue tags:
Reporter:
Created:
24 May 2013 at 04:05 UTC
Updated:
29 Jul 2014 at 22:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pcambraTagging
Comment #2
Anonymous (not verified) commentedComment #3
oadaeh commentedI forgot to add earlier that the same functionality in the filters list is not broken (at least not in this way).
Comment #4
Anonymous (not verified) commentedThe rearrange handler for foreach'ing over $form_state['values'] rather than $form_state['values']['fields'].
Comment #5
Psikik commentedI experienced this issue also and the patch applies cleanly and fixes the bug.
Comment #6
oadaeh commentedThe patch in #4 fixes the problem for me, too. It also seems to be correctly formed.
I'm marking it as RTBC, but we may want to wait for the testbot (just in case).
Comment #8
Anonymous (not verified) commented#4: 2002506-Cannot-Rearrange-Views-Fields-004.patch queued for re-testing.
Comment #9
Anonymous (not verified) commentedResetting the issue to RTBC since that is what it was before the testbot went mental.
Comment #10
dries commentedCan we have a test for this please? Thanks!
Comment #11
longwaveThis was apparently mistakenly committed in http://drupalcode.org/project/drupal.git/commitdiff/db2df2d
Comment #12
dries commentedRerolled this patch.
Comment #13
Anonymous (not verified) commentedAdded tests.
Comment #14
damiankloip commentedNice start!
Can we add an '@see \Drupal\views_ui\Form\Ajax\Rearrange' here too.
We don't use private, these should all be protected. Also, the properties need docblocks.
We generally don't use other modules in tests unless we really need to. We try to use views_test_data for as much of this as possible. So I think we should convert to use that maybe.
Rearrange fields? Maybe we should also test the reordering of sorts too.
This could just be 'Creates a random view' but I think it should also say via the wizard/ui too. Also, pretty much the same thing is used in DisplayTest, maybe we should look at moving a form of this method into UiTestBase? Also, we could just use a new test view instead, then there would be no need to create in the test, as we aren't testing that here.
'Tests'
These don't really need to be static properties? If they do, we should use the static keyword and not the actual class name. Seems like a regular property would be fine though.
Needs newline at EOF.
Comment #15
pcambraHere's a rework of the field test, I've removed the new view to rely on the test_view one, I think the only thing that we have left here is decide if we want the sort test or not... (shall we need to add then testing reorder on filters, area handlers, arguments...?)
Comment #16
pcambraIt's better if I give the testbot something to test :P, renaming the class file.
Comment #17
dawehnerThis is basically RTBC. Thank you!
Should also be Tests instead of tests
Nice!
Let's document the two parameters.
Just remove the starting '/' as you never know whether drupal will be installed in a folder.
Comment #18
pcambraFixed comments in #17
Comment #19
dawehnerThank you!
Comment #20
alexpottCan we combine these into one test method... each test necessitates a full re-install of drupal and this seems overkill.
Comment #21
pcambraHere we go :)
Comment #22
tstoecklerThe interdiff definitely fixes #20 and it was RTBC before, so let's do this.
Comment #23
alexpottCommitted f7ded17 and pushed to 8.x. Thanks!