Forum functioning normally - please let us know if not

[ApexSpeed]

Hi everyone, glad to see the posts and normal functioning today, apologies for the issues the last few days.

If anyone lost posts, I have the ones from the end of week if you need help reposting.

Please DM me or email/facebook us if you see issues, the work last night should have cleared anything causing issues from wednesday.

For context, we saw/caused the issues doing work to add resilience and visibility to the site ops continuous monitoring (ironic huh), and then believed the issues were fixed until I heard yesterday we still had posting/use challenges.

Keith/I will be investing in and doing much more work to ApexSpeed this year to bring the site design and user experience to current standards, towards sustainable operations and increasing community participation. There are now and will continually be many opportunities for your ideas, contribution, and continued support of the site and we look excitedly forward to those times.

We will communicate those changes as impacting to you and welcome any/all feedback and ideas here or in dms/emails/phonecalls, posts, etc...

Thank you, Will

[John Nesbitt]

Thank you for bringing the forum back to functioning. It is an extremely valuable resource for the open wheel/SR community, and greatly appreciated by all.

One micro-micro thing that you might correct: In the small print at the bottom of the page, the vbulletin version number is shown as 4.2.2, which is about 10 years out of date. It looks like "Version 4.2.2" is hardcoded into the HTML, rather than parameterized.

[DaveW]

...For context, we saw/caused the issues doing work to add resilience and visibility to the site ops continuous monitoring (ironic huh), and then believed the issues were fixed until I heard yesterday we still had posting/use challenges...

Reminds me of working on computer programs in the late '60's & early '70's at Case I T. Almost every time they did an OS upgrade, our 2000+ computer-card programs would no longer work, sometimes requiring weeks of screwing around to correct it.

LOL

[Teuobk]

One micro-micro thing that you might correct: In the small print at the bottom of the page, the vbulletin version number is shown as 4.2.2, which is about 10 years out of date. It looks like "Version 4.2.2" is hardcoded into the HTML, rather than parameterized.

The specific errors shown while the site was malfunctioning strongly suggest that the version of vBulletin really is 4.2.2, along with a correspondingly old version of PHP. Not without reason, though: for a period of time, there were numerous PHP releases full of breaking changes, thus requiring many non-trivial code changes and extensive testing when updating old software. I have personally been caught out by that in the past.

Jeff

[EYERACE]

Thank you - cuz it must have been a crazy past few days getting it all proper again

so......

because I don't facebook or X or paypal or nextdoor or most any other thing that creates an internet presence.....

please post mailing address where I may send another check in support of ApexSpeed as a contributing member

...........cuz I'm from the 20th Century and that's how we did things back then

[John Nesbitt]

The specific errors shown while the site was malfunctioning strongly suggest that the version of vBulletin really is 4.2.2, along with a correspondingly old version of PHP. Not without reason, though: for a period of time, there were numerous PHP releases full of breaking changes, thus requiring many non-trivial code changes and extensive testing when updating old software. I have personally been caught out by that in the past.

Jeff

True that. I could not discern what version is running; only that 4.2.2 is hardcoded in the HTML.

In my (long ago) system manager days, I tried to be one release behind the latest release, simply to avoid the kind of breakages you describe.

[Lotus7]

On the superficial level that I use and enjoy Apexspeed, it seems “back to normal” now.
many thanks for an indispensable resource!

[ApexSpeed]

Thank you all for the support and encouragement, each time something like this comes up (despite the bad part) it is great to have the support and feedback about the site.

We're also invested in the long run with the site and feel how great the community and knowledge/sharing/convs are here for the sport(s).

For the techies chipping in here, it is all the things in the thread, 4.2.2 old, fragile and sensitive, and commonly recoverable by immutable force if in no other way. It's cool to see the tech conv/stories and again we appreciate the understanding and suggestions.

My company gdna manages the site, and you can always reach us at apexspeed@gdna.io or me at will@gdna.io for any reason at any time.

We look forward to sharing/starting info and changes in the coming months and hearing your feedback, thanks for being part of ApexSpeed!

[E1pix]

Everything’s working fine on both my iPhone and Macbook Pros.

Congrats!

[Steve Demeter]

I think many of us did not realize (at least I did not) just how much Apexspeed is part of our everyday lives til it was not.

Thanks for keeping it going!!!!

[kr]

Apexspeed
714 New Franklin Rd
LaGrange GA 30240

Thanks for your support!

Keith

Thank you - cuz it must have been a crazy past few days getting it all proper again

so......

because I don't facebook or X or paypal or nextdoor or most any other thing that creates an internet presence.....

please post mailing address where I may send another check in support of ApexSpeed as a contributing member

...........cuz I'm from the 20th Century and that's how we did things back then

[rockbeau25]

Still running into issues trying to access the FC Event News, Info, & Results section.

[kr]

Rock,

Please send William or gdna more details of your problem.

All is working fine for me on PC and phone.

Thanks,
Keith