Alimir
Forum Replies Created
-
Hey @manishkmalla
Thanks for reaching out!
This issue has already been fixed in our latest update (version 5.0.2), and it has been reviewed and approved by Wordfence ✅
It looks like the status hasn’t been marked as “resolved” on their side yet—probably just a small oversight. We’ve already contacted them to update it.
In the meantime, you can rest assured that WP ULike is fully safe 👍
Hey @fff654
Yes 🙂 WP ULike supports all standard post types stored in thewp_poststable.Hi @ruzakuku ,
Just following up on this. Since we haven’t heard back from you, we’ll mark this topic as resolved for now.
If the issue still persists or you have any updates, feel free to reply here and we’ll be happy to take a closer look.
Forum: Plugins
In reply to: [WP ULike – Like & Dislike Buttons for Engagement and Feedback] FeedbackHi Michael,
Thank you so much for the honest feedback and for using WP ULike over the years, it really means a lot to us.
I totally understand your concern. Our goal has always been to make WP ULike a solid and lightweight solution focused on engagement. Some features (like SEO-related tools) were added based on real user requests and changes in Google’s policies over time, especially when aggregate ratings were limited to specific content types. In those cases, we tried to keep things working rather than adding features just for the sake of it.
That said, we’ve always been very careful with the free version. It’s still designed to stay fast, stable, and focused on what it does best: simple likes and meaningful stats. In fact, the current version is one of the lightest and most optimized releases we’ve ever built.
I’m really sorry about the critical error you experienced — that’s definitely not the experience we want anyone to have. If you ever feel like giving WP ULike another try, I’d be more than happy to help you personally and make sure everything runs smoothly.
Thanks again for your kind words and your trust over the years. Feedback like yours helps us keep WP ULike on the right path and improve it step by step.
Warm regards,
AliHi @ruzakuku , thanks for reporting this.
We haven’t received similar reports about the like buttons disappearing in version 5 so far, so we’d like to understand the issue better.
Could you please clarify where exactly the problem happens?
Is the like button not showing on posts, pages, or both (e.g. homepage, single posts, or custom post types)?Also, please try opening WP ULike → Settings and click Save Changes once, even if you didn’t modify anything. In some cases, this helps reinitialize the settings after the update.
If the issue persists, please let us know your WordPress version and theme name so we can investigate further.
Best regards,
Ali@michael8888 please update to V5 🙂
Hey @michael8888
We’ve identified the issue as coming from a third-party framework used for Customizer options. While it existed before, recent WordPress changes seem to have increased its performance impact.
We’ll release a fix soon to reduce the overhead, and we’re also planning to replace this framework with a lightweight custom solution to fully resolve the performance issue.
Thanks for the detailed profiling.
— AliJust a quick update from our side! We’ve added a small code snippet for WP ULike users to prevent conflicts with your plugin’s scripts on our stats page. The snippet is documented here:
https://docs.wpulike.com/article/72-prevent-plugin-script-conflicts
It’s working well, but it would still be ideal if your assets could automatically load only on MonsterInsights’ own admin pages. This would avoid any potential conflicts with other plugins and make the admin experience even smoother.
Hey @erisf
Thanks for reaching out and sorry if your earlier emails didn’t get through to us. We’d love to help you fix this issue!
If possible, could you please share an online link where we can check it directly? Also, it would be helpful if you could let us know your logging method configuration and whether you’re using any specific caching system or plugin on your site.
This info will help us troubleshoot the problem much faster.
@itdcmy Thanks for reporting this! 🙏
From the error details you shared, it looks like the issue is coming from WooCommerce’s Admin/Analytics script (index.jsfrom WooCommerce 9.8.1). This script is being loaded on our statistics page and is failing withanalyticsbeing undefined.Our plugin doesn’t call WooCommerce’s analytics functions directly, so the error is most likely caused by WooCommerce itself or another plugin hooking into WooCommerce Admin.
Here are a few things you can try:
- Make sure WooCommerce is updated to the latest version.
- Go to WooCommerce → Settings → Advanced → Features and check if “WooCommerce Analytics” is enabled.
- Temporarily disable other plugins (except WP ULike + WooCommerce) to see if one is conflicting.
- Clear any site caching / browser caching.
If the problem continues, you may want to report it directly to WooCommerce support, since the error is inside their admin app.
In the meantime, WP ULike statistics should still work — but this WooCommerce error can prevent the page from rendering properly, so fixing/removing the WooCommerce analytics error will solve it.
Hey @haru3
Thanks for your report, and you’re absolutely right! 🙏 At the moment, the datetime is being saved localized in the database, which isn’t correct. We’ll be changing this in the next update, and that will fix the double correction issue.Hi @vanjaz ,
You’re absolutely right — thanks for pointing this out! We’ve been able to reproduce the issue on our side and identified the cause. Our team is already working on a fix, and we’ll be releasing an update in the next few days to resolve it.
Really appreciate your patience and for bringing this to our attention 🙏
Hey @tatianaflow
Please update the plugin to the latest version.Hi,
Thanks for reaching out. We’ve recently reviewed this report and want to clarify that it’s related to a known behavior where users can generate spam likes if voting is not restricted to logged-in users. This is not a security vulnerability but rather an abuse of open access settings.
We’ve seen this issue before and are actively working on a more robust solution. However, it’s a bit complex due to the ability of users to change their IP addresses, which makes standard rate-limiting less effective.That said, I can assure you there is no security risk to your website or its data integrity.
In the meantime, we strongly recommend enabling the “Logged-in users only” option in the plugin settings to prevent such behavior.
We’re also in contact with the source of the report and will request a title change or removal once our solution is finalized.
Thanks for your patience and understanding!
@contemplate done. please update to the latest version. 🙂