Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #803 (closed enhancement: fixed)

Opened 11 years ago

Last modified 10 years ago

ExtendingVisitFramework

Reported by: jvanasco@… Owned by: anonymous
Priority: normal Milestone: 1.0b1
Component: Identity Version: 0.9a5
Severity: normal Keywords:
Cc: jeff

Description

I just went though the visit framework after reading this:

http://trac.turbogears.org/turbogears/wiki/ExtendingVisitFramework

Considering that the identity schema was recently moved out of the TG internals, what would people feel about moving visit?

I have one project where visit as-is is perfect I have another where I'd like to add 'ip , hitcount, start, end'

the current plugin framework makes that possible by using the current visit table and then a second + a plugin.

i'd kind of like to consolidate it into one by doing this:

  • move TG_Visit to model.py, where fields can be added
  • create hook functions in the visit manager that will call a user defined function at the appropriate time

ie:

   class SqlAlchemyVisitManager():
      def new_visit()
          visit = model.TG_Visit()
          visit.commit()

model.py

   class TG_Visit():
      # current TGVisit columns required
      # chance to overwrite udpate_visit

Change History

comment:1 Changed 11 years ago by simon

  • Cc jeff added
  • Component changed from CherryPy to Identity

comment:2 Changed 11 years ago by kevin

  • Milestone set to 1.0b1

comment:3 Changed 11 years ago by kevin

  • Status changed from new to closed
  • Resolution set to fixed

done in [1603], at least as far as moving to model.py. If it's not possible to do the other desired things, we can open a new ticket.

Note: See TracTickets for help on using tickets.