Joel

Dear flexpavillion

First of all, I would like to sincerely apologize for the issue you are facing and thank you for your patience while we reviewed your case.

Be reminded that according to www.remarpro.com’s guidelines, we can’t offer support for commercial products here. In order to provide you with the best possible assistance, please create a ticket directly with our dedicated support team.

When you submit the ticket, you should receive a case ID in a format similar to “Case #JS8723HJKXXX.” Please share this case ID with us once it’s been created so we can confirm that it’s been received and continue to monitor your issue.

Thank you again for your understanding and cooperation. We look forward to resolving this matter as quickly as possible.

Best regards,

Hello, flexpavillion

I hope this message finds you in good spirits. I’m sorry to hear that you are having this experience.

I understand that you are getting an error message- “Status: Error Reason: Unsupported file format. Only JPEG, PNG, WEBP, or GIF are supported” for images that were previously optimized but are now being restored- it can be due to several factors. I’ll try to help you with the information I’ve gathered. The best thing to do would be to write to Elementor direct support and provide more information related to the issue, such as system information and error messages in the Google console. However, I will do my best to help you.

1. Cached data from the first optimization process could interfere with the second attempt. The system may be referencing old or corrupted cache data. Clear all caching mechanisms (both server and browser) that may be interfering with the image optimization plugin.
2. In my experience, the files may be corrupted or changed after restoring the images, which may have been modified or corrupted. This could change their internal formatting, causing the optimizer not to recognize them as valid PNG or WEBP files. Try downloading the restored images and making sure they display correctly in standard image viewers or editing software. If the images do not open, they are probably damaged.
3. There might be an issue with our image optimization tool, either a bug or a server-related limitation that does not recognize the restored images. Make sure that the file permissions of the restored images are correct. Sometimes, incorrect permissions can prevent our optimizer from accessing or modifying the files.
4. If the above does not work, it is possible that the restore process reverted the files incorrectly or that they were restored in a different or invalid format. The underlying file structure could be incorrect even if the file extensions are .png or .webp. Try downloading the restored images and then reactivating them in the media library. This may avoid any potential issues caused by the restoration.

If none of these steps resolves the issue, we can dig deeper by inspecting the Google Console errors and system information. In this case, sending us the page or additional information may help us detect any errors or conflicts in the console after running these staging.

Let me know how it goes or if you need further assistance!

Have a fantastic day/evening. 

Hi,

Thanks for reaching out! 

It looks like there may be an issue related to how the floating bar loads or how the scripts interact with the page during the refresh.

• Please check switch to a basic theme (like the Hello theme) and see if the issue persists. This can help determine if your theme is causing the problem.
• Also you can try duplicate the page and test the floating bar on a completely blank page to isolate whether another page element is causing the issue.
• Sometimes browser extensions or session-based issues can interfere with how the page loads. Try testing the site in incognito mode to rule this out.
• Finally, Temporarily deactivate all plugins except for the essential ones and check if the comment section reappears. If it does, reactivate the plugins individually to identify if any of them are causing conflicts.

If none of these steps resolve the problem, we can dig deeper by inspecting how the floating bar script interacts with other elements on the page. In this case, sending us the page or additional information may help us to detect any error or conflict in the console or after running these tests.

Have a fantastic day/evening.

Hello,

Thanks for reaching out! We’ve previously resolved similar concerns for many users and are ready to help you. If you have Elementor Pro, do refer to our specialized Pro support here.

To get quicker help, please get in touch with us via ‘My Elementor‘, and we’ll be on it right away.

Be reminded that according to www.remarpro.com’s guidelines, we can’t offer support for commercial products here. Thanks for your patience and understanding.

Wishing you a great day!
Kind Regards,

Hello,

Thank you for reaching out. We’ve successfully addressed similar issues for other users and are more than willing to assist you as well. If you’re utilizing Elementor Pro, please use our dedicated Pro support.

To expedite assistance, kindly connect with us through your ‘My Elementor‘ account, and we’ll prioritize resolving your concern swiftly.

Please note that as per www.remarpro.com guidelines, commercial product support isn’t provided on this platform.

I appreciate your understanding.

We are wishing you a pleasant day ahead.

Kind Regards,

Hi,

Thanks for reaching out! 

