My View has a Node:Edit-link field. Once you submit the exposed filter form, the edit link ?destination= changes, so that it redirects you back to the form with the filters set how they were when you left -- makes sense.

The problem, however, is that the encoding is failing for some reason, and the redirect back breaks the filters.

After I submit the filter, this is the "edit" link: http://localhost/node/23/edit?destination=admin/workbench/content/my%3Ft...

On the node edit page, the current url is: http://localhost/node/23/edit?destination=admin/workbench/content/my%3Ft...

I'm redirect to: http://localhost/admin/workbench/content/my?title=6type%3DAll6state%3DAl...

Notice ?title=6type=

For some reason, despite the filters I use there is a 6 after the first argument, rather than a &. This is putting the entire URL after title= into the title filter; thus breaking the view.

Comments

mstef’s picture

Status: Active » Closed (cannot reproduce)

This seems to be a problem with an OG contextual filter; not views.

wipeout_dude’s picture

Issue summary: View changes

I have all of a sudden started seeing this on one of my views (Not using OG).. Its been working fine but suddenly started seeing this issue..

When clicking the edit link the destination is..
?destination=node/63/record-list%3Ffield_status_value%3D16title%3D
and probably should be
?destination=node/63/record-list%3Ffield_status_value%3D1%26title%3D

So it's encoding the "&" character as "6" instead of "%26"..

All other views on the site appear tobe fine and this view was working for the last few years so can't see what has happened.. Originally the vew was using ajax but I have disabled that and still get the error..

wipeout_dude’s picture

Version: 7.x-3.5 » 7.x-3.14
Status: Closed (cannot reproduce) » Active
jomarocas’s picture

edit link still no working, any ideas?

joelrotelli’s picture

Exactly the same problem here...Any updates on this ?

DamienMcKenna’s picture

Version: 7.x-3.14 » 7.x-3.x-dev

Does the problem still happen with the latest release? If so, can someone please document the simplest approach to triggering this problem? For example, can you reproduce it using the Admin Views default admin pages?