[web2py] Re: GRID selectable inside component
Oops, got it. Still can't reproduce.
On Thursday, December 31, 2015 at 5:23:38 PM UTC-5, Krzysztof Socha wrote:
>
> As I wrote:
>
> 2.13.4-stable+timestamp.2015.12.26.04.59.39
> (Running on nginx/1.4.6, Python 2.7.6)
>
> Strange... I will have to investigate a bit more, than. I will report
> back, what I find.
>
> Krzysztof.
>
> On Thursday, December 31, 2015 at 10:38:10 PM UTC+1, Anthony wrote:
>>
>> Sorry, tried your exact code and it works for me. Which version of
>> web2py? Maybe attach a minimal app that demonstrates the problem.
>>
>> Anthony
>>
>> On Thursday, December 31, 2015 at 3:39:37 PM UTC-5, Krzysztof Socha wrote:
>>>
>>> Anthony,
>>>
>>> Thank you for (very) quick reaction! And Happy New Year! ;)
>>>
>>> Here is an example:
>>>
>>> I define a grid in the following action:
>>> def grid_test():
>>> grid = SQLFORM.grid(db.project, formname='grid_test',selectable=[('Test',
>>> lambda ids: 1/0)])
>>> response.view = 'project/grid.load'
>>> return dict(grid=grid)
>>>
>>> ...of course the expected behavior is that the 'Test' action will cause
>>> an error (division by zero). Indeed, this happens if I simply put such
>>> defined grid as part of regular controller action.
>>>
>>> However, when I put it in a component:
>>>
>>> {{=LOAD('project','grid_test.load', ajax=True)}}
>>>
>>> where the grid.load looks like this:
>>>
>>> {{=grid}}
>>>
>>> Pressing the 'Test' button does not cause the error - presumably because
>>> the selectable action is not executed at all...
>>>
>>> I hope this is clear enough. In my code, I actually tried to do a
>>> redirect, but the result is exactly the same - the selectable action does
>>> not appear to execute... I just tested this on:
>>>
>>> 2.13.4-stable+timestamp.2015.12.26.04.59.39
>>> (Running on nginx/1.4.6, Python 2.7.6)
>>>
>>> Krzysztof.
>>>
>>> On Thursday, December 31, 2015 at 8:41:46 PM UTC+1, Anthony wrote:
A basic example works for me. Can you show some code that you know
exhibits the problem?
Anthony
On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha
wrote:
>
> I noticed a similar thing... I need two grids on a page. As
> documented, it does not work very well to simply put them in one
> controller
> function. Hence, I tried with LOADing a component. This generally works,
> but I cannot get the selectable actions to work. I have defined custom
> selectable actions and they work fine if the gird is not inside a
> component. As soon, as I load it as a component, nothing happens. It
> seems
> that the form is submitted, but the selectable action is not executed. A
> bug somewhere? Or is there another way of doing this?
>
> Krzysztof.
>
> On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart
> wrote:
>>
>> I have a grid inside a component inside a component which has
>> selectable set to run a function that assigns the ids to a session
>> variable. When inside the component it does not work when i click submit
>> I
>> can tell that the page is being reloaded but the callback does not run.
>> I
>> know that the code works because if I go to the .load page directly and
>> try
>> it works as expected. But from the component page it doesnt execute the
>> callback.
>>
>>
>>
>> selectable = [('Create Invoice', lambda ids: [selectabletest(ids)],
>> 'btn btn-info btn-md')]
>> grid2 = SQLFORM.grid(query, selectable=selectable,
>> args=request.args[:1], formname='invgrid', user_signature=False)
>>
>> def selectabletest(ids):
>> session.lambdatest = ids
>>
>> This message is for named person(s) only. It may contain
>> confidential and/or legally privileged information. No confidentiality
>> or
>> privilege is waived or lost should mis-transmission occur. If you
>> receive
>> this message in error, delete it (and all copies) and notify the sender.
>>
>> You must not, directly or indirectly,use, disclose, distribute, print,
>> or
>> copy any part of this message if you are not the intended recipient. GAD
>> GROUP TECHNOLOGY, INC. reserves the right to monitor all e-mail
>> communications through its networks.
>>
>> Any views expressed in this message are those of the individual
>> sender, except where the message states otherwise and the sender is
>> authorized to state them to be the views of any such entity.
>>
>> This e-mail has been virus and content scanned by GAD GROUP
>> TECHNOLOGY, INC.
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group
[web2py] Re: GRID selectable inside component
As I wrote:
2.13.4-stable+timestamp.2015.12.26.04.59.39
(Running on nginx/1.4.6, Python 2.7.6)
Strange... I will have to investigate a bit more, than. I will report back,
what I find.
Krzysztof.
On Thursday, December 31, 2015 at 10:38:10 PM UTC+1, Anthony wrote:
>
> Sorry, tried your exact code and it works for me. Which version of web2py?
> Maybe attach a minimal app that demonstrates the problem.
>
> Anthony
>
> On Thursday, December 31, 2015 at 3:39:37 PM UTC-5, Krzysztof Socha wrote:
>>
>> Anthony,
>>
>> Thank you for (very) quick reaction! And Happy New Year! ;)
>>
>> Here is an example:
>>
>> I define a grid in the following action:
>> def grid_test():
>> grid = SQLFORM.grid(db.project, formname='grid_test',selectable=[('Test',
>> lambda ids: 1/0)])
>> response.view = 'project/grid.load'
>> return dict(grid=grid)
>>
>> ...of course the expected behavior is that the 'Test' action will cause
>> an error (division by zero). Indeed, this happens if I simply put such
>> defined grid as part of regular controller action.
>>
>> However, when I put it in a component:
>>
>> {{=LOAD('project','grid_test.load', ajax=True)}}
>>
>> where the grid.load looks like this:
>>
>> {{=grid}}
>>
>> Pressing the 'Test' button does not cause the error - presumably because
>> the selectable action is not executed at all...
>>
>> I hope this is clear enough. In my code, I actually tried to do a
>> redirect, but the result is exactly the same - the selectable action does
>> not appear to execute... I just tested this on:
>>
>> 2.13.4-stable+timestamp.2015.12.26.04.59.39
>> (Running on nginx/1.4.6, Python 2.7.6)
>>
>> Krzysztof.
>>
>> On Thursday, December 31, 2015 at 8:41:46 PM UTC+1, Anthony wrote:
>>>
>>> A basic example works for me. Can you show some code that you know
>>> exhibits the problem?
>>>
>>> Anthony
>>>
>>> On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha
>>> wrote:
I noticed a similar thing... I need two grids on a page. As documented,
it does not work very well to simply put them in one controller function.
Hence, I tried with LOADing a component. This generally works, but I
cannot
get the selectable actions to work. I have defined custom selectable
actions and they work fine if the gird is not inside a component. As soon,
as I load it as a component, nothing happens. It seems that the form is
submitted, but the selectable action is not executed. A bug somewhere? Or
is there another way of doing this?
Krzysztof.
On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart
wrote:
>
> I have a grid inside a component inside a component which has
> selectable set to run a function that assigns the ids to a session
> variable. When inside the component it does not work when i click submit
> I
> can tell that the page is being reloaded but the callback does not run. I
> know that the code works because if I go to the .load page directly and
> try
> it works as expected. But from the component page it doesnt execute the
> callback.
>
>
>
> selectable = [('Create Invoice', lambda ids: [selectabletest(ids)],
> 'btn btn-info btn-md')]
> grid2 = SQLFORM.grid(query, selectable=selectable,
> args=request.args[:1], formname='invgrid', user_signature=False)
>
> def selectabletest(ids):
> session.lambdatest = ids
>
> This message is for named person(s) only. It may contain confidential
> and/or legally privileged information. No confidentiality or privilege
> is
> waived or lost should mis-transmission occur. If you receive this
> message
> in error, delete it (and all copies) and notify the sender. You must
> not,
> directly or indirectly,use, disclose, distribute, print, or copy any part
> of this message if you are not the intended recipient. GAD GROUP
> TECHNOLOGY, INC. reserves the right to monitor all e-mail communications
> through its networks.
>
> Any views expressed in this message are those of the individual
> sender, except where the message states otherwise and the sender is
> authorized to state them to be the views of any such entity.
>
> This e-mail has been virus and content scanned by GAD GROUP
> TECHNOLOGY, INC.
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: GRID selectable inside component
Sorry, tried your exact code and it works for me. Which version of web2py?
Maybe attach a minimal app that demonstrates the problem.
Anthony
On Thursday, December 31, 2015 at 3:39:37 PM UTC-5, Krzysztof Socha wrote:
>
> Anthony,
>
> Thank you for (very) quick reaction! And Happy New Year! ;)
>
> Here is an example:
>
> I define a grid in the following action:
> def grid_test():
> grid = SQLFORM.grid(db.project, formname='grid_test',selectable=[('Test',
> lambda ids: 1/0)])
> response.view = 'project/grid.load'
> return dict(grid=grid)
>
> ...of course the expected behavior is that the 'Test' action will cause an
> error (division by zero). Indeed, this happens if I simply put such defined
> grid as part of regular controller action.
>
> However, when I put it in a component:
>
> {{=LOAD('project','grid_test.load', ajax=True)}}
>
> where the grid.load looks like this:
>
> {{=grid}}
>
> Pressing the 'Test' button does not cause the error - presumably because
> the selectable action is not executed at all...
>
> I hope this is clear enough. In my code, I actually tried to do a
> redirect, but the result is exactly the same - the selectable action does
> not appear to execute... I just tested this on:
>
> 2.13.4-stable+timestamp.2015.12.26.04.59.39
> (Running on nginx/1.4.6, Python 2.7.6)
>
> Krzysztof.
>
> On Thursday, December 31, 2015 at 8:41:46 PM UTC+1, Anthony wrote:
>>
>> A basic example works for me. Can you show some code that you know
>> exhibits the problem?
>>
>> Anthony
>>
>> On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha
>> wrote:
>>>
>>> I noticed a similar thing... I need two grids on a page. As documented,
>>> it does not work very well to simply put them in one controller function.
>>> Hence, I tried with LOADing a component. This generally works, but I cannot
>>> get the selectable actions to work. I have defined custom selectable
>>> actions and they work fine if the gird is not inside a component. As soon,
>>> as I load it as a component, nothing happens. It seems that the form is
>>> submitted, but the selectable action is not executed. A bug somewhere? Or
>>> is there another way of doing this?
>>>
>>> Krzysztof.
>>>
>>> On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart
>>> wrote:
I have a grid inside a component inside a component which has
selectable set to run a function that assigns the ids to a session
variable. When inside the component it does not work when i click submit I
can tell that the page is being reloaded but the callback does not run. I
know that the code works because if I go to the .load page directly and
try
it works as expected. But from the component page it doesnt execute the
callback.
selectable = [('Create Invoice', lambda ids: [selectabletest(ids)],
'btn btn-info btn-md')]
grid2 = SQLFORM.grid(query, selectable=selectable,
args=request.args[:1], formname='invgrid', user_signature=False)
def selectabletest(ids):
session.lambdatest = ids
This message is for named person(s) only. It may contain confidential
and/or legally privileged information. No confidentiality or privilege is
waived or lost should mis-transmission occur. If you receive this message
in error, delete it (and all copies) and notify the sender. You must not,
directly or indirectly,use, disclose, distribute, print, or copy any part
of this message if you are not the intended recipient. GAD GROUP
TECHNOLOGY, INC. reserves the right to monitor all e-mail communications
through its networks.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized to
state them to be the views of any such entity.
This e-mail has been virus and content scanned by GAD GROUP TECHNOLOGY,
INC.
>>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: GRID selectable inside component
Anthony,
Thank you for (very) quick reaction! And Happy New Year! ;)
Here is an example:
I define a grid in the following action:
def grid_test():
grid = SQLFORM.grid(db.project, formname='grid_test',selectable=[('Test',
lambda ids: 1/0)])
response.view = 'project/grid.load'
return dict(grid=grid)
...of course the expected behavior is that the 'Test' action will cause an
error (division by zero). Indeed, this happens if I simply put such defined
grid as part of regular controller action.
However, when I put it in a component:
{{=LOAD('project','grid_test.load', ajax=True)}}
where the grid_test.load looks like this:
{{=grid}}
Pressing the 'Test' button does not cause the error - presumably because
the selectable action is not executed at all...
I hope this is clear enough. In my code, I actually tried to do a redirect,
but the result is exactly the same - the selectable action does not appear
to execute... I just tested this on:
2.13.4-stable+timestamp.2015.12.26.04.59.39
(Running on nginx/1.4.6, Python 2.7.6)
Krzysztof.
On Thursday, December 31, 2015 at 8:41:46 PM UTC+1, Anthony wrote:
>
> A basic example works for me. Can you show some code that you know
> exhibits the problem?
>
> Anthony
>
> On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha wrote:
>>
>> I noticed a similar thing... I need two grids on a page. As documented,
>> it does not work very well to simply put them in one controller function.
>> Hence, I tried with LOADing a component. This generally works, but I cannot
>> get the selectable actions to work. I have defined custom selectable
>> actions and they work fine if the gird is not inside a component. As soon,
>> as I load it as a component, nothing happens. It seems that the form is
>> submitted, but the selectable action is not executed. A bug somewhere? Or
>> is there another way of doing this?
>>
>> Krzysztof.
>>
>> On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart
>> wrote:
>>>
>>> I have a grid inside a component inside a component which has selectable
>>> set to run a function that assigns the ids to a session variable. When
>>> inside the component it does not work when i click submit I can tell that
>>> the page is being reloaded but the callback does not run. I know that the
>>> code works because if I go to the .load page directly and try it works as
>>> expected. But from the component page it doesnt execute the callback.
>>>
>>>
>>>
>>> selectable = [('Create Invoice', lambda ids: [selectabletest(ids)], 'btn
>>> btn-info btn-md')]
>>> grid2 = SQLFORM.grid(query, selectable=selectable,
>>> args=request.args[:1], formname='invgrid', user_signature=False)
>>>
>>> def selectabletest(ids):
>>> session.lambdatest = ids
>>>
>>> This message is for named person(s) only. It may contain confidential
>>> and/or legally privileged information. No confidentiality or privilege is
>>> waived or lost should mis-transmission occur. If you receive this message
>>> in error, delete it (and all copies) and notify the sender. You must not,
>>> directly or indirectly,use, disclose, distribute, print, or copy any part
>>> of this message if you are not the intended recipient. GAD GROUP
>>> TECHNOLOGY, INC. reserves the right to monitor all e-mail communications
>>> through its networks.
>>>
>>> Any views expressed in this message are those of the individual sender,
>>> except where the message states otherwise and the sender is authorized to
>>> state them to be the views of any such entity.
>>>
>>> This e-mail has been virus and content scanned by GAD GROUP TECHNOLOGY,
>>> INC.
>>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: why you should upgrade to web2py 2.13.4
On Tuesday, December 29, 2015 at 6:34:38 PM UTC-8, Dave S wrote: > > > > On Tuesday, December 29, 2015 at 4:41:31 PM UTC-8, Dave S wrote: >> >> >> See below: >> >> On Saturday, December 26, 2015 at 12:22:27 AM UTC-8, Massimo Di Pierro >> wrote: >>> >>> There are many reasons you should upgrade, depending on which version >>> you are using now: >>> >>> - to help us make sure we did not break backward compatibility. If your >>> existing app does not work with 2.13.4 (and it should) you give us a chance >>> to fix the problem. If no, any potential incompatibility will propagate >>> forward making it more difficult for us to fix it later, and more difficult >>> for you to upgrade. >>> >> >> Looks good so far. Limited testing of one app (the one that has the most >> code, as it happens, though it isn't exactly a Massive Super Site). Went >> from 2.12.3 to 2.13.4 (on creaky old Fedora 16) and didn't see any problems >> with DB (SQLite), http access, CSS, or the admin page for DBs. >> > > Footnote: I'm a BeyondCompare user, which made it very easy for me to > migrate. Unzip into a 2.13 directory, use the folder compare between that > and the existing (2.12) directory to set up the apps in their new home, > then do a folder compare between the Welcome app and my apps to catch all > the changed files in the js, css, etc sub-dirs. > > >> (Looks like ticket display shows the version of the currently running >> instance, not the version that created the ticket.) >> >> >>> - to take advantage of new features. For example the awesome JWT feature >>> that allows to create API tokens and use them for authentication without >>> hitting the database. >>> >> >> I'm drooling ... >> >> >>> - there is also an important security bug fix in 2.13.4 related to >>> auth.settings.registration_requires_approval=True. The bug allows a newly >>> registered user to bypass the approval process and approve himself/herself. >>> Under come conditions. This is now fixed. >>> >>> >> Not using this yet, so untested. >> >> I have the Windders version downloaded, but haven't deployed it ... I was >> going to, because that's an even smaller app, but didn't get there before >> wandering away aimlessly. >> >> I will mention any issues should I encounter any. >> > Now I've done the same with my "baby app" that's a csv demo. Still awaiting issues to mention. > >> Thanks Massimo, Niphlod, Anthony, and the others! >> >> /dps >> > > Repeated thanks! > > Repeatedly -d -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Re: GRID selectable inside component
A basic example works for me. Can you show some code that you know exhibits
the problem?
Anthony
On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha wrote:
>
> I noticed a similar thing... I need two grids on a page. As documented, it
> does not work very well to simply put them in one controller function.
> Hence, I tried with LOADing a component. This generally works, but I cannot
> get the selectable actions to work. I have defined custom selectable
> actions and they work fine if the gird is not inside a component. As soon,
> as I load it as a component, nothing happens. It seems that the form is
> submitted, but the selectable action is not executed. A bug somewhere? Or
> is there another way of doing this?
>
> Krzysztof.
>
> On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart
> wrote:
>>
>> I have a grid inside a component inside a component which has selectable
>> set to run a function that assigns the ids to a session variable. When
>> inside the component it does not work when i click submit I can tell that
>> the page is being reloaded but the callback does not run. I know that the
>> code works because if I go to the .load page directly and try it works as
>> expected. But from the component page it doesnt execute the callback.
>>
>>
>>
>> selectable = [('Create Invoice', lambda ids: [selectabletest(ids)], 'btn
>> btn-info btn-md')]
>> grid2 = SQLFORM.grid(query, selectable=selectable, args=request.args[:1],
>> formname='invgrid', user_signature=False)
>>
>> def selectabletest(ids):
>> session.lambdatest = ids
>>
>> This message is for named person(s) only. It may contain confidential
>> and/or legally privileged information. No confidentiality or privilege is
>> waived or lost should mis-transmission occur. If you receive this message
>> in error, delete it (and all copies) and notify the sender. You must not,
>> directly or indirectly,use, disclose, distribute, print, or copy any part
>> of this message if you are not the intended recipient. GAD GROUP
>> TECHNOLOGY, INC. reserves the right to monitor all e-mail communications
>> through its networks.
>>
>> Any views expressed in this message are those of the individual sender,
>> except where the message states otherwise and the sender is authorized to
>> state them to be the views of any such entity.
>>
>> This e-mail has been virus and content scanned by GAD GROUP TECHNOLOGY,
>> INC.
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: GRID selectable inside component
I noticed a similar thing... I need two grids on a page. As documented, it
does not work very well to simply put them in one controller function.
Hence, I tried with LOADing a component. This generally works, but I cannot
get the selectable actions to work. I have defined custom selectable
actions and they work fine if the gird is not inside a component. As soon,
as I load it as a component, nothing happens. It seems that the form is
submitted, but the selectable action is not executed. A bug somewhere? Or
is there another way of doing this?
Krzysztof.
On Wednesday, October 15, 2014 at 7:46:56 PM UTC+2, LaDarrius Stewart wrote:
>
> I have a grid inside a component inside a component which has selectable
> set to run a function that assigns the ids to a session variable. When
> inside the component it does not work when i click submit I can tell that
> the page is being reloaded but the callback does not run. I know that the
> code works because if I go to the .load page directly and try it works as
> expected. But from the component page it doesnt execute the callback.
>
>
>
> selectable = [('Create Invoice', lambda ids: [selectabletest(ids)], 'btn
> btn-info btn-md')]
> grid2 = SQLFORM.grid(query, selectable=selectable, args=request.args[:1],
> formname='invgrid', user_signature=False)
>
> def selectabletest(ids):
> session.lambdatest = ids
>
> This message is for named person(s) only. It may contain confidential
> and/or legally privileged information. No confidentiality or privilege is
> waived or lost should mis-transmission occur. If you receive this message
> in error, delete it (and all copies) and notify the sender. You must not,
> directly or indirectly,use, disclose, distribute, print, or copy any part
> of this message if you are not the intended recipient. GAD GROUP
> TECHNOLOGY, INC. reserves the right to monitor all e-mail communications
> through its networks.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorized to
> state them to be the views of any such entity.
>
> This e-mail has been virus and content scanned by GAD GROUP TECHNOLOGY,
> INC.
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: Place different response.meta.description on each page
in your controllers/default.py def page_one(): response.meta.description = 'page_one' return dict(foo='bar') def page_two(): response.meta.description = 'page_two' return dict(foo='baz') etc etc etc On Thursday, December 31, 2015 at 3:27:07 AM UTC+1, Joe wrote: > > Hello Niphlod, > > Thanks for your reply. > > I tried to do that several different ways but I am sure I did it wrong. > Can you please let me know how to set this exactly? > > Thanks > > > On Wednesday, December 30, 2015 at 4:35:13 PM UTC+8, Niphlod wrote: >> >> set response.meta.description in the controller that generates the page >> >> >> On Wednesday, December 30, 2015 at 6:21:40 AM UTC+1, Joe wrote: >>> >>> Hello, >>> >>> By default meta tags are in menu.py >>> >>> response.meta.author = '' >>> response.meta.description = '' >>> response.meta.keywords = '' >>> response.meta.generator = '' >>> >>> What is the best way to place a unique meta description on each page of >>> the website? >>> >>> Thanks. >>> >>> Cheers, >>> >>> Joe >>> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
