So while experimenting with axtime earlier this year, I created a 2013 season. Now I'd like to remove it, but don't see a way to do so. And of course we've had 2 events now in 2015 so I can't just revert back to a backup prior to adding the 2013 season :-)

@JasonPowell There currently isn't a way to delete a season through the UI.

10-4 ... will ping you about it once 2015 season is over.

@Chris - Dumb question. Can he export each of the events he's concerned about preserving into CSV files, export the membership, whack the database back to empty (re-install?), and then re-import everything clean from the CSV files?

When I did our class import from an AXware file, it came in corrupted. (No surprise whenever AXware is involved!) The result is that I cannot save any changed season settings. I have since edited the AXware file to fix the errors, and plan to whack the database and start from scratch before our first event on Sunday. Just want to verify that this is a sound idea, and won't blow anything else up.....

@vreihen I personally wouldn't do that... I would instead use RoboMongo to get into the actual data. Obviously, at your own risk :-)

What was wrong the the axware class file?

@Chris - The file had SS listed with a non-zero PAX and the PAX flag set. After import, AXti.me is displaying it as a PAX class. When I tried to remove the bogus PAX class (or make any other changes to the season settings), the save button didn't work and there was no errors on the console.

Not a big deal to me, since the first thing that I did when I did the AXti.me install on the production event computer was take a local backup of the blank database so that I could fall back before going live. If I was really smart, I would have made a backup of the database files into a different folder and created a new step 1 batch to bring it up as a test/play instance for training purposes and such.....

@Chris - If you're bored, I just did a cloud backup named "brokenSS" with the season that I can't edit. I already fixed the import file and plan to start over from scratch before our first event on Sunday, so it is really no big deal to me why it won't save. Lesson learned about keeping a "data firewall" between AXware files and the rest of the world..... :-)

@vreihen By "console" errors, are you referring to the web browser console or command/terminal window?

I'm going to assume command/terminal. I'm guessing there is a javascript error in the browser that is preventing the season edit page to be submitted.

Right click anywhere on the season edit page, select "Inspect Element". Then find the "Console" tab/button in the new screen that pops up. Reload the page and look for any red colored lines indicating an error. copy and paste or take a screenshot.

@Chris - Yes, command/terminal window.

Here's the JS web browser console error from trying to delete the bad SS as an index class and pressing save:

jquery-1.9.0.min.js:3 Uncaught Error: Syntax error, unrecognized expression: #?--index

As I said, I wouldn't waste any time on it. The file was legitimately messed up before import, and I have since successfully imported the repaired file into a freshly installed test database setup.....

On second thought, could this be a problem with the comma in the club name?

<form action="/club/Poughkeepsie Sports Car Club, Inc/newseason" method="POST">

I may have left it off in the test database where it imported cleanly.....

@vreihen said:

jquery-1.9.0.min.js:3 Uncaught Error: Syntax error, unrecognized expression: #?--index

This error indicates that there is a class name of "?" that was somehow imported.

I'll modify your cloud backup tonight.

@Chris said:

This error indicates that there is a class name of "?" that was somehow imported.

Oh, yes! I forgot that I had to cut that little doozie (and other AXware oddities like the mailout class) from the file while I was fixing it. Why can't we have classes with punctuation in them, or even worse if someone shows up and wants to run pi as their car number? :-) (I've head that this actually happened an an FSAE event, and use as proof that engineers can sometimes have a sense of humor. FSAE rules now read that a car number must be a non-zero positive integer.)

I'll modify your cloud backup tonight.

Seriously, it's not worth the time. I'm going to blast it tomorrow and start from scratch. When doing my original testing, I first imported an old AXware event and then a week later did the MSR membership import. It created so many duplicate members that it is easier to start from scratch and keep the AXware data far, far, far away from it this time. There's 10+ years of cruft in our AXware computer, and I don't want to bring one byte of that over into AXti.me.....

As a footnote, I now have a clean database that has the correct season/classes and a fresh MSR member import. I felt so strongly about no data being brought over from that other software/computer to prevent the new system from catching "AXware cooties" that I even just ran out to buy a new USB flash drive.....