Rearrange of fields gives AJAX HTTP error

bug confirmed

Fixed in the latest commited.

Thanks for reporting the issue.

I am using the latest dev from today (including the commit: "#1113052 by dereine: Allow to rearraenge items again, sigh")

When I select "And/Or" drop-down, I get the following AJAX error:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /admin/structure/views/ajax/rearrange-field/news/block_1/field
StatusText: OK
ResponseText: [{"command":"settings","settings":{"basePath":"\/","ajaxPageState":{"theme":"opa","theme_token":"dh-D7SvBwpxfYYdJhggi0rzDq9V8nYv9OvE37VxMo88","css":[]}},"merge":true},{"command":"alert","text":"The requested page could not be found."}][{"command":"settings","settings":{"basePath":"\/","ajaxPageState":{"theme":"opa","theme_token":"dh-D7SvBwpxfYYdJhggi0rzDq9V8nYv9OvE37VxMo88","css":[]}},"merge":true}]

I do not get any error when clicking on "And/Or" for filter criteria.

+1 - Same as #3

I am using the latest dev from today (including the commit: "#1113052 by dereine: Allow to rearraenge items again, sigh")

After this commit you should see "sort" on the fields/sorts/etc. again.

Can you please verify this with a drush cc all? This would be really helpful, because it works for me fine.
For all things you can imagine: fields, filters, sorts, areas, conditional filters etc.

Upgraded to #afffec8

Doubled down on drush cc all

Error persists on Fields

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /bc/admin/structure/views/ajax/rearrange-field/dealer_locator/page_1/field
StatusText: parsererror
ResponseText: [{"command":"settings","settings":{"basePath":"\/bc\/","ajaxPageState":{"theme":"seven","theme_token":"VwxMyp0U9-XZvvSaTh-xitH4tCtQKWaeCJH91Bsglw8","css":[]},"nice_menus_options":{"delay":800,"speed":1},"admin_menu":{"destination":"destination=admin\/structure\/views\/ajax\/rearrange-field\/dealer_locator\/page_1\/field","hash":"5f0568dda4322ddfdbbc3910a271f517","basePath":"\/bc\/admin_menu","replacements":{".admin-menu-users a":"0 \/ 1"},"toolbar":{"activeTrail":"\/bc\/admin\/structure"}}},"merge":true},{"command":"alert","text":"The requested page could not be found."}][{"command":"settings","settings":{"basePath":"\/bc\/","ajaxPageState":{"theme":"seven","theme_token":"VwxMyp0U9-XZvvSaTh-xitH4tCtQKWaeCJH91Bsglw8","css":[]},"nice_menus_options":{"delay":800,"speed":1},"admin_menu":{"destination":"destination=admin\/structure\/views\/ajax\/rearrange-field\/dealer_locator\/page_1\/field","hash":"5f0568dda4322ddfdbbc3910a271f517","basePath":"\/bc\/admin_menu","replacements":{".admin-menu-users a":"0 \/ 1"},"toolbar":{"activeTrail":"\/bc\/admin\/structure"}}},"merge":true}]

That sure looks like perfectly valid JSON. Hm. I wonder why it's not parsing.

Oh ho. http://jsonformatter.curiousconcept.com/ tells me that's not actually valid JSON after all. There's JSON on that page *twice*.

This is true of *both* invalid JSONs here.

Also, 'needs work' is a status for patches that have failed review and are back to the author for work. Setting an issue to this state causes us to be unable to track it.

The message in there is that the requested page cannot be found.

You may need to rebuild your menu cache for this to work. 'drush cc menu' if using drush, or the cache clear on the performance page.

After studying this, I discovered that our 404 handling is bad. What that JSON is *supposed* to do is give you a popup that says "The requested page cannot be found." Which is a sure indicator you need a menu rebuild.

Just committed a fix to the 404 handling.

No wait. A menu rebuild shouldn't actually fix that for you. Need to think more.

Ok, the problem is that the path is wrong.

It is: /bc/admin/structure/views/ajax/rearrange-field/dealer_locator/page_1/field

It should be: /bc/admin/structure/views/ajax/rearrange/dealer_locator/page_1/field

It's possible that the only thing you need to do is refresh the page with the view?

Refreshing the page does nothing but you're right about the path being incorrect:

When I change rearrange-field to rearrange, I get back what looks like correct markup.

If refresh your page doesn't help you should probably download a the newest version. It's fixed there.

Apologies on the incorrect status.

Upgrading to latest dev. (#81bb43c)

A cache clearing frenzy ensued, including browser cache.

Works for me. Danke.

Thanks for providing that this is fixed!

Nice work! "Sort" now appears and works like a charm.

Thanks!