Issue 36 in proximitymarketing: i'm trying to fix the code of campaign timing

3 views
Skip to first unread message

proximity...@googlecode.com

unread,
Aug 2, 2011, 5:34:14 PM8/2/11
to openpr...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 36 by only_way...@yahoo.com: i'm trying to fix the code of
campaign timing
http://code.google.com/p/proximitymarketing/issues/detail?id=36

i'm trying to fix the bug in the campaign timing
as you all know that campaigns with start and stop date are not working
correctly according to the timezone and Manuel offered solution by
JavaScript so i tried to fix it with knowledge which i have and i reached
to the following
server log times is correct according to the time zone
23:08:27 Dongles added ( correct time )
so i moved to the function which responsible to show the matching campaigns
vim /opt/openproximity2/django-web/openproximity/models.py
def getMatchingCampaigns
the following line gets the time correctly

time_ = time_ or datetime(*time.gmtime()[:-2])
but the html page which show the campaign doesn't show it in the start date
/opt/openproximity2/django-web/openproximity/templates/op/imports/campaigns.html

so where i should modify to make the campaign work in start and end date
all what i need is just hints and i will proceed to fix this bug
which part is responsible for this bug ??

proximity...@googlecode.com

unread,
Aug 31, 2011, 11:21:03 AM8/31/11
to openpr...@googlegroups.com
Updates:
Status: Duplicate
Mergedinto: 32

Comment #1 on issue 36 by naranjo....@gmail.com: i'm trying to fix the code

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages