We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 39426
    • 15 Posts
    Now I realized that all comments are shown and XFPC works.
    But on my home page I created some teaser texts with thumbnail images where I also wanted to show the number of comments which are written. That can be implemented with QuipCount. And these numbers are never updated. When a visitor writes a comment you can't see the right QuipCount number on the home page. I call the snippet QuipCount uncached. It seems to be that XFPC doesn't realize that it has to refresh the home page too.
    What can I do?
      • 40045
      • 534 Posts
      You could, for example, load the comments via AJAX (there is even a snippet for that bundled with XFPC), probably the easiest way, the less easier way would be to customize the QuipComment (or how it's called) snippet, so it deletes the static html file generated by XFPC when a new comment is made...
        • 12410
        • 353 Posts
        Quote from: mindeffects at Nov 12, 2012, 04:33 AM
        If you want to optimize the speed of MODX you should also evaluate the performace tags the system comes with:

        • [^qt^] Query Time (in seconds)
        • [^q^] Queries. Number of requests (queries) made for the page-load where this appears.
        • [^p^] PHP parsing time (in seconds)
        • [^t^] Total load time (in seconds)
        • [^s^] Source of the load (usually, this reads 'database', but presumably this could also be 'cache')

        You could put those MODX-tags into the HTML title-tag so you don't have to look into the sourcecode each time you do a reload. On a live site, this may be not such a good idea and you might want to place them inside a meta-tag:
        <meta name="generator" content="Query time: [^qt^] ([^q^] Queries) // Parse time: [^p^] // Total time: [^t^] // Source: [^s^]">

        RTFM somehow does not contain anything about the ^-tags. :-(

        cheers
        Oliver

        P.S.: It was aweseome meeting you guys at the MODXpo in Utrecht.

        Hmmmm that interesting but I cant get query values
        <meta name="generator" content="Query time: 0.0000 s (0 Queries) // Parse time: 0.2156 s // Total time: 0.2156 s // Source: database">
          • 42046
          • 436 Posts
          Another way I've had success speeding up page loads is using pdoResources from pdoTools in place of getResources when processing of TVs aren't required.

          http://modx.com/extras/package/pdotools

          And FYI, I get the same "Cannot modify header information - headers already sent by" errors when trying to use xfpc.
            • 44258
            • 33 Posts
            Quote from: absent42 at Jul 28, 2013, 08:04 PM
            Another way I've had success speeding up page loads is using pdoResources from pdoTools in place of getResources when processing of TVs aren't required.

            http://modx.com/extras/package/pdotools

            And FYI, I get the same "Cannot modify header information - headers already sent by" errors when trying to use xfpc.

            thanks for this, its so helpful in speeding up the modx.
            • Guys, I am collecting all kind of information to update this post. Please let me know if you have any current info to add to this!

              Any info is helpful. Even small things you found out like this: https://twitter.com/bytethinker/status/679793529128914944
              • To detect internal MODX speed issues, you could use https://github.com/bezumkin/debugParser . There is a version to buy on MODstore (https://modstore.pro/packages/utilities/debugparser), if you don't want to build it yourself. There is a GPM buildable version on https://github.com/Jako/debugParser .