Ditto intermittently fails to display template variables

I guess you first need to follow two tutorials, otherwise you will not be able to understand what I am talking about.
Tut1: http://codingpad.maryspad.com/2009/03/28/building-a-website-with-modx-for-newbies-part-1-introduction/
Tut2: http://net.tutsplus.com/tutorials/other/working-with-a-content-management-framework-modx/

Quote from: microcipcip at Apr 18, 2013, 10:20 AM

I guess you first need to follow two tutorials, otherwise you will not be able to understand what I am talking about.
Tut1: http://codingpad.maryspad.com/2009/03/28/building-a-website-with-modx-for-newbies-part-1-introduction/
Tut2: http://net.tutsplus.com/tutorials/other/working-with-a-content-management-framework-modx/

Thank you microcipcip. I'll take a look at those tutorials and see if I can get my head around this .... Sam

I'm back again microcipcip. I wanted to try one more time to run Ditto uncached (your suggestion).

The problem I have is that Ditto tries to run a document resource that contains eForm uncached.

When Ditto is cached and eForm is uncached, eForm works. (See attachment 1)

When Ditto is uncached and eForm is also uncached, then eForm will not work. (See attachment 2)

Do you know why? I would like to try running Ditto uncached.

Thanks ... Sam

Try Ditto uncached and eForm cached. Not sure if that would work, but it is worth trying.

I clearly don't understand the concept of cacheing when a heirarchy of cached elements are involved.

If Ditto is higher in the pecking order than the document it loads (that is Ditto loads the document resource) if Ditto is running uncacheable but the page it's running in IS cacheable, and ALSO the document ditto is loading IS cachable (eForm) ..... then, what happens?

In other words, MODx loads a cacheable page which happens to be in the cache, that cacheable page then runs Ditto which itself is running uncached, does that then force a fresh load of the document (the sidebox) that the uncacheable Ditto is loading? As an aside, does it even matter that the sidebox itself is marked cacheable as a Resource ID?

My problem is that I just don't understand multiple layers of "cacheability". This is a mystery in MODx.

??? Sam

Quote from: samg at Apr 29, 2013, 09:38 AM

I clearly don't understand the concept of cacheing when a heirarchy of cached elements are involved.

If Ditto is higher in the pecking order than the document it loads (that is Ditto loads the document resource) if Ditto is running uncacheable but the page it's running in IS cacheable, and ALSO the document ditto is loading IS cachable (eForm) ..... then, what happens?

In other words, MODx loads a cacheable page which happens to be in the cache, that cacheable page then runs Ditto which itself is running uncached, does that then force a fresh load of the document (the sidebox) that the uncacheable Ditto is loading? As an aside, does it even matter that the sidebox itself is marked cacheable as a Resource ID?

My problem is that I just don't understand multiple layers of "cacheability". This is a mystery in MODx.

??? Sam

Hi Sam,

Sorry I don't know the answer to your question, I think that the cache/uncache of MODX Evolution is buggy, you may have to start a thread and ask this specific question to someone that knows how the core works.

OK, I'll try this out by trial and error. Right now the various sidebox resources had been coded as "cacheable". I made them uncacheable to see if they will be retrieved on the fly when needed. If so that will solve my problem.

If that doesn't work, I'll change the template and try coding Ditto as uncacheable and the document displayed (containing eForm code) as cacheable.

Finally, I'll go the the whole enchilada and code the entire page (Resource ID) as uncacheable. I'm not nearly as concerned about caching performance as I am about the disappearing sideboxes.

Thanks, microcipcip.