Well sheeit TGR

[frorider]

So today we lapsed back into that 2024 vibe of no ability to post pics? And that weird serif font in the text box? Deja vu.

Not going to bother going to the appropriate forum, gets dusty in there.

[The Reverend Floater]

But we have that Check Out Our Shop button where you can buy mega cringey TGR/Grateful Dead merch!

[old goat]

Can't we all just migrate to tik tok?

[BmillsSkier]

It’s like in Office Space when the Bobs didn’t tell Milton he had been fired years ago and that payroll had been accidentally sending him checks (so he kept showing up); and instead they just fixed the glitch.

I fear all this garbage with the site is TGR “fixing the glitch”.

Sad, really.

[Core Shot]

Edit function gives the spinning wheel of death

[The Nuclear Option]

The end is nigh. What possible business case could they have to justify investing a single dollar?

[singlecross]

Help us Cody Fifty Kenobi… you’re our only hope

[byates1]

I can only post w Tapatalk. We are willing to fund the fix. Who do we need to talk to? An in person in Wilson?

Sent from my Pixel 8 Pro using Tapatalk

[EWG]

I’m here in JH now. Does anybody know which cord to unplug and plug back in? I’ll walk over.

[byates1]

^ head over there and let em know we mean business. If we have to send in dunfree we will.

Sent from my Pixel 8 Pro using Tapatalk

[byates1]

Preserving and upgrading a vBulletin message board involves several key steps to ensure the continued usability and security of your forum. Here is a concise guide:

1. **Backup Everything**:
- Start by making a complete backup of your database and files. This is crucial in case anything goes wrong during the upgrade process.
- Regular backups should be part of your ongoing maintenance.

2. **Assess Current Version**:
- Check the version of vBulletin you're using. Older versions may have specific upgrade paths or limitations.
- Review the changelog or documentation provided by vBulletin for details on version differences.

3. **Upgrade Path**:
- Follow the recommended upgrade path provided by vBulletin. If you're several versions behind, you may need to perform intermediate upgrades.
- Pay attention to any pre-upgrade tasks like disabling plugins or customizations.

4. **Choose the Right Version**:
- Decide whether to upgrade to the latest version of vBulletin 5 or switch to a different forum software (e.g., XenForo, Discourse) if vBulletin's current features or performance do not meet your needs.

5. **Test Environment**:
- Set up a test environment, such as a subdomain or local server, and run the upgrade there first. This helps pinpoint potential issues without affecting your live site.

6. **Review Custom Code and Plugins**:
- Identify any custom modifications or plugins. Post-upgrade, these may need rewriting or fine-tuning for compatibility.
- Check for updated versions of these plugins or replacements that fit your upgraded environment.

7. **Perform the Upgrade**:
- Execute the upgrade process in your test environment first, ensuring that everything works as expected.
- Once satisfied, proceed with the upgrade on your live site during low-traffic times to minimize impact.

8. **Post-Upgrade Testing**:
- Verify all forum features and functions post-upgrade, including user logins, posts, threads, and administrative settings.
- Check for broken links, missing data, or errors.

9. **Security and SEO**:
- Update security settings based on the new version’s features.
- Review and update any SEO settings or URL structures that may have changed during the upgrade.

10. **Inform Users**:
- Communicate with your community about the upgrade process, any new features, or necessary changes to how the forum will now work.

By carefully planning and executing each step, you can preserve and enhance your vBulletin forum for future use.

Sent from my Pixel 8 Pro using Tapatalk

[Toadman]

Where's Rontele when you need him?

[frorider]

I PM’d him but notifications have been broken lately so…

[toast2266]

I think the problem is in step #6, they retained the custom code that makes the site shit the bed every 3 weeks.

Sent from my SM-S901U using Tapatalk

[mcski]

I think the problem is in step #6, they retained the custom code that makes the site shit the bed every 3 weeks.

Sent from my SM-S901U using Tapatalk

Who is they? TGR or a vendor?