They can be even if you define them in a model but ok, you can define
them in a view but must come before the extend.
{{
response.title='My Product view'
response.meta.keywords='phones,calls,smartphone'
response.meta.description='This is a phone seller site made with
web2py'
response.meta.author='me'
}}
{{extend 'layout.html'}}
....
On Aug 6, 9:04 am, Bruno Rocha <rochacbr...@gmail.com> wrote:
> 2010/8/6 mdipierro <mdipie...@cs.depaul.edu>
>
> > You should this in a model, before the view is executed:
>
> > response.title='My Product view'
> > response.meta.keywords='phones,calls,smartphone'
> > response.meta.description='This is a phone seller site made with
> > web2py'
> > response.meta.author='me'
>
> > The sitemap cannot be accomplished by a helper. It needs a helper and
> > a storage.
>
> In this example you are declaring globally.
> The problem is that SEO variables. must be unique for each view, and
> sometimes, must be built according to the parameters received, as in the
> example of Canonical URLS.
>
> take this example:
> / Showproduct/01 the url needs to be changed to /showproduct/foo-smartphone
>
> and also title of the page needs to be amended in accordance with the
> product,
> response.title = "my phone shop | phones | Smartphone foo"
> response.keywords = "foo, phone, brand, 3G, 5 mp cam"
>
> Regarding the sitemap is a good point to look how this is being done out
> there, to get an
> idea:http://sitemaps.org/protocol.phphttp://docs.djangoproject.com/en/dev/ref/contrib/sitemaps/?from=olddocs
> COOL
> FEATUREhttp://docs.djangoproject.com/en/dev/ref/contrib/sitemaps/?from=olddo...http://code.google.com/p/django-seo-tools/
>
>
