Sorry for asking "why?" again ;-)

But this doesn't make sense to me.

1. A block is something the user can add/edit/remove. Users are not supposed to play around with google analytics

2. You have to add this block to every page

3. You should make sure it gets called at the end of the body


I would rather make a dashboard field and a new element footer_element (like header_element).
Loader::element('footer_required');

Imho: This is much safer and needs even less work....

No sorries about the same question; if you ask there must be a doubt.

Before opting for a block I considered the two following paths:

1) Embedding the tracker code in the template. This is not immediately feasible because every site has its own tracker account;

2) Some pages/sites may not want to be tracked but still use the template.

The conclusion was that a block - even if must be included manually in every page - offered more flexibility compared to embedding the tracker code in the template.

Again, I might be missing something here...

I would also like to see C5 implementing the CmsMadeSimple idea of global page snippets, i.e. a snippet of code that will be inserted in any page and which is unbound from the template.

I haven't made multiple page sites yet, but I would think you could have a "front" content or forward facing page type that has adsense. I wouldn't put it in a block, put it right in that template in the footer.

Yes, in the past we've always just put our tracking codes in a footer include.

In an upcoming release of c5 we will have a field in the dashboard that will automagically throw whatever you want in the footer of EVERY page.

So remo got it right.
-frz

It might be wise to go with a similar strategy to Wordpress on this type of stuck.

C5 has the concept of blocks (visual represention on individual pages), but perhaps there needs to be a concept of a "plugin" as well.

Plugins could be slightly different because they would be functionality that isn't necessarily visible and can possibly go across multiple/all pages. Then theme developers could support plugins by using the following code in their theme (whether in the footer or not):

<?php Loader::element('plugins'); ?>

In my opinion C5 is still missing the ability of adding content that will be automatically inserted in every page (e.g. Wordpress plugin, site-wide content in CMS Made Simple). If you are interested, have a look at it.

By the way - it seems that C5's visit count really mismatches Google Analytics'. Any idea why?

wow we really need to update the faq page...

you can do this with page defaults quite easily.

the page count in the c5 dashboard is actual page counts - google shows you visitor counts.

You are damn right mate :) Thanks for the suggestion.