- Price: 20 USD lifetime license
- Bundled translations: English
- Flarum compatibility: 1.2+
- See and purchase on Extiverse
- See on Flarum Discuss
Table of content:
Rich Embeds is a Flarum extension that adds previews to links posted in discussions. The previews are generated from OpenGraph data or an optional fallback method.
The data crawling is performed by the Flarum server without any external service and is cached for fast retrieval and minimal impact on page load times.
Images and favicons can optionally be proxied through the server to protect the visitor’s privacy.
A whitelist or blacklist of websites can be configured to control which websites are previewed and prevent abuse of the proxy script.
- Fixed image proxy toggle not being applied.
Rich Embeds overrides the TextFormatter
URL rendering template and as such may conflict with other extensions.
This page will be kept up to date with any known incompatibility that can’t be worked around.
- Purchase the “KILOWHAT Rich Embeds” extension via the Extiverse website
- If this is your first premium extension purchase from Extiverse, follow the “Composer configuration” instructions available at https://extiverse.com/premium/subscriptions
- Install the extension via Composer:
composer require kilowhat/flarum-ext-rich-embeds
- Open the Flarum admin panel and enable the extension
- See below for the settings
You can use the following commands to update:
composer require kilowhat/flarum-ext-rich-embeds php flarum migrate php flarum cache:clear
If you are having issues with the extension, check the following:
- If the extension doesn’t install, check you have correctly configured Extiverse’s private repository.
- If an error happens during activation or usage of the extension, check the logs in
If you are still having issues, please copy the output of the logs above, as well as the output of
php flarum info and send an email to [email protected].
Support is provided on a “best effort” basis. Most replies should usually be within 24h.
I only provide help solving specific issues with the extension. I won’t install the extension for you.
You can disable all embeds on a specific post.
Users with the required permission will see a button appear when they hover any embeds on a post. After accepting the confirmation modal that appears, all embeds will be detached from that specific post.
There is currently no way to re-enable the embeds on a post that has been disabled. An option will be added in a future update.
In the meantime if you must re-enable embeds on the post, you can edit the
kilowhat_rich_embeds_disable column on the
posts table in the database manually.
Users with the matching permissions are allowed to request an update of the crawled data for an embed.
Please be careful with this permission as there is currently no rate limiting that controls how often you can request new previews.
When an identical link is posted again in a new post, a refresh is not automatically requested (the existing cached data is always used). Only users with the permission can manually request a refresh for a URL.
This extension includes a custom parser that follows the OGP specification.
A “fallback” parser takes care of retrieving the favicon as well as optional fallback values in case OpenGraph data is missing. See documentation on the corresponding setting.
You can control which websites can be embedded in posts through a blacklist and/or whitelist. See documentation on the whitelist setting.
Admins and moderators are subject to the same rules as regular users and can’t add previews to websites that are not whitelisted.
Existing previews that were generated before a setting change will not be deleted.
A future update will add a way to generate previews for all existing posts in the database.
In the meantime, you need to edit at least one character in a post and save it to have the previews generated.
All settings can be found in the extension page of the admin panel.
Controls the positioning of the link preview around the original link:
- Inline: replaces the link text with the crawled page title and adds the favicon in front of the text. Hovering the link reveals the preview block.
- Block (default): replaces the link with the full preview block.
- Separated: the post content is not altered. Preview blocks are added below the post content.
Inline is automatically used for links without OpenGraph data, links where OpenGraph parsing failed, and links with custom labels.
Separated mode currently doesn’t auto-updates during post editing. It updates after the post has been saved.
Controls the look of the block preview:
- Vertical (default): The images are placed under the text content and takes the full width of the block.
- Horizontal: The images are placed to the right of the text content.
Proxies all images and favicons through Flarum’s server.
The origin server will only see the “Guzzle” user agent (the library used internally for requests) and the server IP.
Flarum will only perform the proxy request if the image URL is whitelisted, and will only return the response if the returned
Content-Type starts with
When this option is enabled, a fallback preview will be generated from the page’s
<img> tags in the page body.
These previews might not look as good as OpenGraph previews because the data crawled this way might not have been intended to be displayed in a preview.
These 2 settings control which URLs will have previews generated as well as the URLs that can be sent through the image proxy.
Each entry in the lists should be separated by a newline.
Each entry can be either a domain name or a regular expression.
A domain should contain only the host part of a URL without any protocol or path, for example
github.com. Subdomains of the given domain will automatically be accepted as well.
Regular expressions should include delimiters and modifiers. The accepted delimiters are
~. Make sure to include the
i modifier for case-insensitive matching. The expression will be evaluated against the raw URL typed by the user with
All URLs are already validated with PHP’s
FILTER_VALIDATE_URL and TextFormatter’s
#url filter so you don’t need to repeat any such validation in your regex.
Don’t forget to whitelist the domain names of any CDN server used by your whitelisted website’s OpenGraph images.
The extension will automatically blacklist all URLs that include private range IPs, unless you explicitly whitelist them. Consider blacklisting your internal domain names if the server is not isolated.
Use embeds in own post: controls which users can use embeds in their posts. When a post is edited, it’s the author of the post that is evaluated. If the author of a post was deleted, editing the post will cause all embeds to be removed.
Disable embeds on own post: controls which users can remove embeds on posts they have authored. This option appears after the post has been successfully created.
Disable embeds on any post: moderation equivalent of the Disable embeds on own post permission.
Refresh embeds on any post: gives access to the button to refresh an existing embed.