You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/authentication/configuration/email-sms-templates.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ It will be useful to take a look at the following terms as they will reappear in
23
23
24
24
### Revolvapp WYSIWYG email editor plugin
25
25
26
-
The email editor uses the [Revolvapp](https://imperavi.com/redactor/legacy/revolvapp) email template editor plugin by Imperavi. To acquaint yourself with the template markup syntax, consult [Imperavi's docs](https://imperavi.com/redactor/legacy/revolvapp/docs/syntax/quick-start).
26
+
The email editor uses the [Revolvapp](https://imperavi.com/legacy/revolvapp/) email template editor plugin by Imperavi. To acquaint yourself with the template markup syntax, consult [Imperavi's docs](https://imperavi.com/legacy/revolvapp/docs/syntax/quick-start).
27
27
28
28
As you will see, the template markup is an HTML-like language and each type of node supports its own set of attributes which control its behavior. A lot of the attributes are borrowed from HTML itself.
Copy file name to clipboardExpand all lines: docs/components/organization/organization-profile.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: '`<OrganizationProfile />` component'
3
-
description: Clerks <OrganizationProfile /> component is used to render a beautiful, full-featured organization management UI that allows users to manage their organization profile and security settings.
3
+
description: Clerk's <OrganizationProfile /> component is used to render a beautiful, full-featured organization management UI that allows users to manage their organization profile and security settings.
4
4
---
5
5
6
6

If set to `true`, all default properties will be used. Otherwise, accepts an object with an optional `role` property of type [`OrganizationCustomRoleKey[]`](#organization-custome-role-key) and any of the properties described in [Shared properties](#shared-properties).
30
+
If set to `true`, all default properties will be used. Otherwise, accepts an object with an optional `role` property of type [`OrganizationCustomRoleKey[]`](#organization-custom-role-key) and any of the properties described in [Shared properties](#shared-properties).
Copy file name to clipboardExpand all lines: docs/users/invitations.mdx
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ You can create an invitation in the [Clerk Dashboard](#using-clerk-dashboard) or
21
21
To invite users, navigate to the **Users** page from the top-level menu, then select the **Invitations** tab. Select **Invite user** and enter the email address of the person you want to invite. Optionally, set an expiration date for the invitation. Once you've entered the necessary details, select **Send invite** to send the invitation email.
22
22
23
23
> [!TIP]
24
-
> The same page will be available throught the top-level menu, when you are in the **Restricted** sign-up mode.
24
+
> The same page will be available through the top-level menu, when you are in the **Restricted** sign-up mode.
25
25
26
26
### Using Backend API
27
27
@@ -95,7 +95,7 @@ You can revoke an invitation at any time. Revoking an invitation prevents the us
95
95
To revoke an invitation, navigate to the **Users** page from the top-level menu, then select the **Invitations** tab. Find the invitation you want to revoke and select **Revoke** from the dropdown menu on the right.
96
96
97
97
> [!TIP]
98
-
> The same page will be available throught the top-level menu, when you are in the **Restricted** sign-up mode.
98
+
> The same page will be available through the top-level menu, when you are in the **Restricted** sign-up mode.
Copy file name to clipboardExpand all lines: docs/webhooks/debug-your-webhooks.mdx
+7-9Lines changed: 7 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,11 @@ Developing with webhooks can be a new experience for developers. It can be hard
9
9
10
10
When you or a user of your application performs certain actions, a webhook can be triggered. You can see the full list of [webhook events](/docs/webhooks/overview#supported-webhook-events) for a list of the actions that could result in a Webhook. Depending on the events subscribed to in the [**Webhooks**](https://dashboard.clerk.com/last-active?path=webhooks) page in the Clerk Dashboard, a webhook event will be triggered and sent to the specified endpoint in your application.
11
11
12
-
When you are developing on your localhost, your application is not internet facing and can't receive the webhook request. You will need to use a tool that creates a tunnel from the internet to your localhost. These tools will provide temporary or permanent URLs depending on the tool and the plan you subscribe to. Popular tools include `ngrok`, `localtunnel` and `Cloudflare Tunnel`.
12
+
When you are developing on your localhost, your application is not internet facing and can't receive the webhook request. You will need to use a tool that creates a tunnel from the internet to your localhost. These tools will provide temporary or permanent URLs depending on the tool and the plan you subscribe to. Popular tools include `ngrok`, `localtunnel`, and `Cloudflare Tunnel`.
13
13
14
14

15
15
16
-
This guide will address common issues that arise when developing with webhooks and how to debug them.
16
+
Debugging webhook-related issues can be tricky, so the following sections address common issues and how to resolve them.
17
17
18
18
## Check your Middleware configuration
19
19
@@ -39,11 +39,9 @@ export const config = {
39
39
40
40
## Test the Route Handler or API Route
41
41
42
-
If you are having trouble with your webhook, you can create a basic Route Handler and then test it locally. First, add the following file and code to your app.
42
+
If you are having trouble with your webhook, you can create a basic Route Handler to test it locally.
43
43
44
-
If you're having trouble with your webhook, you can create a basic response and then test it locally.
45
-
46
-
1. Create a test route in your application:
44
+
1. Create a test route by adding the following file and code to your application:
@@ -52,7 +50,7 @@ If you're having trouble with your webhook, you can create a basic response and
52
50
```
53
51
</CodeBlockTabs>
54
52
1. Run your application.
55
-
1.Run the following command to send a request to the test route:
53
+
1.Send a request to the test route using the following command:
56
54
```bash
57
55
curl -H 'Content-Type: application/json' \
58
56
-X POST http://localhost:3000/api/webhooks/test
@@ -94,7 +92,7 @@ The following table has some of the common response codes you might see and what
94
92
95
93
## Debug webhook verification
96
94
97
-
To verify the webhook, see the [guide on webhooks](/docs/webhooks/sync-data#create-the-endpoint-in-your-application) for a detailed code example. You can also visit the [Svix guide on verifying payloads](https://docs.svix.com/receiving/verifying-payloads/how).
95
+
To verify the webhook, see the [guide on webhooks](/docs/webhooks/sync-data#create-the-endpoint) for a detailed code example. You can also visit the [Svix guide on verifying payloads](https://docs.svix.com/receiving/verifying-payloads/how).
98
96
99
97
Diagnosing a problem in this part of the webhook can be challenging. Your best bet would be the liberal use of `console.log`. You could log out the following to check if the values are correct:
100
98
@@ -109,6 +107,6 @@ Checking the values and the progress of the webhook code will allow you to narro
109
107
110
108
## Check your logic
111
109
112
-
Once you have verified the webhook, you will now be writing your own code to handle the values from the webhook. This could range from saving data to a databse, or integrating with another system, to updating users or sending emails or SMS.
110
+
Once you have verified the webhook, you will now be writing your own code to handle the values from the webhook. This could range from saving data to a database, or integrating with another system, to updating users or sending emails or SMS.
113
111
114
112
If the webhook is verified and you're seeing a `500` status code or your webhook is not behaving as expected, remember that you can use `console.log` to help diagnose what the problem is. Console logs and errors will be displayed on your command line, allowing you to see what's happening and address the bugs.
0 commit comments