Pial
Forum Replies Created
-
Hi @spidergas ,
Thank you so much for taking the time to share your experience. We truly appreciate your kind words and it really means a lot to our team.
Just a small note. It looks like your message was added as a comment under another review. If you would like, you can also share your feedback directly on the review page so other users can easily see it and understand your experience with the plugin as well.
You can leave your review here:
https://wordpress.org/support/plugin/essential-addons-for-elementor-lite/reviews/#new-postAnd here is a quick guide that shows how to submit a review:
https://d.pr/v/LXwa8pYour feedback genuinely helps other users learn about the plugin and it means a great deal to us. Thanks again for your support.
Have a wonderful day.
Hi @tmcavalini ,
Iām really happy to hear everything is working properly now. It means a lot to us that you took the time to confirm.
If you have a moment, I would truly appreciate it if you could leave us a quick 5 star review about your experience. It only takes about 30 seconds, and your feedback genuinely helps us continue improving the plugin and supporting users like you.
You can leave your review here:
https://wordpress.org/support/plugin/betterdocs/reviews/#new-postYour support makes a real difference for our team. Thank you again, and please feel free to reach out anytime you need assistance.
Have a wonderful day!
Hi @tmcavalini,
Just checking in regarding this issue.
Could you please let us know if you had a chance to test the development version we shared earlier? We want to confirm whether the fix has resolved the fatal error on your end.
If the issue is still occurring, kindly share your current PHP version as well so we can investigate further.
Looking forward to your update.
Hi @tmcavalini ,
We have implemented a fix for this issue on our end.
Could you please check the development version here and confirm if everything works correctly on your side?
If you are still experiencing the error, kindly let us know your current PHP version as well so we can double check compatibility.
Looking forward to your feedback.
Hello @wordpresslover7,
We have not heard back from you regarding this issue. Since there has been no further response, we are assuming that updating to version 2.1.0 has resolved the problem on your end.
For now, we are marking this topic as resolved. If you face the issue again or have any further questions, please feel free to reopen the thread and let us know.
Have a nice day.
Best regards,
PialHi @tmcavalini ,
It looks very likely that your site is currently running PHP 7.2 or an older version, which is causing this fatal error.
Please update your PHP version to 7.4 or higher from your hosting control panel. After upgrading, clear any cache and check the site again. In most cases, the issue resolves automatically once the server is running a newer PHP version.
At the same time, we will also review this internally and work on improving compatibility where possible.
Please let me know how it goes after the update.
Hello @wordpresslover7,
Just following up here š
Could you please confirm if updating to version 2.1.0 has resolved the PHP notice on your end?
Looking forward to your feedback.
Best regards,
PialHello @iapial ,
We have fixed the issue. Please update the plugin to the latest version 2.1.0.
After updating, kindly check and let us know if everything is working properly on your end.
Best regards,
Hi @dumel,
Since we have not heard back from you for a while, we are going ahead and marking this topic as resolved for now.
If you still need help, please feel free to reopen the thread and share your requirements in a bit more detail. Let us know what you are trying to build so we can better understand your use case and guide you using the most suitable widgets.
Thank you.
Hi @pjmoore2026,
Since the issue appears to be isolated to the College network and the carousels are functioning correctly outside of it, we are marking this topic as resolved for now.
If you face the issue again or need further assistance, please feel free to open a new topic and we will be happy to help.
Thank you.
Hi @czerwonacegla,
Thank you for your update.
Since we already provided the fixed development version, could you please make sure that you have updated the plugin using the ZIP file we shared earlier? If you have already done so, kindly double check that the updated version is active on your site.
After installing the ZIP file, please follow these steps carefully:
- Clear all caches including browser cache, plugin cache, and any server or CDN level cache if applicable.
- Regenerate Essential Addons assets
Go to wp-admin ā Essential Addons ā Tools and click on the Regenerate Assets button.
Screenshot reference: https://d.pr/i/vNnrn9
Please make sure the regeneration completes successfully. - Clear Elementor cache
You may follow this guide to properly clear Elementor cache:
https://d.pr/i/mG6nMD - After completing the above steps, please test the Masonry widget again. If possible, kindly also test it on a completely new blank page to rule out any page specific conflict.
Asset regeneration is important after updating via ZIP, as older compiled files can sometimes still be served and cause unexpected behavior.
Please let us know the result after trying the steps above. We will be happy to continue assisting you.
Thank you.
Hi @pjmoore2026,
Thank you for the detailed update and for taking the time to test the site across different environments. That was very helpful.
Based on what you described, it does strongly suggest a network level restriction on the College side rather than an issue with the carousel configuration itself. Since the carousels are working properly outside the College network, the widget and its scripts are loading as expected in a normal environment.
In cases like this, the most common causes tend to be:
ā¢ Firewall or content filtering rules blocking certain JavaScript files
ā¢ CDN domains being restricted
ā¢ Aggressive network level caching serving outdated script files
ā¢ Security policies preventing inline or dynamic JavaScript executionFor your IT team, it may help to check whether any of the following are being blocked:
ā¢ JS files related to Essential Addons or Elementor
ā¢ CDN resources used by the plugin
ā¢ Swiper.js or other carousel related script libraries
ā¢ Console errors in the browser developer tools on affected machinesIf possible, please ask your IT team to open the browser console on a College connected desktop and check for any red error messages when loading the homepage. That information would be very useful in pinpointing exactly what is being restricted.
Hope It helps
Hello @wordpresslover7 ,
Really sorry for the delay here, and thank you for reaching out.
Please note that Simple 301 Redirects follows a limited release cycle, where updates are mainly focused on security related and critical improvements. Since there were no such changes required recently, there has not been a new release during this period.
That said, this item is already assigned to our team. We are hoping to include it in an upcoming release very soon.
In the meantime, we highly recommend giving our AI-Powered Link Management – BetterLinks a try. BetterLinks is the updated and actively maintained version of this plugin and receives regular updates with new features and improvements. It is completely free to use, and you can migrate your existing redirects to BetterLinks with a single click, so you can test it without any hassle.Again, we appreciate your patience, and please feel free to reach out if you have any further questions.
Best regards,
PialHello @bensonbrad
Thank you for sharing the Site Health information. I have reviewed it carefully. Even though the memory limits are set quite high, memory usage can still fluctuate depending on how many dynamic elements and widgets are used, especially with complex Elementor layouts. This can sometimes result in unexpected 500 errors.To help us investigate further, could you please enable the WordPress debug log and try editing the page again? Please set WP_DEBUG and WP_DEBUG_LOG to true, keep WP_DEBUG_DISPLAY disabled, and then share any errors from the debug.log file. This will help us identify what is triggering the issue.
Since you have reached out to us directly as well, we have already replied there with some additional details and next steps.
Looking forward to your update.
Hello again @flatword ,
Hope you are doing well.
Just following up here. Since we have not heard back from you after our last response, I am going to mark this topic as resolved for now.
If the issue still persists or comes up again, please create a new thread and share the details there. We will gladly help and continue from that point.
Have a nice day.