To set all Accordion widgets to expand by default in Elementor, there isn’t a built-in option to achieve this directly. 

Alternatively, there could also be third-party plugins or add-ons available that can offer that feature, so I would advise you to join the Elementor Community?? and check with our users there for such a plugin or other workaround recommendation.

Finally, you can send your feature request?, which will give your request more scope.

I apologize for not being able to provide you with this particular feature for the moment. Please let me know if you have any other questions or concerns regarding this consult. 

Thank you so much for your kind understanding.

Have a fantastic day/evening.

Hi Romain,

Thanks for reaching out! 

The problem could be related to the way our plugin handles custom fonts and styles. As -webkit-text-stroke can be inconsistent depending on the context or text rendering on certain platforms, I propose a workaround using Elementor Core styles that should work for all browsers.

Go to Heading widget > Text Stroke > Select the pixel you need.?

Screenshot: https://prnt.sc/JSKjYpvo8VRv

Let me know how it goes, or if you need further assistance!

Hi Romain,

Thanks for contact us! The issue you’re experiencing where you can’t edit with Elementor but the front-end works fine could be due to a few potential causes. Here’s a checklist of steps to help resolve it:

1. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
2. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
3. Go to Elementor > Tools > Regenerate CSS and click on it.. Afterward, go to Settings > Permalinks and hit “Save” without making any changes. This refreshes the permalinks and can sometimes resolve odd behavior.
4. Clear both your browser cache and any caching plugins that may be active on your website (such as WP Rocket, W3 Total Cache, etc.).

If none of these steps solve the problem, you might need to check your server’s error logs or contact your hosting provider to make sure there are no server-related issues.

Let me know how it goes!

Hello,

Thanks for reaching out! 

It sounds like the CSS files in your Elementor setup are either not being saved properly or being overwritten after page reloads. The fact that regenerating the CSS solves the issue temporarily points to a caching or file permissions problem. Here’s a step-by-step approach to troubleshoot and potentially solve this:

1. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
2. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
3. If you’re using a caching plugin (like WP Rocket, W3 Total Cache, etc.), Sometimes caching plugins conflict with how Elementor generates its CSS files. Disable any caching plugins temporarily and see if the issue persists. Or clear your site’s cache.?
4. Now, go to Elementor > Tools > Regenerate CSS and click on it.. Afterward, go to Settings > Permalinks and hit “Save” without making any changes. This refreshes the permalinks and can sometimes resolve odd behavior.
5. Ensure that your wp-content/uploads/elementor/css folder has the correct write permissions (typically set to 755 for folders and 644 for files). Incorrect permissions could prevent Elementor from saving the generated CSS correctly.

In some cases, the server’s caching systems or configurations (like Nginx rules, Redis, etc.) might be contributing to the issue. If none of the above helps, contact your hosting provider and explain the problem.

If the issue persists after these steps, you might need to restore a backup from a point before the issue started or if you using Elementor Pro,  reach out our support for further investigation.

Let me know how it goes, or if you need further assistance!

Hello,

Thanks for reaching out! 

It looks like the overlay is getting stuck due to an issue that could be related to our update and the way we manage the CSS. Since you’ve already cleared the cache and regenerated the CSS and data, let’s explore some additional steps to fix this issue:

1. Ensure that your theme is fully compatible with the latest version of Elementor. Sometimes, theme CSS might override Elementor’s settings.
2. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
3. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
4. Open the popup on your site and inspect it using the browser’s developer tools (right-click > Inspect). Look for CSS that forces the overlay to stay active. Check the popup container class and see if there are any styles (like display: block or z-index) that shouldn’t be there.

If the issue started after a specific update, try rolling back to a previous version of Elementor that worked fine (Elementor > Tools > Version Control > Rollback).

Also you can go to the section/widget where you’ve applied the “Zoom In” effect and review its settings. Verify the duration and scale values (under the Advanced > Motion Effects section). If the scale is too large, adjust it to a more subtle value (e.g., around 1.05–1.1 for a light zoom effect).

I hope this helps you to solve the problem. Let me know how these steps go, and if needed, we can dive deeper into specific aspects of the setup.

Hello,

Thanks for reaching out! 

