myContent pages don't get cached

[dcanazz]

Being my first post here, I'd start with my sincere congratulations for this very good piece of software.
The only weak point of this cms is the lack of developer documentation but ... I don't think you need me, to know it.
I am setting up a site for a "customer" using (for now) 0.10rc2, and I wrote a few extra components to suite their needs.
My  main add-on is a new content-type module allowing attachments and images to be inserted in the page.
I had to modify some core files to manage this - I know it's dangerous etc. etc.
My problem is: the pages with contentype == myContent never get cached.
I think I understood the caching is managed by Smarty, I would like some hints to find out why the pages aren't cached.
Is there a way to print out debug information apart from putting echo statements around?
Thank you,
Daniele

[megabob3]

You have the necessary skill to modify the CORE and nope to create a NEW MODULE?!

Report your work on a new module and you will resolve cache problem.

In my opinion you took a bad way.

Bye
Roberto.

[dcanazz]

Roberto,
thank you for your reply. Maybe the problem was my English, or maybe you overlooked some part of my post.
I humbly think I have the skill to create a new module since

>> [my post] My  main add-on is a new content-type module allowing [...]

and the module works as intended and gently interfaces with the core with my few modifications added.

I don't understand what you mean by "Report your work on a new module and you will resolve cache problem".
Do you mean I should post my module here? Or maybe that I should convert it to a "module"?
In the first case, the module is "ready" but it won't work without those core modifications I spoke about so there is no point in posting it at least for now. Furthermore, I am not asking anybody to do debugging work for me, just some hints to understand how the caching part of the system works saving me some digging into the smarty  or cmsms code.
In the second case, as I wrote a few lines above, it's already a module, written to the best of my knowledge using as examples the modules included in the distribution and using the guides on the wiki as documentation.
Lastly, maybe you're right saying

> In my opinion you took a bad way

but I assure you I always try to have a "Keep It Simple, Stupid" attitude, and I didn't find a simpler way.
Maybe you want me to elaborate on this point - i.e. what convinced me to go this way?

Bye and thanks again,

Daniele

[megabob3]

Ooo you are right, it's more probably that my english is worst of yours

I will contact you via PM, i guess you are italian like me

[Ted]

Modules will never cache.  The idea of them is that they're dynamic is some way or another, and caching their output would be a "bad" thing.

However, content types are also dynamically loaded.  And not being modules, they do cache properly.

Take a look in lib/contenttypes.  You'll see files for the 4 main content types in CMSMS.  You can probably just take the Content type, copy it, and modify it to your needs.  When you're done, it'll "just work".

Granted, it's not as convienent as the module approach, but for a custom work that probably won't get distributed, it shouldn't be a big problem.

[nils73]

Every time I take a look around here, there is something new:

Modules will never cache.  The idea of them is that they're dynamic is some way or another, and caching their output would be a "bad" thing.

Brings me back to search and yet another question I already asked somewhere. Do you have a draft on how CMSMS works, what gets cached, what preRender does, when does postRender take effect and stuff like that? I would really like to create something like a visual model that describes how CMSMS works. It took me quite a lot of time to understand how it works and I am still unable to figure out most things on my own.

Regards,
Nils

[Ted]

Well, quick roadmap:

0.10 finally gets released.  The reason that this is taking so long is because functionally, this will be a pre1.0 release.  The span between 0.10 and 1.0 will be approximately 2-3 months.  This WHOLE period will be dedicated to bugs, little fixes and documentation.  I'm dreading it, but I know it has to happen and I'm the one that has to do it.

So, no, there isn't something there yet.  And I know it desperately needs to be, but I don't want to write anything twice (since once is hard enough), so it will have to wait until 0.10 is done.

And if someone wants to start, they're more than welcome to.  I'm available always for questions and descriptions.  Putting it into real text is the hard part for me...