Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author rektification

    (@rektification)

    Hey @ferraz13galo

    There’s no easy way to do this. If you’re comfortable editing your database, then you can manually update the user id in the order meta table, but I wouldn’t recommend this unless you know what you’re doing. The other option is to remove them from the group, cancel the current subscription, and have them re-purchase the subscription with a 100% off coupon code (assuming they’ve already paid the first time). This is the cleanest way, though does involve a little more friction for your user.

    We could consider building in a utility for this, but it might some time before we can get to it. How many cases of this do you expect in a month or year?

    Plugin Author rektification

    (@rektification)

    Hi @reza10

    Thanks for reaching out, and for the kind words.

    As for the reminders, the plugin itself doesn’t have this functionality built in. On the Pro version, this would be handled by WooCommerce Subscriptions. In cases where it’s being used with a Simple Product, you could potentially use a plugin like AutomateWoo, but even then we might need to add a hook for that to work. Since these are features covered by the Pro version, you can head over to the website and fill out the contact form providing your use case (Simple product or Subscription), and we can look into what we can do to extend that functionality.

    Kind regards,
    Nick

    Plugin Author rektification

    (@rektification)

    Hey @ferraz13galo

    This is a good suggestion. We’ll investigate what’s involved and see how we can implement this.

    Thanks again!

    Plugin Author rektification

    (@rektification)

    Thanks for the suggestions! The first suggestion is already being worked on. We’ll take a look at the second one to see how we can implement something like this.

    Thanks!

    Plugin Author rektification

    (@rektification)

    Great questions!

    >1) How can I check every once in a while that the plugin is working well? I’m afraid of it stop working for any reason in the future and inactive costumers keep staying in the groups/channel.

    You can check a couple of things. First, the WooCommerce logs. If the wctlgm-subscriber-manager logs have recent entries, then the plugin is working. You can check other WooCommerce log entries. For example, check the fatal-errors log if you see one and check if any are related to the plugin.

    If you are using a simple product with an expiry, you can check the Scheduled Actions tab in WooCommerce > Settings. The expiry actions use action scheduler. If you see any failed actions related to wctlgm, then you might have an issue.

    >2) How can I see a costumer Telegram ID/username? This is important in case of any need of manually dealing with some situations. It would be good to see costumer username, as telegram doesn’t allow searchs by ID.

    This in something on the roadmap to add. We’re hoping to get this included in version 2.0 of the plugin but we’re still in very early development on this. The intent is to include a table in the plugin settings where you can view users, their ID’s, order/subscription status, etc.

    In the meantime, you would need to check the logs and do a database query for order meta to get the details. However, we don’t currently store the Telegram username in the database, so you won’t be able to cross-reference this.

    Plugin Author rektification

    (@rektification)

    @ferraz13galo I’m happy to hear you found a work-around for now until we resolve the issue. Interestingly, we’ve not had any other reports of this. A potential cause could be how transients are stored in your cache, meaning the type of object cache (Redis/Memcached) could interfere with reads across servers, or be returning a non-expected truthy value. The next plugin release will include a broader logic check to account for these variations, plus some extra logging to try and trace the issue.

    In the meantime, please let me know if you run into any other issues.

    Plugin Author rektification

    (@rektification)

    @ferraz13galo Your steps are perfect, this is exactly what you need to do.

    It’s possible Cloudflare is blocking the webhook signals in this case (from your video it looks like you are using Cloudflare). If so, you will need to change some settings in Cloudflare to allow the webhook signals through. The endpoint that needs to get through will be /wp-json/wctlgm/v1/telegram-bot/.

    In this case, maybe you need to “Skip” all protections in WAF -> Custom rules for /wp-json/wctlgm/. Also, if not already set, in Cache Rules, set a Bypass for /wp-json/*.

    If this still doesn’t help, then try to view the Cloudflare logs and your server logs to see if this is getting blocked.

    Looking forward to your reply.

    Nick

    Plugin Author rektification

    (@rektification)

    Hey @ferraz13galo ! Sorry to hear you’re having issues, but also thank you for sharing the video, that was very helpful.

    My first suggestion is to make sure you click “Save Changes” in the settings after adding your bot ID and url, then after saving, click on “Set Webhook”. Having said that, from the video I can tell it seems to set correctly. You can click it again just to be sure though.

    The next step is to “EDIT” a message in the channel. So after you send the message, you need to make a small edit to it. This is the signal the bot sends to the plugin with the channel ID.

    We’ve also recently added some documentation to our site, this article in particular might be helpful: https://wctlgm.com/kb/how-to-add-a-private-channel-or-group/#1-toc-title

    I hope this helps, if not please let me know.

    Kind regards,
    Nick

Viewing 8 replies - 1 through 8 (of 8 total)