Theme updates deliver bug fixes, new features, and WordPress compatibility patches. Updating safely means your customizations survive the process intact. This guide covers everything to check before, during, and after an update.
Before you update
- Take a full site backup. Use Duplicator, UpdraftPlus, or your host’s backup tool. Don’t skip this — a 2-minute backup can save hours of recovery time.
- Check the changelog. Review the update notes in your account or ThemeForest comments before upgrading. Look for anything labelled “breaking change.”
- Test on staging first. If your host provides staging (SiteGround, WP Engine, Cloudways all do), run the update there before touching production.
- Are you using a child theme? If yes, your PHP and CSS changes are safe. If not, note any files you’ve modified so you can re-apply changes after updating.
Not using a child theme? Any PHP or CSS edits you made directly to the parent theme files will be wiped on update. See our child theme guide before proceeding.
Method 1 — Update from WordPress admin
- Download the latest theme ZIP from your Themezinho account page.
- Go to Appearance → Themes and click Add New → Upload Theme.
- Upload the new ZIP and when prompted click “Replace current with uploaded”.
- WordPress will overwrite the parent theme files. Your child theme is untouched.
Method 2 — Manual FTP update
- Extract the new theme ZIP locally.
- Connect to your server via FTP.
- Delete the old
/wp-content/themes/themezinho/folder (your child theme folder is separate — leave it alone). - Upload the new theme folder in its place.
After updating
- Clear all caches — caching plugins, Cloudflare, your browser, and the Elementor CSS cache.
- Regenerate Elementor CSS: go to Elementor → Tools → Regenerate Files & Data.
- Check your homepage and key pages — scroll through them quickly to spot any layout shifts.
- Flush permalinks: go to Settings → Permalinks and click Save Changes.
Troubleshooting post-update issues
If something looks broken after updating: first clear all caches. 90% of post-update visual issues are stale CSS being served by a caching layer. If the issue persists after clearing caches, check our plugin conflict guide or open a support ticket.
