Skip to content

Website History

This page is a short record of the main work Visionquest Development (Jim) has done on cadence-group.com, based on the email history. It’s here so new team members understand why the site is set up the way it is.

Year What happened
2018–2019 Jim maintains the site on an older ThemeForest theme (Builder) with Visual Composer: monthly updates and HTTPS fixes.
2020 Jim recommends his Pegasus theme. It’s approved, and the site is rebuilt on a new HostGator server with SSL. Forms are rebuilt.
2021 Pegasus is in use. Jim replaces old Visual Composer tabs and accordions with his own Pegasus Tabs plugin. Hosting outages and backup setup.
2023–2024 Outages caused by a full disk and WordPress updates. HostGator moves the site to a new server. SSL ownership moves to Tina. Resumes found in Google are blocked.
2025 Forms are reconnected to Apptivo. SiteOrigin is chosen to replace WPBakery.
2026 The dev site shows up in search and is removed. Malware cleanup. The site moves to SiteGround on Nov 2. A staging site is set up Nov 19.

The theme: ThemeForest “Builder” → Pegasus

Section titled “The theme: ThemeForest “Builder” → Pegasus”
  • Feb 2018: The site ran Builder, a theme bought on ThemeForest, with bundled plugins including Visual Composer (now called WPBakery), Revolution Slider, and a portfolio plugin. Jim updated Visual Composer and WordPress on the dev site and reported that updating the theme itself needed FTP access.
  • Feb 2020: Jim found that Builder had been discontinued on ThemeForest (no more downloads or updates). Visual Composer was stuck on an old version, and Revolution Slider broke after a required PHP upgrade. He also found that past edits had been made directly to the main theme instead of a child theme. He recommended a theme update.
  • Mar 17, 2020: Jim recommended moving to Pegasus, his own theme, with all future changes going in a child theme so updates don’t wipe them out. He showed a working copy of the site on Pegasus.
  • Mar 27, 2020: Cadence approved the Pegasus version, as long as the forms and Google map worked.
  • Apr–May 2020: The Pegasus site was set up on the new server for review. The emails don’t give the exact date it went live, but by 2021 the live site was running Pegasus (Jim pointed the team to the Pegasus settings in Sept 2021).
  • Aug 2021: A tab on the home page showed different text to different people. The cause was Visual Composer’s old “Tabs” and “Accordions” elements, which Visual Composer had retired years earlier. Jim fixed the text and advised staying away from those old elements.
  • Sept 2021: Jim installed his Pegasus Tabs plugin (tabs and accordions through simple shortcodes) on dev and live as the replacement, and fixed the Submit Resume button.
  • Aug 6, 2025: Jim confirmed that SiteOrigin Page Builder is the builder to move to, because it works well with Pegasus. WPBakery is the one to move away from. At the time about 95% of live pages used WPBakery. Jim also gave a temporary fix for blog title alignment in SiteOrigin until the theme is updated.
  • Oct 29, 2026: After the malware cleanup, Jim recommended removing WPBakery (JS Composer) to reduce the site’s attack surface, since attackers often target big plugins like it.
  • Nov 2026: The team converted pages to SiteOrigin. WPBakery hasn’t been removed yet, and new SiteOrigin page work is on hold until staging is tested.
  • Early 2020: The site and a separate dev site were on HostGator cPanel hosting. The emails don’t say where the site was hosted before that.
  • Apr–May 2020: Cadence set up a new HostGator server, and Jim moved the site onto it along with a new dev.cadence-group.com site.
  • Sept–Oct 2021: The live and dev sites had short outages and database-connection errors. HostGator repaired configuration files on the live site, and Jim fixed the dev site. CodeGuard (a paid HostGator backup add-on) was set up in Oct–Dec 2021, alongside Jim’s own manual backups.
  • Sept 2023: The site went down several days in a row because its main settings file (wp-config.php) kept being emptied. Jim found the hosting account’s disk was full (a 3 GB limit), cleared out old leftover files, and changed the FTP password.
  • Feb 2024: The same file was wiped again during an automatic WordPress update. Jim turned off automatic core updates and kept doing monthly updates by hand.
  • Jul–Sep 2024: HostGator migrated the site to a new server. On Aug 20, 2024 Jim pointed cadence-group.com and the dev site at it.
  • Oct 29, 2026: After the malware incident, Jim recommended making the move to SiteGround the top priority.
  • Nov 2, 2026: The site went live on SiteGround. Before the move, Jim scanned a fresh copy of the site, replaced WordPress core files, and shrank the database from about 330 MB to 77 MB by removing old Caldera Forms data and thousands of spam form entries (real Gravity Forms entries were kept). He also hardened the site: new database table prefix, all plugins updated, and PHP blocked from running in the uploads folder.
  • Nov 19, 2026: Jim created the staging2 staging site. The domain’s DNS is still at GoDaddy, so see Using the Staging Site.
  • May 2019: Cadence asked Jim to fix images and content that broke the secure (HTTPS) version of the site.
  • Feb 2020: Jim tracked the last “mixed content” warnings to fonts loaded by the old theme and to an outdated tracking script, and removed them.
  • May 2020: An SSL certificate was installed on the new live and dev sites, and Jim set the site to always use HTTPS. In Jan 2021 he also updated old http:// links in the database.
  • Jul–Aug 2024: Certificate renewal emails were going to a former employee’s address. On Aug 20, 2024 the domain’s contact was changed to Tina so certificate checks go to her.
  • Apr 2025: Jim advised that SSL came free with the HostGator hosting, so the separate GoDaddy SSL purchase could stop.
  • May–Jun 2020: The site’s 10 forms were rebuilt with Caldera Forms so leads could flow to the CRM. Jim recommended Gravity Forms, which the site now uses.
  • Oct 28–29, 2024: Resumes in Google. A job applicant found the resume she had submitted through the site in Google search results. Jim found the files were in an upload folder that search engines could reach (an issue dating back to 2022). He blocked search engines from that folder and moved the files out temporarily so Google would drop them faster.
  • 2024–2025: Website forms were connected to Apptivo. In Jul–Aug 2025, form submissions caused a “critical error” and stopped reaching Apptivo. Jim worked with Apptivo support on their integration code, and by Aug 14, 2025 the main forms were feeding Apptivo again.
  • Nov 2026: Gravity Forms entries were cleaned up during the SiteGround move. Cadence asked Jim to confirm that resumes are still hidden from search engines on the new server and deleted after they reach Apptivo. That’s being confirmed.
  • Sept 2023: Repeated outages were first suspected to be a hack, but traced to the full disk (see Hosting).
  • Aug 2026: Google and Bing were showing the dev site to the public. Jim blocked search engines from it. In Oct 2026 the dev site was removed, and old dev links now redirect to the live site.
  • Oct 2026: Malware (“cloaking”). SmartSites, Cadence’s SEO agency, found that search engines were being shown a gambling page instead of Cadence’s real pages, while normal visitors saw the real site. That’s why the site vanished from Bing and Google results looked wrong.
    • Oct 16: Jim removed a hidden file manager and a modified core file, replaced WordPress core, and reinstalled clean plugins.
    • Oct 27–29: The cloaking came back through other hidden backdoors. Jim did a full forensic review. The earliest entry point was a fake plugin installed in July 2026, followed by hidden files added in Aug–Sept. He removed all of them and confirmed search engines now see the real site.
    • Nov 3: SmartSites confirmed the cleanup was holding on SiteGround.
    • Follow-up: Reset passwords, remove unknown owners from Google Search Console and Bing Webmaster Tools, ask Google and Bing to recrawl, remove unused plugins, and keep one security plugin running.

The Success Stories page lists Cadence’s case studies. It uses a custom template Jim maintains, and each case study is a Portfolio entry. See Portfolio (Case Studies).