Symphony.

Had a look for this in the forum but wasn’t sure if it’s possible.. Was looking at a way to generate static html pages from each entry in a datasource? is this something that could be done with Symphony?

To what end? Could you give us an example of how the technique would be used? The workflow?

Have a section called jobs and each entry has a url such as domain.co.uk/jobs/view/{entry-id}

At present these entries are stored in the Database and retrieved when entry is selected.. But as this section grows I get the feeling that the datasource might get larger and demand more processing to retrieve all entries.. Cache Lite does a good job at the moment, but there are a few things I wish were not cached as I would like a more accurate reading of page views from the site.. so serving up static pages from section entries seemed a logical thought! Analytics does this, but I really want the Page views to be within the CMS itself as well and I can only think of serving up the page as a static page would help this. thoughts?

Sounds like you want DS fragment caching instead of full page output caching?

But CacheLite actually does exactly this — it serves a static HTML version of your rendered page. If I remember correctly you’re using Incremement Number field to count the number of views of each job? If so, neither CacheLite not Cacheable Datasource will help you: both will cache the output of the DS and prevent it executing.

Hi nickdunn,

Yes Cache Lite is serving up a massive help for this site as far as Page rendering times are concerned.. the combo of Cache Lite and Number Field is causing inaccurate counts of page views and thought if the page itself static and used page header info to count views (probably talking rubbish here cos I’m not absolutely sure how the Number Views field processes the page view itself.)

Are you Saying the DS fragment Caching would solve this or would I be restricted on page views once more? Thanks for your help here.

EDIT Tried to keep this to a single post but thought it was a good question with regards to generating static pages anyway.. just in case the flagging of repeat posts comes a knocking :)

The Increment Number field increments each time the field is pulled into the XML via a Data Source. So if the output of your DS doesn’t execute (whether you cache the entire page, or the DS itself) the result will be the same.

You could potentially write an Extension to track Job views. When CacheLite is installed, some delegates still fire on the frontend so you can still execute some Symphony logic.