Hello @jovmbbuzz
That method name was updated to engage_account_type and fixed everywhere in version 3.2.5. This error could have been caused by a caching issue from within the site somewhere.
Thank you for the quick response.
The site is working, however the dashboard is still not working even after clearing cache: https://prnt.sc/wcvWW6XAzSME
-
This reply was modified 8 months, 1 week ago by
jovmbbuzz.
Just to be sure I’ve tested out version 3.2.5 on a demo site. It might be that caching is occurring somewhere on the server.
Here are steps to address this:
- Clear Caches:
- WordPress Caching Plugins: If using a caching plugin (e.g., WP Super Cache, W3 Total Cache, LiteSpeed Cache), clear all its caches.
- Server-Side Caching: If your hosting provider uses server-side caching (e.g., Varnish, Nginx FastCGI cache), clear it through your hosting control panel or by contacting support.
- CDN Caching: If using a Content Delivery Network (CDN) like Cloudflare, clear its cache.
- Browser Cache: Clear your web browser’s cache and cookies, or test the site in an incognito/private browsing window.
- Verify Plugin Update Status:
- Navigate to Dashboard > Updates in your WordPress admin area and click the “Check Again” button to ensure WordPress has recognized the latest version of the plugin.
- Check the plugin’s version number displayed in the Plugins list to confirm it reflects the updated version.
- Troubleshoot Plugin Conflicts:
- Temporarily deactivate other plugins to see if a conflict is causing the issue. Reactivate them one by one to identify the culprit.
- Switch to a default WordPress theme (e.g., Twenty Twenty-Four) to rule out theme-related conflicts. You don’t have to do this step if it’s fairly difficult.
- Manual Update (if applicable):
- If the update was performed automatically and issues persist, consider performing a manual update:
- Deactivate and delete the plugin from your WordPress installation.
- Download the latest version of the plugin from the official source or developer.
- Upload and activate the new version.
- Database Issues:
- Some plugins store data or settings in the WordPress database. If the update involved database schema changes, ensure these were applied correctly. You might need to check for update routines within the plugin’s code or consult the developer’s documentation.
- File System Permissions:
- Ensure that the file system permissions for the plugin’s directory and files are correct, allowing WordPress to write and read the updated files.
By systematically addressing these potential causes, you can typically resolve instances where outdated plugin code is still being executed after an update.
https://kmowatt.idxbrokerhome.com/wp-content/uploads/2025/09/Screenshot-2025-09-24-at-8.52.51-AM.png
https://kmowatt.idxbrokerhome.com/wp-content/uploads/2025/09/Screenshot-2025-09-24-at-8.53.07-AM.png
