Developer Add-On error

  • sstaboulis

    (@sstaboulis)


    3 days, 12 hours ago

    Hello!
    I have been working on the implementation of Developer add ons for the pretty links, but I am now stuck with an issue with the add on.
    I am trying to use the webhook tool for any Pretty link created in the portal, I have created a cloud run function with GCP in order to expose a URL and get the notifications sent by the webhook, all good till here, I have clicked the test send button and for linked added event and I see I get the notification in my endpoint, the only thing is that I do not see the header PRLI-API-KEY to authenticate the request as the documentation website says, so this is something to check why I am not getting that header?
    So, since I did not get the header I though was because it is not a real pretty link addition event, it was just a test, so I have created a new Pretty link, but now the issue is that I do not get any notification in my endpoint and I do not see any way to see the logs or something similar within the plugin in WordPress, so mainly there are 3 questions:

    1. is it ok that I do not see the header PRLI-API-KEY when I click send test button in the Events section?
    2. do I need to do something special in order to get working the webhook notifications for real examples (from send test button works)?
    3. Is there a way to see any log or errors when happen regarding the Developer tools Add on? I am just wondering if there is any error while triggering the event in the backend but I do not see any way to get those logs.

    thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support oiler

    (@eulerarthur)

    3 days, 4 hours ago

    Hi there,

    Thanks for reaching out!

    You’re right about the header, and your report actually helped us track it down. Webhook notifications weren’t sending the auth header because of a mismatch on our end between where the key is stored and where it’s read from, so that part wasn’t anything wrong on your side (more below).

    On the second question, about test sends working but a real link creation not triggering anything: those two go through different paths. The test button sends immediately, but real events get queued and sent out through WordPress cron, so there’s normally a delay. Worth double checking that your webhook URL is saved with “Link Added” (or “All Events”) enabled, and that cron is actually running on your host, since some hosts disable or delay it (specially if the website doesn’t receive many visitors). If that’s fine and you still don’t see anything after a couple of minutes, let us know.

    As for logs, there isn’t a delivery log in the plugin UI right now, so the Events tab won’t show you what happened in the backend. If you have access to the site’s database, you can check the prlidt_events_events table to confirm the event actually fired, prlidt_resque_jobs to see if it’s queued but hasn’t gone out yet, and prlidt_resque_failed_jobs for the actual error if delivery failed after cron ran.

    Further, since Developer Tools is a premium add-on, to actually get the header bug patched on your site we’ll need you to open a request through our premium support channel here: https://prettylinks.com/premium-support-request/. Once that’s in we can sort out the fix and take a closer look at the delivery issue too.

    Looking forward to your reply. Thanks!

    All the best,
    Euler.

    Thread Starter sstaboulis

    (@sstaboulis)

    2 days, 12 hours ago

    Hi Oiler,


    Thanks for the response here, regarding the premium support ticket I already created one before posting here, it was on last Friday 26th June and I have not got any response till now, I have created a new ticket though that form hopefully I got a response as faster as I got here in the forum.

    regarding the cron process I found something interesting, I was checking the cron prlidt_resque_jobs_worker and it is active in our host and is running every minute but for some reason it is not picking up the events in the table wp_prlidt_resque_jobs, but when I run the cron manually wp cron event run prlidt_resque_jobs_worker, for some reason the events where picked up and now the queue table is empty and all events moved to wp_prlidt_resque_completed_jobs, is there a specific configuration or option we need to have in consideration for this cron since this is active and running, but automatically is not picking up the events but manually it is?

    Thanks

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

You must be logged in to reply to this topic.