Open jasonkarns opened 11 years ago
That's probably the easiest thing that's still 'correct'. Though, from a product owner's perspective, I would still expect to be able to share the article, even without campaign info loaded. The campaign info is only necessary to show current dollars raised, and to track the share events. Base functionality (sharing to twitter/fb/email) doesn't actually require a campaign_id.
Ought to get some guidance on this from Adam/Kevin. Should be low priority but might be something they'd like to support (maybe a day or two's worth of work?)
A day sounds about right, but I don't think that day will happen next week.
On Sun, May 12, 2013 at 9:33 PM, Jason Karns notifications@github.comwrote:
That's probably the easiest thing that's still 'correct'. Though, from a product owner's perspective, I would still expect to be able to share the article, even without campaign info loaded. The campaign info is only necessary to show current dollars raised, and to track the share events. Base functionality (sharing to twitter/fb/email) doesn't actually require a campaign_id.
Ought to get some guidance on this from Adam/Kevin. Should be low priority but might be something they'd like to support (maybe a day or two's worth of work?)
— Reply to this email directly or view it on GitHubhttps://github.com/testdouble/impaq-me/issues/10#issuecomment-17789487 .
agreed.
On Sun, May 12, 2013 at 9:42 PM, Zach notifications@github.com wrote:
A day sounds about right, but I don't think that day will happen next week.
On Sun, May 12, 2013 at 9:33 PM, Jason Karns notifications@github.comwrote:
That's probably the easiest thing that's still 'correct'. Though, from a product owner's perspective, I would still expect to be able to share the article, even without campaign info loaded. The campaign info is only necessary to show current dollars raised, and to track the share events. Base functionality (sharing to twitter/fb/email) doesn't actually require a campaign_id.
Ought to get some guidance on this from Adam/Kevin. Should be low priority but might be something they'd like to support (maybe a day or two's worth of work?)
— Reply to this email directly or view it on GitHub< https://github.com/testdouble/impaq-me/issues/10#issuecomment-17789487> .
— Reply to this email directly or view it on GitHubhttps://github.com/testdouble/impaq-me/issues/10#issuecomment-17789645 .
I'm thinking we auto-close the iframe in production and log it for view in the dashboard. That way they get feedback on what went wrong when they are setting up.