Skip to content

Commit

Permalink
Add a FAQ item for rendering a form
Browse files Browse the repository at this point in the history
  • Loading branch information
zackkatz committed Apr 19, 2024
1 parent 6f880d4 commit fbc67c1
Showing 1 changed file with 19 additions and 1 deletion.
20 changes: 19 additions & 1 deletion docs/Client/dev-faq.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# Developer FAQ

## How do I render the authorization screen? {#how-do-i-render-the-authorization-screen}

You can trigger the `trustedlogin/{namespace}/auth_screen` action to render the authorization screen. The proper JS and CSS files will be enqueued automatically:

```php
<h1>My Plugin</h1>

<p>This is a page inside my plugin.</p>

<?php

// Render the TrustedLogin Grant Support Access screen.
do_action( 'trustedlogin/{namespace}/auth_screen' );
?>

<p>More content here.</p>
```

## What happens if TrustedLogin service is down? {#what-happens-if-trustedlogin-service-is-down}

If the TrustedLogin service is down, the user will be presented with a button to contact support. That button points to the the Support URL (`vendor/support_url`) setting passed to the [`Config` object](configuration/).
Expand All @@ -13,4 +31,4 @@ encryption or when generating the requests to your website.

TrustedLogin requires user action to provide logins. This is in compliance with WordPress.org.

All files (vendor logo, CSS, and JS files) must be local (using `plugin_dir_url()` or similar) to comply with WordPress.org rules.
All files (vendor logo, CSS, and JS files) must be local (using `plugin_dir_url()` or similar) to comply with WordPress.org rules.

0 comments on commit fbc67c1

Please sign in to comment.