Saravanan S, a11n
Forum Replies Created
-
Forum: Reviews
In reply to: [Google for WooCommerce] Strong contender for worst plugin ever@joe388 sorry about the troubles. We believe we can fix this looping issue during your setup of the extension, if you are willing to try again and you can start a new support thread, for help. We understand if you have already moved on to a different plugin.
Forum: Reviews
In reply to: [Google for WooCommerce] Strong contender for worst plugin ever@joe388 , No worries. If you found a plugin you like that helps with your need, we are happy for you, and no, we didn’t want you to be our QA. Thanks.
Forum: Reviews
In reply to: [Reddit for WooCommerce] Great support for third party developersHi @alekv ,
Thanks for taking the time to leave a review. We appreciate your time and feedback. We are equally excited for the upcoming releases.
Forum: Reviews
In reply to: [Google for WooCommerce] PHP errorsHi @vitovisentini,
Thanks for rating the extension though you are having issues with the Php errors. Thanks for bringing this to our notice. Our developers have been notified of your issue and will review this peformance issue and a future update should address this issue soon.
Forum: Reviews
In reply to: [Google for WooCommerce] Strong contender for worst plugin everHi @joe388 ,
Sorry to hear about your issues.
I reviewed your profile and any support threads you have created and couldn’t find any topics, where you have requested for help with your issues with Google For WooCommerce. It’s not clear why you say worst plugin, although you haven’t requested for help in the forums.
Could you please create a new support thread, so we can assist you further? Thanks.Forum: Reviews
In reply to: [Google for WooCommerce] It’s not easy to make it work but I finally couldHey there @onetailer ,
Sorry to hear about your issues.
I reviewed your profile and any support threads you have created and couldn’t find any topics, where you have requested for help with your issues with Google For WooCommerce. It’s not clear why you say it doesn’t work, although you haven’t requested for help in the forums.
Could you please create a new support thread, so we can assist you further? Thanks.Forum: Reviews
In reply to: [Google for WooCommerce] Good SupportHi @ercanbora ,
Thank you for taking the time to leave a positive review and for your patience working with us to get the issue resolved.Forum: Reviews
In reply to: [WooCommerce Analytics] Great plugin with potentialHi @benoitfouc ,
Thanks for the positive review and the team is aware of these metrics and are already evaluating adding such filters and comparison option to the metrics. These feature requests are tracked here if you are interested in voting for them. While these feature might not show up in the next version of the plugin, they are definitely in the works and will be made available soon.Hi @svennnax ,
Could you confirm for us if you have tried recreating a new post email notification?
In some rare cases, a Post Notification email might not send and there’s no apparent reason why. It’s possible something got corrupted in the email template. When this happens, try recreating the email from scratch to see if it fixes the problem. if the new email is sent correctly, then it’s safe to delete the old one.
Do keep us posted on how this troubleshooting works out for you.
Hello,
Thank you for the detailed technical explanation and for confirming that the issue is resolved in a clean browser environment. You’ve identified exactly what’s happening – the browser is treating the license key field as a password field due to the
type="password"attribute and automatically filling it with stored credentials, even when no MailPoet-specific data was intentionally saved.Your suggestion about adding
autocomplete="off"orautocomplete="new-password"attributes, or reconsidering the field type altogether, is spot on from a technical standpoint. This is definitely something our development team should review to prevent this autofill behavior from affecting other users.I’ll make sure to pass this feedback along to our development team as a potential improvement for future updates. The technical details you’ve provided will be very helpful for them to understand the root cause and implement an appropriate solution.
In the meantime, as a workaround, you can:
– Clear the saved autofill data for your site in your browser settings
– Disable autofill for password fields in your browser preferences
– Use a different browser for MailPoet administration
I really appreciate you taking the time to investigate this thoroughly and provide such clear technical details. This kind of feedback helps us improve the plugin for everyone. If you encounter any other issues or have additional suggestions, please don’t hesitate to reach out.
Forum: Reviews
In reply to: [Google for WooCommerce] Not syncing at allHi @kenttkh92 ,
Sorry to hear about your issues with syncing your products to Google Merchant Center .
I reviewed your profile and any support threads you have created and looks like this review was may be too early as we are still awaiting your response in the thread?
Could you please reply to our team, so we can assist you further? Thanks.Hi @jackmeat ,
Sorry to hear about the issue with the activation links not working as expected. Could you confirm for us if you are using only the shortcode as [activation_link] or are you using it alongside a
http://text. Could you try the instructions here on how to use the activation link shortcode in your emails and let us know if that works as expected? If you don’t see any improvements, could you share a screenshot of the issue in your emails?Could you keep us posted on how the recommended suggestion works out for you?
Hi @svennnax ,
Thanks for testing the automations and confirming that only the new post notification emails aren’t working, but any other scheduled newsletters are sent as expected. This indicates that something odd is going on from the time when you publish a post to how that triggers an email in MailPoet.Could you help us understand, your workflow when you publish a blog post? Perhaps that can give us a clue on if something isn’t working well with MailPoet and we can address that.
We look forward to hearing back from you as soon as possible.
Hi @heron0debaro ,
Thanks for working with us via the form for this specific request and for making this request solved. We appreciate it.
Have a lovely day ahead!!
Hi @andreadelriva ,
Thanks for marking this issue resolved. We appreciate your promptness and helping keep the forums updated.Have a lovely day ahead!!