VendorHearth Pro integrates with the WordPress update system so eligible software updates can appear directly within your WordPress dashboard.
Keeping VendorHearth updated gives you access to available bug fixes, improvements, and new features released during your active license period.
How VendorHearth Updates Work #
When an eligible VendorHearth Pro update is available, WordPress can display it alongside your other plugin updates.
You can review available updates from:
WordPress Dashboard → Plugins
or:
WordPress Dashboard → Updates
VendorHearth periodically validates your license to determine update eligibility.
An Active License May Be Required #
Your VendorHearth Pro license provides access to updates during the applicable license period.
VendorHearth licenses do not automatically renew.
If your license has expired, your installed version continues to function, but you may need to renew your license before receiving newer VendorHearth Pro releases.
Before Updating #
VendorHearth stores important operational information for your organization.
Before installing a major update, make sure you have a current backup of your WordPress website.
Your backup should include:
- WordPress database
- WordPress files
- Uploaded vendor files
- VendorHearth data
This provides a recovery option if an unexpected problem occurs.
Do Not Delete VendorHearth to Update It #
When an update is available through WordPress, use the normal update process.
You generally do not need to delete VendorHearth before installing an update.
Deleting plugins unnecessarily can complicate troubleshooting and is not the recommended routine update method.
Installing an Update #
When an update is available:
- Back up your website.
- Review the available VendorHearth update.
- Select the normal WordPress update option.
- Allow WordPress to complete the update.
- Return to VendorHearth after the update completes.
- Review System Readiness.
- Test important workflows.
Check System Readiness After Updating #
After a significant VendorHearth update, open:
VendorHearth → System Readiness
Review the results for problems involving:
- VendorHearth version
- Database or schema
- Portal pages
- User roles
- Uploads
- Scheduled automation
- Payment configuration
- Setup state
Address significant warnings before assuming the update is complete.
Test Important Workflows #
You do not need to retest every feature after every small update, but important workflows should be checked after major releases.
Consider testing:
- Vendor Login
- Vendor Dashboard
- Applications
- Payments
- Square connection
- Vendor Relations Portal
- Organizer Portal
- Event Packet
- Vendor Check-In
If your next event is approaching, testing these features becomes especially important.
Check Square After Major Site Changes #
A normal VendorHearth update should not require you to recreate your Square configuration.
However, if an update occurs alongside a domain migration, major WordPress change, or other substantial site work, verify your payment configuration.
Confirm that VendorHearth is still receiving the expected payment updates.
Do Not Update During Vendor Check-In #
Avoid performing major plugin or WordPress updates while actively operating an event.
If possible, complete updates and testing before event day.
Updating during vendor arrival introduces unnecessary risk to:
- Check-in
- Vendor portal access
- Booth information
- Event packets
- Other operational tools
Keep WordPress Updated Too #
VendorHearth depends on WordPress and your website environment.
VendorHearth Pro requires:
- WordPress 6.2 or newer
- PHP 8.1 or newer
Maintaining a supported WordPress and PHP environment helps reduce compatibility and security problems.
If an Update Causes a Problem #
If something behaves unexpectedly after an update:
- Do not immediately delete VendorHearth.
- Review System Readiness.
- Clear relevant site or server caches.
- Confirm your WordPress and PHP versions meet requirements.
- Identify which VendorHearth feature is affected.
- Record any visible error message.
- Check whether other plugins or the theme were updated at the same time.
If necessary, restore your known-good website backup while the problem is investigated.
Avoid Editing VendorHearth Plugin Files Directly #
Do not modify VendorHearth’s core plugin files to customize the system unless specifically instructed for development purposes.
A future VendorHearth update can replace modified plugin files.
Keeping the installed plugin files intact also makes troubleshooting much easier.
Update Before You Need the New Version #
Whenever possible, do not wait until the morning of an event to install a major VendorHearth update.
Install updates when you have enough time to verify the system afterward.
For organizations actively accepting applications and payments, choose an update window that allows you to test those workflows before vendors rely on them again.
Next Step #
Continue to Moving or Reconfiguring a VendorHearth Installation to learn what to check when changing domains, migrating WordPress, replacing portal pages, or making other major configuration changes.
