bethlakshmi / GBE

Code repository for the Great Boston Burlesque Expo
3 stars 0 forks source link

Download tech info as csv #158

Closed jonkiparsky closed 10 years ago

jonkiparsky commented 10 years ago

From Scratch, via email: "It would be wonderful if there was a way to download the tech info for each show as a spreadsheet or CSV file. And it would be wonderful if this happened really soon ... If you go to one of the show pages, so let's say The Rhinestone Revue at http://burlesque-expo.com/Schedule.php?action=25&EventId=9 and you are logged in and have the right privileges, there's an Event Admin menu in the upper right hand corner. One of the items on that menu is Show Tech Info.

If you click on it, you see all of the info that was submitted for that show by the performers (http://burlesque-expo.com/DisplayActTechInfo.php?ShowId=9)

It'd be fabulous if up near the top of that new page (http://burlesque-expo.com/DisplayActTechInfo.php?ShowId=9) there was a button that said "Download as a CSV" and did just that"

jonkiparsky commented 10 years ago

@bethlakshmi Added code for this. Could you kick this into dev for testing? (and if testing is happy, into prod?) Thanks @burlexpo Ready for testing on kiparsky.net, with outdated info. Ready for testing on test site when Betty says so.

bethlakshmi commented 10 years ago

Can do tonight, not so easy from the office.

Although keep an eye out - the github is configured so that it should automatically update in testing. I've seen 2 issues, though:

1 - it can take anywhere from 1 minute to 1 hour. 2 - it gets confused if you check in multiple checkins inside of 10-60 minutes and drops some of the updates.

So... keep an eye out, you may just find that in an hour, it's up in test-expo.

On Tue, Feb 4, 2014 at 3:29 PM, Jon Kiparsky notifications@github.comwrote:

@bethlakshmi https://github.com/bethlakshmi Added code for this. Could you kick this into dev for testing? (and if testing is happy, into prod?) Thanks @burlexpo https://github.com/burlexpo Ready for testing on kiparsky.net, with outdated info. Ready for testing on test site when Betty says so.

Reply to this email directly or view it on GitHubhttps://github.com/bethlakshmi/GBE/issues/158#issuecomment-34103359 .

jonkiparsky commented 10 years ago

In that case, if it's going to auto update, it'll have done by now. Mr scratch, be advised.

sent from my handy. typos are just part of the fun. On Feb 4, 2014 4:37 PM, "bethlakshmi" notifications@github.com wrote:

Can do tonight, not so easy from the office.

Although keep an eye out - the github is configured so that it should automatically update in testing. I've seen 2 issues, though:

1 - it can take anywhere from 1 minute to 1 hour. 2 - it gets confused if you check in multiple checkins inside of 10-60 minutes and drops some of the updates.

So... keep an eye out, you may just find that in an hour, it's up in test-expo.

On Tue, Feb 4, 2014 at 3:29 PM, Jon Kiparsky <notifications@github.com

wrote:

@bethlakshmi https://github.com/bethlakshmi Added code for this. Could you kick this into dev for testing? (and if testing is happy, into prod?) Thanks @burlexpo https://github.com/burlexpo Ready for testing on kiparsky.net, with outdated info. Ready for testing on test site when Betty says so.

Reply to this email directly or view it on GitHub< https://github.com/bethlakshmi/GBE/issues/158#issuecomment-34103359> .

Reply to this email directly or view it on GitHubhttps://github.com/bethlakshmi/GBE/issues/158#issuecomment-34110057 .

bethlakshmi commented 10 years ago

In test, but not in dev.

Scratch may be busy right now ... he sounded busy 5 min ago...

On Tue, Feb 4, 2014 at 4:39 PM, Jon Kiparsky notifications@github.comwrote:

In that case, if it's going to auto update, it'll have done by now. Mr scratch, be advised.

sent from my handy. typos are just part of the fun.

On Feb 4, 2014 4:37 PM, "bethlakshmi" notifications@github.com wrote:

Can do tonight, not so easy from the office.

Although keep an eye out - the github is configured so that it should automatically update in testing. I've seen 2 issues, though:

1 - it can take anywhere from 1 minute to 1 hour. 2 - it gets confused if you check in multiple checkins inside of 10-60 minutes and drops some of the updates.

So... keep an eye out, you may just find that in an hour, it's up in test-expo.

On Tue, Feb 4, 2014 at 3:29 PM, Jon Kiparsky <notifications@github.com

wrote:

@bethlakshmi https://github.com/bethlakshmi Added code for this. Could

you kick this into dev for testing? (and if testing is happy, into prod?) Thanks @burlexpo https://github.com/burlexpo Ready for testing on

kiparsky.net,

with outdated info. Ready for testing on test site when Betty says so.

Reply to this email directly or view it on GitHub< https://github.com/bethlakshmi/GBE/issues/158#issuecomment-34103359> .

Reply to this email directly or view it on GitHub< https://github.com/bethlakshmi/GBE/issues/158#issuecomment-34110057> .

Reply to this email directly or view it on GitHubhttps://github.com/bethlakshmi/GBE/issues/158#issuecomment-34110348 .

bethlakshmi commented 10 years ago

posted!