Open searls opened 10 years ago
yeah that should be fine for now, let's just make sure the documentation captures how one would do that in case it does come up before we get to actually implementing the UI
Where is the best place to document that?
On Wed, Aug 6, 2014 at 11:17 AM, Adam Schweigert notifications@github.com wrote:
yeah that should be fine for now, let's just make sure the documentation captures how one would do that in case it does come up before we get to actually implementing the UI
Reply to this email directly or view it on GitHub: https://github.com/testdouble/impaq-me/issues/121#issuecomment-51349346
probably just collect any weird odds on ends on a wiki page
Posted here: https://github.com/testdouble/impaq-me/wiki/Controlling-exact-campaign-start-&-end-times
On Wed, Aug 6, 2014 at 11:43 AM, Adam Schweigert notifications@github.com wrote:
probably just collect any weird odds on ends on a wiki page
Reply to this email directly or view it on GitHub https://github.com/testdouble/impaq-me/issues/121#issuecomment-51353260.
Campaign start & end as implemented in #104 are actually tracking times, but for simplicity sake, the web form is only collecting the date. That means if you set 2014-08-03 as the start and 2014-08-05 as the end of a campaign, it will save as midnight eastern time the morning of 8/3 through 11:59pm the night of 8/5.
The most recent campaign wanted to launch at a very specific time of day, so in the future we could either:
heroku run rails c
and adjust the time with something likeCampaign.find(SOME_ID).update(:starts_at => Campaign.find(SOME_ID).starts_at + 10.hours)
I presume this is going to be a rare request and I recommend you stick to the console / non-UI approach for now