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.
@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.
Hello Nick. I sent your reply to my our dev, who helps me out with technical stuff.
He sent me the cloudfare logs and the plugin logs.
He said there is no block on Cloudfare. And said that the plugin logs shows that the plugin identified the edited message. It just didn’t work after that.
After seeing the logs, my dev told me to try to put, manually, the channel ID, and it worked well after testing in a simulated purchase.
The bot worked in the channel. Therefore, the “get id” function still doesn’t work and I think you guys should take a look at it… I will buy the pro version and I get in contact in any problem.
@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.
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.
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.
>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.
A have 2 suggestions for you guys: 1) To store the telegram username and first name/Last name. This is useful in case of banning any member for bad behaviour, for example. Because I need to ban in Telegram an in my website, so this member won’t be able to buy again.
2) To have a “Plugin Status” tab, in which the plugin checks those logs and returns if it is working or not. If not, it could show the possible issue, as the logs could be a diagnosis.
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!
Viewing 10 replies - 1 through 10 (of 10 total)
The topic ‘GET ID function doesn’t work’ is closed to new replies.
