Forum Replies Created

Viewing 15 replies - 151 through 165 (of 1,419 total)
  • Plugin Support Milos

    (@miloss84)

    Hello there,

    Thank you for being so patient.

    At the moment, Elementor does not include a global setting that completely disables all schema markup across the site. Schema output in Elementor is generated only by specific widgets and features, not by the core editor globally.

    In most real-world cases, duplicate schema happens because Elementor widgets such as Accordion, while the SEO plugin also generates JSON-LD for the same content. When both are active, Google detects duplicates.

    The recommended approach is to let the SEO plugin be the single source of schema and prevent Elementor from adding its own. This can usually be done by disabling schema at the widget level. For example, Elementor’s Accordion widget can output FAQPage schema, which should be turned off if your SEO plugin already handles FAQ schema. Similarly, the Star Rating widget outputs schema-related microdata in the HTML, which can conflict with SEO plugin review or product schema.

    If you need a hard stop and want to fully prevent Elementor from outputting schema regardless of widget usage, the safest workaround is to filter Elementor’s rendered output and strip the schema before it reaches the front end. This can be done via a small PHP snippet added to a child theme or a snippets plugin. The filter targets only Elementor widgets known to generate schema and removes their structured data without affecting your SEO plugin.

    Best regards,

    Plugin Support Milos

    (@miloss84)

    Hi,

    Thank you for you great feedback,

    Since you are an Elementor One user, you can open a support ticket at my.elementor.com ref: https://elementor.com/help/how-to-submit-a-support-ticket/ I’d also suggest you check out Elementor Community Group on Facebook.

    We have created it to connect Elementor users together and share knowledge, Global Elementor Community.

    WordPress.org rules state that commercial products are not supported here.

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thank you for contacting us.

    If you’re still seeing these requests, a few possibilities could be causing them:

    1. Caching / CDN: Sometimes cached scripts from before the update continue to load, even after updating Elementor. Clear your site cache, browser cache, and any CDN cache (Cloudflare, etc.) and test again.
    2. Plugins or theme integrations: Some third-party Elementor addons or themes may include legacy Elementor code that still references Mixpanel. Temporarily disable other plugins and switch to a default theme to isolate the source.
    3. Staging / old script remnants: Check if your site is running old versions of Elementor JS/CSS from the /uploads/elementor folder or a child theme. Make sure all Elementor assets are fully updated.
    4. Incorrect version or update issue: Confirm that Elementor is fully updated and that the update completed successfully.

    Hope this helps.

    Kind regards

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thank you for contacting us.

    If a visitor loads a page built with Elementor, Elementor itself does not independently collect or store that visitor’s IP address. Elementor is a page builder plugin that runs on your own WordPress site, so any visitor data (including IP addresses) is processed by your website and hosting environment, not by Elementor as a separate service.

    That said, IP addresses may still be processed in these cases:

    • By your web hosting provider / server logs
    • By WordPress itself (for example, comments, security, or caching)
    • By third-party services you use (analytics, CDN, etc.)

    Hope this helps.

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    Hi there

    Thank you for contacting us.

    This error usually means the Elementor “common” script is not loading at all, or it’s loading too late, so frontend-modules tries to use it before it exists. In practice, this is almost always caused by a plugin conflict or JavaScript optimization, even when caching appears to be disabled.

    Please temporarily disable all plugins except Elementor (and Elementor Pro, if you’re using it) and check the page again. This step is important even if you’ve already tested plugins before, as this specific error is very commonly caused by plugin-level JS interference.

    If the error disappears, re-enable the plugins one by one until it comes back. The plugin that triggers it will usually be doing JS delay, defer, or optimization.

    Also make sure there is no JavaScript optimization happening outside of plugins, such as hosting-level optimization or Cloudflare Rocket Loader, which is a very common cause of this issue.

    After that, go to Elementor → Tools → Regenerate CSS & Data, then clear all caches.

    If the error still remains, reinstalling Elementor is the next step. Delete the plugin and install it fresh. This often fixes cases where files didn’t update cleanly.

    If you want, send me a link to one affected page and I’ll check exactly what’s breaking the script load order.

    Best regards,

    Plugin Support Milos

    (@miloss84)

    Hi,

    Thank you for taking the time to share such direct and detailed feedback. We genuinely appreciate it.

    I’m sorry for the frustration these changes have caused. I completely understand how excessive promotional content, AI elements, and widgets are enabled by default.

    I also understand your concerns about the menu change, especially when important items are moved to the top in a way that feels unintuitive and disrupts established workflows.

    Your comment about it feeling like “a CMS within a CMS” is especially insightful and clearly reflects how these changes can come across from a user’s perspective.

    Please know that I will pass your feedback along in full to management and the relevant teams. Input like this is extremely valuable to us because it comes from real-world usage, not just internal assumptions.

    Once again, I’m sorry for the negative experience, and thank you for being honest with us. If you have any additional examples or suggestions, feel free to share them.

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    Hi,

    Video – https://www.loom.com/share/00ff2d9de5ee408eab56c460ce6d12ee

    Since you are an Elementor Pro user, you can open a support ticket at my.elementor.com ref: https://elementor.com/help/how-to-submit-a-support-ticket/ I’d also suggest you check out Elementor Community Group on Facebook.

    We have created it to connect Elementor users together and share knowledge, Global Elementor Community.

    WordPress.org rules state that commercial products are not supported here.

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thank you for contacting us.

    Can you please contact you hosting provider to check this and fix from their side,

    Looking forward hearing from you.

    Kind regards

    Plugin Support Milos

    (@miloss84)

    Hi,

    Since you are an Elementor Pro user, you can open a support ticket at my.elementor.com ref: https://elementor.com/help/how-to-submit-a-support-ticket/ I’d also suggest you check out Elementor Community Group on Facebook.

    We have created it to connect Elementor users together and share knowledge, Global Elementor Community.

    WordPress.org rules state that commercial products are not supported here.

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thank you for reaching out.

    If you’re still seeing these requests, a few possibilities could be causing them:

    1. Caching / CDN: Sometimes cached scripts from before the update continue to load, even after updating Elementor. Clear your site cache, browser cache, and any CDN cache (Cloudflare, etc.) and test again.
    2. Plugins or theme integrations: Some third-party Elementor addons or themes may include legacy Elementor code that still references Mixpanel. Temporarily disable other plugins and switch to a default theme to isolate the source.
    3. Staging / old script remnants: Check if your site is running old versions of Elementor JS/CSS from the /uploads/elementor folder or a child theme. Make sure all Elementor assets are fully updated.
    4. Incorrect version or update issue: Confirm that Elementor is fully updated and that the update completed successfully.

    Hope this helps.

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thanks for contacting us again, if the issue stoped after deactivating ShopBuilder – WooCommerce Builder For Elementor

    Therefore, we highly recommend that you report this issue to the support team for this plugin, so they may further troubleshoot and provide any recommendation (or possible fix) to resolve this issue.

    Should they need any help from us, they can open an issue on our Github account and our developers will be happy to assist. https://github.com/elementor/elementor/issues

    For reference: What do we Support?

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Could you please share your site URL so we can review the Developer Console and Network tab for any relevant issues?

    We look forward to hearing from you.

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    Hi there,

    As 368durham explains, this isn’t a PHP 8.3 incompatibility with Elementor. The key part of the error is:

    “Call to undefined function … mb_convert_case()”

    mb_convert_case() is provided by PHP’s mbstring extension. What’s happening is that your server is running PHP 8.3 without mbstring enabled, so Elementor can’t call that function and WordPress crashes in the admin.

    Please ask your hosting provider to enable/install the PHP mbstring extension for the PHP 8.3 environment used by your site (it’s often a toggle in their PHP Selector / MultiPHP INI, or it needs to be enabled at the OS package level).

    Looking forward to hearing back from you soon.

    Kind rgards,

    Plugin Support Milos

    (@miloss84)

    Hi there,

    Thanks for contacting us and hope you are doing well and having a great day.

    To rule out the possibility of a plugin or theme conflict, please deactivate all your plugins (besides Elementor ). If it solves the issue reactivate them one by one to find the culprit. If it didn’t help, switch your theme (temporarily) to a default WP theme such as Twenty Nineteen and see if it makes any difference.

    Also, this could happen due to our Elementor performance experiments you can try to deactivate them. To deactivate them you can go to Elementor > settings > features

    Performance features currently in the experimental stage are:

    • Element Caching – Elements caching reduces loading times by serving up a copy of an element instead of rendering it fresh every time the page is loaded. When active, Elementor will determine which elements can benefit from static loading – but you can override this

    I am looking forward to hearing back from you soon.

    Kind regards,

    Plugin Support Milos

    (@miloss84)

    HI there,

    You can try to report this issue to the support team for this WPML plugin, so they may further troubleshoot and provide any recommendations (or possible fixes) to resolve this issue.

    Should they need any help from us, they can open an issue on our Github account and our developers will be happy to assist. https://github.com/elementor/elementor/issues

    For reference: What do we Support?

    Kind regards,

Viewing 15 replies - 151 through 165 (of 1,419 total)