On Aug 25, 1:45 am, Richard <richar...@gmail.com> wrote:
> A few questions/comments from my experience implementing this:
>
> tickets2db.py needs an update because of a new interface for
> RestrictedError():
> 40) error.load(filename) -> error.load(request, request.app,
> filename)

will fix it, thanks.

> If I want to reuse the admin ticket view in another controller, is
> this the proper way?
> response.view = '../../admin/views/default/ticket.html'

yes or just copy the ticket.html

> The code line numbers in my tickets don't match the correct code line
> because there is an extra new line inserted between every code line.
> So a 3 line function is being rendered like this:
> 1. def user():
> 2.
> 3.   response.view = 'form.html'
>
>       return dict(form=auth())
>
> Richard
>
> On Aug 25, 3:52 pm, Richard <richar...@gmail.com> wrote:
>
> > just one host.
> > hmm, I guess an RSS feed won't be queried often so efficiency is not
> > important and I can just read from disk like you suggest.
>
> > Richard
>
> > On Aug 24, 7:31 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > I do not know if you need to load them in db unless you have multiple
> > > hosts.
>
> > > On Aug 24, 12:09 am, Richard <richar...@gmail.com> wrote:
>
> > > > hello,
>
> > > > I would like to create an RSS feed of error tickets generated by my
> > > > app. I was planning to create a CRON job with scripts/tickets2db.py to
> > > > load them into the database, and then generate an RSS feed from the
> > > > database.
>
> > > > But before I start I want to check if there is a better way, or
> > > > existing code for this.
>
> > > > Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to