It appears that the latest update to our plugin has caused the “Zoom In” animation to behave differently, causing a more pronounced effect than expected on your website. This could be due to changes in the way animations are handled by our recent update.

In our recent update, we have split animations.min.css into multiple CSS files and load them conditionally.

Go to Elementor > Tools > Regenerate CSS & Data. This will rebuild the CSS and JavaScript files for Elementor. Now, if you’re using a caching plugin (like WP Rocket, W3 Total Cache, etc.), clear your site’s cache.

Also you can go to the section/widget where you’ve applied the “Zoom In” effect and review its settings. Verify the duration and scale values (under the Advanced > Motion Effects section). If the scale is too large, adjust it to a more subtle value (e.g., around 1.05–1.1 for a light zoom effect).

I hope this helps you to solve the problem. Let me know how it goes, or if you need further assistance!

Hello,

Thanks for reaching out! 

These warnings are related to our plugin indicating that an attempt is being made to access user-related data (in this case, the user password and email property) but fails because the values are not set or are referenced incorrectly.

The error occurs when the Elementor code expects user information but it isn’t present, such as when there is no logged-in user or incomplete data for the current user. Sometimes conflicts with other plugins or your theme can cause issues with how user data is passed, especially if they modify or interact with the way Elementor processes user sessions.

1. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
2. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
3. Ensure that both WordPress and Elementor are up to date, as updates often fix bugs like these.

If the issue persists after these steps, you might need to restore a backup from a point before the issue started or if you using Elementor.

Let me know how it goes, or if you need further assistance!

Hello,

Thanks for reaching out! 

The error you’re encountering (Uncaught TypeError: Cannot read properties of undefined (reading ‘tools’)) typically suggests that there’s an issue with the initialization of an Elementor widget, potentially due to a conflict between JavaScript files or missing resources. Please try this:

1. Temporarily deactivate all plugins except for Elementor. Then, check if the issue persists. If the error goes away, re-activate plugins one by one to identify which plugin may be causing the conflict.
2. Temporarily switch to a default theme like Hello Elementor or Twenty Twenty-One. If the issue resolves, the problem might be related to your theme.
3. If you’re using a caching plugin (like WP Rocket, W3 Total Cache, etc.), clear your site’s cache. Now, go to Elementor > Tools > Regenerate CSS & Data. This will rebuild the CSS and JavaScript files for Elementor.
4. If you’re using custom code or JavaScript within Elementor, ensure they are coded correctly and compatible with the latest version of Elementor.

If the issue persists after these steps, you might need to restore a backup from a point before the issue started or if you using Elementor Pro,  reach out our support for further investigation.

Let me know how it goes, or if you need further assistance!

Hello,

Thanks for reaching out! We’ve previously resolved similar concerns for many users and are ready to help you. If you have Elementor Pro, do refer to our specialized Pro support here.

To get quicker help, please get in touch with us via ‘My Elementor‘, and we’ll be on it right away.

Be reminded that according to www.remarpro.com’s guidelines, we can’t offer support for commercial products here. Thanks for your patience and understanding.

Wishing you a great day!
Kind Regards,

Hello,

Thanks for reaching out! 

It seems you’re encountering a permission issue with one specific page on your website, while other pages work fine. The error message you’re seeing is related to server permissions, typically tied to Apache’s configuration or the file system on your hosting.

• Please check the file permissions of the page in question. Ensure the files related to that page have the correct permissions (usually 644 for files and 755 for directories). If you’re not sure how to check this, you can reach out to your hosting provider or check via your file manager or FTP.

• Sometimes a misconfiguration in the .htaccess file can block access to certain pages. Check if there are any custom rules or restrictions in your .htaccess that might be blocking access to this particular page. You can try renaming the .htaccess file to something like .htaccess_old and see if the page becomes accessible. If it works, the issue lies within the .htaccess file. In that case, you can regenerate it by going to Settings > Permalinks in WordPress and clicking Save Changes.

• Also, try deactivate all plugins except Elementor and see if the issue persists. If the page works, reactivate the plugins one by one to identify the conflict.

If not work, since the error message references “Apache Server at Port 443,” there may be server-specific issues. Contact your hosting provider’s support and ask them to investigate the server logs for any clues.

Let me know how it goes, or if you need further assistance!