Roundup Tracker - Issues

Message5694

Author rouilj
Recipients ber, ezio.melotti, rouilj
Date 2016-07-01.02:21:57
Message-id <1467339717.82.0.198358901658.issue2550785@psf.upfronthosting.co.za>
In-reply-to
I think this will work. Replace the existing:

  <input type="hidden" name="__came_from" tal:attributes="value
string:${request/base}${request/env/PATH_INFO}">

with:

    <input type="hidden" name="__came_from"
      tal:condition="exists:request/env/QUERY_STRING"
      tal:attributes="value 
string:${request/base}${request/env/PATH_INFO}?${request/env/QUERY_STRING}">

    <input type="hidden" name="__came_from"
      tal:condition="not:exists:request/env/QUERY_STRING"
tal:attributes="value
      string:${request/base}${request/env/PATH_INFO}">

This will replicate the current page url with or without the the query
string, so it should redirect to the same page that you are currently
viewing.

Use a form with an action of /${request/env/PATH_INFO} as ezio
did, or ${request/base}${request/env/PATH_INFO}

I would like a solution for:

      tal:attributes="value
     
string:${request/base}${request/env/PATH_INFO}?${request/env/QUERY_STRING}">

to replace ${request/env/QUERY_STRING} with nothing if the
QUERY_STRING doesn't exist. In the current form it breaks with an
exception hence the need to check for the existence of
request/env/QUERY_STRING.

Can somebody test and see if this solves the issue?
History
Date User Action Args
2016-07-01 02:21:57rouiljsetmessageid: <1467339717.82.0.198358901658.issue2550785@psf.upfronthosting.co.za>
2016-07-01 02:21:57rouiljsetrecipients: + rouilj, ber, ezio.melotti
2016-07-01 02:21:57rouiljlinkissue2550785 messages
2016-07-01 02:21:57rouiljcreate