Memory effect

Memory effect

Remember pages already loaded!
– If a page has been visited already and is re-visited, it is there instantly.
– Especially applies to the clicking of the “back button”
– Default: “memoryoff: false” – set to “true” to completely shut off or supply URLs separated by
", "
i.e. comma + space
to exclude from memory effect selectively!
– You might want to do that, if your site has pages that expect to be refreshed dynamically…

The memory cache can be flushed as follows:


(You might want to perform a cache flush e.g. once the user has logged out…)

Goes hand in hand with the prefetch and preview effects

13 thoughts on “Memory”

  1. Hi Arvind,

    I am looking for a way to check if a page has already been cached.
    Within pronto.request I load a query plugin showing a loading progress bar. It would be find to check if the target page has already been loaded so I would prevent the loading indicator from showing.
    Any idea? Thanks, Patrick

    1. Hi Patrick,

      you should be able to do the following:

      if($.pages(url)) { ... //page is in cache}

      ($.pages(url) returns undefined if not cached)

  2. Tested new cache (6/6/14), error after deleting cache on line 360:
    “lk = head.find(“.ajy-link”);”
    Uncaught TypeError: Cannot read property ‘find’ of undefined.

    1. seems like $.getPage(“head”) returns undefined because the if state you added after deleting the cache.

      1. I fixed the problem by adding:
        else {
        return $(o);
        after line 160.

        its working now but after deleting cache and loading page its loads the page with no head (no css and js) and then after the page have been loaded you can see the head injection.. looked badly 😀

        1. Hi Ariel!

          Thanks for testing this new feature further!
          It’s a pity it doesn’t work straight away, but that is probably normal for a new feature…

          Do you have any idea, what the correct algorithm would look like?

          I have the weekend off, so I could dedicate it to fixing this bug in the new feature / finding the correct algorithm…
          Just thinking out loud – maybe it is not correct to fully empty the cache.
          Would it be alright to use your site as a testbed?

          If you don’t want that, then maybe you could post the link via eMail ( and I’ll treat it discretely.
          If you don’t want that either, I could use my partner site: as a testbed instead.

          Sorry about the inconvenience so far, but it is not a trivial addition…

  3. Bug Found: when you use $(this).html the browser will replace & in the javascript inline code into & which will bring to js errors, try to use $(this).text insted. (worked for me).

    another issue, I found no way to empty the cache/memory, and I would like to do so in some cases.

    1. Hi Ariel,

      I’ve added a new method:


      for you… (stands for “flush”)
      Please test!

      Regarding the other issue – which line of code do you mean in “Ajaxify“?

      1. wow, you are fast!
        for the entites bug:
        line 179 and 305, both made errors for me for coverting & in inline javascript into &.

        and for the new flush cache made an error after cleaning cache:
        Uncaught TypeError: Cannot read property ‘find’ of undefined. (line 159 in ajaxify.js)

        1. Hi Ariel,

          Changed line 159.
          Also replaced




          on lines 179, 305 and 312

          Could you re-test please – thanks!

  4. Hi Arvind,
    Great plugin! I’ve got it working.
    How can I flag a page NOT to be cached in plugin ‘memory’. I have pages that need to run a query and display updated data each time the page is hit. So far, the only way I have found to get the ‘updated’ query results to display on the page is to refresh the page but that’s not a good solution.

    1. Hi Bob!

      Thanks for the great idea! Implemented! (please see description on this page)
      Please test, as I think it’ll work but haven’t tested it yet…

      Regards, Arvind

Leave a Reply

Your email address will not be published. Required fields are marked *

Copyright 2005-2016, All rights reserved.
Latest update: 18. October 2016