Stripping some characters in the simple edit url

Squiz Matrix Support
1

Hi,
I'm having a weird thing happening in Simple Edit.

Loading the simple edit screen fails to load the main screen (top purple bar and side purple bar load fine) because it cannot find the URL.



Both in the notice and in the error log I've noticed that the URL being looked for is as follow:

    cms.mydomain.com/cmstest/_edit/http2F2Fcmstest3FSQ_ACTION26hipo_source_code_name=hipo_job_acquire_locks-e4a6222cdb5b34375400904f03d8e6a5


In the address bar of the browser I get this:
    http://cms.mydomain.com/cmstest/_edit/?sq_redirect_url=http2F2Fcmstest3FSQ_ACTION26hipo_source_code_name%3Dhipo_job_acquire_locks-e4a6222cdb5b34375400904f03d8e6a5


As you can see the %2F became 2F (etc..) in the request.
Also in the address bar the sq_redirect_url reads: http2F2Fcmstest (which is equivalent to http//cmstest). Am I right to assume the http// shouldn't be there?

Version 3.8.2 - Oracle (but the same version on another environment works).

Anyone ever encountered this?
Any hints as to where I should be looking to fix it?

Cheers.
2

Its a known bug. We're working on fixing it at the moment.

3

[quote]Its a known bug. We’re working on fixing it at the moment.
[right][post=“10083”]<{POST_SNAPBACK}>[/post][/right][/quote]



Any work around for the moment?



Edited to say: how come it is working on my test environment?

4

Don't use simple edit? :) Its a problem with keyword replacement removing HTML encoded entities in Simple Edit.

[quote]Edited to say: how come it is working on my test environment?
[right][post="10085"]<{POST_SNAPBACK}>[/post][/right][/quote]

Different version of Matrix perhaps?
5

Don't know if it is related but one of my user complained his asset listing keyword were not working anymore.



What bug number is it? I couldn't find it in the bug tracker.



Testing environment is the same version of Matrix, but it works because there is no layout applied.

6

[quote]What bug number is it? I couldn’t find it in the bug tracker.
[right][post=“10087”]<{POST_SNAPBACK}>[/post][/right][/quote]



I think its an internal bug (i.e. we spotted it and are fixing it internally). One of the developers probably knows more.

7

There was an issue with the keywords that we found - causing the above problems were caused by URL-encoded paths (essentially any URL that was urlencoded would be prone to problems, as it would confuse pairs of % signs with keywords and replace them with nothing - which shouldn't be happening) - and have fixed in the 3.8 and Dev branches.