Forum Replies Created

Viewing 15 replies - 1 through 15 (of 36 total)
  • Plugin Support Riyaz

    (@mriyazuddin1)

    Hey @ozoemena!

    Thanks for sharing the screenshots. I’m still unable to replicate this issue at my end. I have involved our developers to look into this and if needed we might ask screenshots of all the AnsPress settings and not just Permalinks. Will get back to you as soon as I have an update for you. Appreciate your patience in the meantime.

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hi @ozoemena,

    Thanks for your patience and for working through the troubleshooting steps so far. I appreciate the detailed information and the console error.

    From the error you shared:

    Uncaught TypeError: Cannot read properties of null (reading ‘action’) at rtm-upload-terms.min.js?ver=4.7.4:6:4067

    …it appears that a script in rtMedia is attempting to access an element or property that doesn’t exist at the time of execution. This is likely interfering with AnsPress’s submit flow, causing the spinner to never finish.

    I see the last version of rtMedia was released on 30th Oct 2025 and you’ve reported this issue the same day. Assuming rtMedia was updated the same day, its possible the update brought in a change that is causing this issue. However, I see these issues may happen as AnsPress plugin was last updated a year ago and hasn’t received any update since then. Older plugins are likely to have issues with other plugins receiving regular updates.

    I’ve tried replicating this issue on a test site but I have not been able to and as a result I guess it might be some settings in the plugin causing this.

    There are a couple of options here:

    1. Share screenshots of AnsPress settings (make sure to capture a screenshot for all the pages available in the plugin settings) and share with me so I can try and replicate the issue on my test site. If I’m able to replicate it, I can try changing the AnsPress settings around to see what combination works. I can also try AnsPress with the previous version of rtMedia to determine if the new version is causing the conflict.
    2. Reach out to AnsPress support directly to find out what exactly is causing this issue and see if they have any plans to release an update to this plugin. If they’re able to point you to any settings or code in the rtMedia plugin, we’ll be happy to look into.
    Plugin Support Riyaz

    (@mriyazuddin1)

    Hey @carolparmar! The plugin update has been released two days ago along with the fix. Please give it a try and do let us know if you run into any issues or have questions.

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hello @carolparmar ! I really appreciate your patience. I reported this issue to our developers as it was a bug. The good news is, it has been fixed now and should be available in the next release. Please look out for the next update of this plugin.

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hi @carolparmar ! Thanks for sharing the details. I was able to replicate this issue on a test site. I’m investigating this further. Will get back to you as soon as I have an update for you. Appreciate your patience in the mean time.

    Regards,
    Riyaz

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hello @carolparmar !

    I’m sorry to hear about the issues you’re facing. Let me help with that. Could you first share the steps you’ve taken so far? l’d like to know how exactly did you export the content from Blogger and imported into WordPress.

    Also, if you can provide any additional information including error message and / or screenshot, that will be a huge help.

    Regards,

    Riyaz

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hi @peps23 !

    As my colleague mentioned in Purge Entire Cache not working via ngx_cache_purge module? thread, the feedback has been shared with our developers and they’re working on implementing this in a future release. However, I’m afraid we do not have an estimate of when exactly this would happen. I’d encourage you to keep an eye on the future releases.

    I really appreciate your patience as well as your efforts to share this feedback to us.

    Thanks

    Riyaz

    Riyaz

    (@mriyazuddin1)

    Hi @rahul-sarkar !

    Thanks for reaching out and sorry for the delay in getting to this.

    Please note the sites need to be listed on Google Programmable Search Engine settings in order for this to work. You can learn more about Google Programmale Search Engine here.

    Please feel free to let us know if you have more questions or need help.

    Best,

    Riyaz

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hi @ozoemena !

    This is one of the fastest responses a plugin/theme author has provided. Thank you for the prompt response.

    So glad to hear that :-).

    Here are some of the info you requested:

    Thanks for sharing the details. I’m not seeing any obvious issues with the settings. Also, its good to hear that WordPress, all plugins and the theme are updated to their latest versions.

    However, I’d still need to see the browser console screenshot. The screenshot you shared doesn’t show the console. I have recorded my screen showing how to do that. Please take a look at this screencast: https://d.pr/i/7oxNWD for reference. Make sure to reproduce the issue first, go to the browser console and then obtain a screenshot.

    Best Regards,

    Riyaz

    Plugin Support Riyaz

    (@mriyazuddin1)

    Hi @ozoemena!

    Thanks for reaching out and for the detailed troubleshooting, we really appreciate the time you’ve taken to isolate the issue and confirm the conflict.

    To help us identify the exact root cause, could you please provide a bit more information?

    1. When did the issue first start appearing?
    2. Were any changes made to the site (plugin/theme updates, new installations, or custom code) before it started? If so, please share what was changed.
    3. Are all plugins and themes up to date? Please make sure everything is running the latest version, then share the version numbers for:
      • WordPress
      • BuddyPress
      • bbPress
      • AnsPress
      • rtMedia
      • Your active theme
    4. When the submit spinner keeps loading, please check for any console errors in your browser:
    5. Also, please share screenshots of rtMedia settings from rtMedia → Settings.

    Once we have these details, we’d be able to identify the root cause and find a solution.

    Thanks again for your kind words and for using rtMedia, we’ll do our best to get this resolved quickly!

    Best regards,

    Riyaz

    Riyaz

    (@mriyazuddin1)

    Thank you for the update and for sharing the System Status Report earlier. A few things stand out that could be contributing to the slowness when updating products:

    • Database size is very large (3.5GB total, with posts and postmeta alone over 1.4GB).
    • Action Scheduler tables are oversized (40MB+ actions, 30MB+ logs).
    • Outdated WooCommerce template overrides from the Breakdance theme.

    Recommended Steps

    🔹 1. Back up your site first
    Before making any changes, please take a full backup of your site and database.

    🔹 2. Clean up completed scheduled actions
    Go to WooCommerce → Status → Scheduled Actions → Completed and delete old completed actions.

    • If there are too many to delete through the admin panel, you can use WP-CLI or run an SQL query.
    • If you’re not comfortable with that, I recommend asking your hosting support or a hiring developer for assistance.

    🔹 3. Optimize the database
    If cleaning up scheduled actions doesn’t reduce the database size enough, use a plugin like WP-Optimize.

    🔹 4. Update theme templates
    Update the outdated Breakdance theme templates to ensure full WooCommerce compatibility. You can follow this support guide.

    If the issue still persists after trying the above, please reply back with:

    • The steps you’ve taken
    • An updated System Status Report

    That will help narrow down the next troubleshooting steps.

    Riyaz

    (@mriyazuddin1)

    I’d recommend first updating all plugins and themes to their latest versions before trying to deactivate MailPoet. Based on the error message, it looks like MailPoet and WooCommerce are each loading different versions of the CssDocument::__construct() function, which is causing the conflict. The stack trace also indicates that the issue is being triggered through the WooCommerce Reminder Pro plugin. If any of the plugins involved have updates available, applying those may resolve the problem right away.

    If updating doesn’t resolve it, the next step would be to temporarily disable WooCommerce Reminder Pro (in addition to MailPoet if needed) and check whether the error disappears. If it does, that confirms the plugin as the source of the issue. In that case, I’d recommend reaching out directly to the plugin’s support team here: https://weplugins.com/. Just click on the Support link, log in (or create an account), and you’ll be able to submit a ticket.

    Riyaz

    (@mriyazuddin1)

    Hi Scott,

    Thank you for getting back to us and providing the details of your findings after completing the troubleshooting steps. I appreciate your diligence in isolating the issue.

    Based on your description, it seems the conflict occurs when both the WooCommerce plugin and the LearnDash WooCommerce Integration plugin are activated simultaneously. This kind of issue typically happens when there is a compatibility issue between the plugins.

    Here’s what you can do next:

    1. Check for Updates: Ensure that all your plugins, especially LearnDash WooCommerce Integration, LearnDash LMS, and WooCommerce, are updated to their latest versions. The latest version of WooCommerce is 9.5.1, but please confirm that LearnDash plugins are also on their most recent releases.
    2. Contact LearnDash Support: Since the conflict involves the LearnDash WooCommerce Integration plugin, their support team may have more insights or a patch for this compatibility issue. You can reach out to them directly or check their documentation/forums for similar reports.
    Riyaz

    (@mriyazuddin1)

    For the last step though, please be sure to take a backup of your website before uninstalling and reinstalling WooCommerce.

    Riyaz

    (@mriyazuddin1)

    Hi @athleticcity,

    Thanks for your patience in troubleshooting this issue so far. It seems that WooCommerce is still attempting to load fonts that aren’t actually present in the woocommerce/assets/fonts/ directory, resulting in the 404 errors you’re seeing.

    This issue likely stems from cached or residual CSS code within WooCommerce that is trying to call these fonts even though they aren’t present. Here are a few steps you can try to resolve this:

    1. Clear Caches: If you have any caching plugin or server-side caching enabled, try clearing it to ensure that no outdated CSS or cached assets are being loaded. This may help remove any cached references to star.eot and WooCommerce.eot.
    2. Check WooCommerce and Theme Versions: Ensure that your WooCommerce and Storefront Theme are up to date, as font-related issues can sometimes be resolved in newer releases. You can check for any available updates directly in your WordPress dashboard under Dashboard > Updates.
    3. Clear transients: To do this, go to WooCommerce > Status > Tools and you’ll find Clear transients button in front of WooCommerce transients as well as Expired transients. Click on both.
    4. Custom CSS Removal (If Applicable): If you have any custom CSS that references these fonts, try temporarily disabling it to confirm it’s not affecting the font loading.
    5. Reinstall WooCommerce: As a final step, if the above steps don’t work, try reinstalling WooCommerce. Before doing so, make sure to back up your site to prevent any data loss. Reinstalling the plugin can refresh any missing files or references, potentially clearing up this issue.

    Please give these steps a try and let us know how they work out. We’ll be happy to continue assisting if the issue persists.

Viewing 15 replies - 1 through 15 (of 36 total)