Document Expired page on using Back Button in List Views

5 posts by 3 authors in: Forums > CMS Builder
Last Post: February 23, 2016   (RSS)

By In-House-Logic - February 18, 2016

Hi all,

Is there anything that we can do to keep this Document Expired message from the users when use the back button in CMSBuilder's list views? I understand why this might have a place when editing a record but on the list view pages it really feels wrong.

This appears to be happening on the major browsers on Widows boxes and I'd assume others clients and OS's too.

Jayme

By In-House-Logic - February 18, 2016

Hi Damon,

The site in question is running  v.2.65 (Build 1122). Sorry, I meant to include that in the OP.

The steps are very basic:

  1. Log into the CMS.
  2. Open a list view.
  3. Open another list view page OR move to page 2 or later of the first list view.
  4. Click browser back button.
  5. Bask in the beauty of a Document Expired message.
  6. Rinse and repeat as desired.

This is not happening on other installs so there's something local causing the issue. The site has some custom plug-ins for Adv.Search and elsewhere that were built by the good folks at IAT over the years. Greg knows the site as GSG and can access it if you'd like a peek under the hood. Probably just a bit of legacy code gumming up the works.

Many thanks,

Jayme

By gregThomas - February 22, 2016 - edited: February 23, 2016

Hi Jayme, 

I was able to recreate the issue, the reason it's happening is because we had to update this sites section list page to use POST instead of GET for submitting forms. We did this as there are a lot of advanced filtering fields in the games section, and often the search request would become larger than what browsers are allowed to send with a GET request.

Most browsers stop users re-submitting forms that are sent via POST (as this is the form type you'd use for payments, booking forms, uploads, etc) with the back / forward buttons with the "Document Expired" message, but this doesn't happen with GET requests. We've previously tried creating a plugin to get around this issue, but it caused other browser issues we couldn't resolve.  In this case, the best solution is to avoid using the forward and back buttons while navigating the section editors.

Cheers,

Greg

Greg Thomas







PHP Programmer - interactivetools.com

By In-House-Logic - February 23, 2016

Thank you Greg. That's unfortunate but I think the client will understand the circumstances here.

J.