WordPress plugin that lets you use Discourse as the community engine for a WordPress blog

Overview

WP Discourse

OpenCollective OpenCollective

Note: the wp-discourse plugin requires >= PHP-5.4.0.

The WP Discourse plugin acts as an interface between your WordPress site and your Discourse community.

The plugin is not a substitute for Disqus-like commenting systems.

Use Discourse for Comments:

  • Automatically creates a forum topic for discussion when a new blog post is published.
  • Associates WP author accounts with their respective Discourse accounts. Does not require DiscourseConnect.
  • Replies from the forum discussion can be embedded in the WP blog post. Select which replies to display based on post score and commenter "trust level" -- see docs.

See it Live

DiscourseConnect

The plugin also comes with optional DiscourseConnect functionality which lets you use your WordPress site as the DiscourseConnect provider for your Discourse forum.

This will override Discourse's native (and powerful) login flow and is only recommended for use cases that strictly require such a setup, e.g. a site that is already using WordPress for large scale user management.

Contact

Installation

From your WordPress dashboard

  1. Visit 'Plugins > Add New'
  2. Search for 'WP Discourse'
  3. Activate WP Discourse from your Plugins page

From wordpress.org

  1. Download WP Discourse
  2. Upload the 'wp-discourse' directory to your '/wp-content/plugins/' directory
  3. Activate WP Discourse from your Plugins page

With Composer

If you're using Composer to manage WordPress, add WP-Discourse to your project's dependencies. Run:

composer require discourse/wp-discourse ~1.3.2

Or manually add it to your composer.json:

=5.4.0", "discourse/wp-discourse": "~1.3.2" } }">
{
  "require": {
    "php": ">=5.4.0",
    "discourse/wp-discourse": "~1.3.2"
  }
}

For more detailed instructions please see the WP Discourse plugin installation and setup.

Frequently Asked Questions

Does this plugin install Discourse for me?

No this plugin acts as an interface between Discourse and WordPress. For it to work you will need to first set up Discourse forum. You can install Discourse for yourself following either of these guides:

Can I import old WordPress comments as Discourse comments (i.e. "replies")?

No.

Do WordPress and Discourse have to be installed on the same server?

The plugin uses the Discourse API, so your forum and blog can be hosted separately and the integration will still work. In fact, we strongly recommend hosting the two applications separately, since their hosting requirements are very different.

Is it possible to customize the comment templates?

Yes, the html templates used for publishing posts on Discourse and for displaying comments on WordPress can be customized in your theme. This is done by hooking into the filters that are applied to each template.

For more details on template customization, see: WP Discourse template customization

Contributing

Before you start contributing or developing this plugin please read the documentation in docs/, starting with contributing.md. If you have any questions about those process, please post in #dev for assistance.

Comments
  • Use Discourse instance as a SSO provider

    Use Discourse instance as a SSO provider

    Implemented the SSO functionality as discussed here.

    What is this?

    As its name states, will allow you to use a Discourse instance as a SSO provider. It works as follow:

    1. If you don't have an account on WP, a new account will be created (although I'm not sure what's happening if you don't have an account on discourse...) and this new account will be linked to your discourse account.
    2. if you do have an account on WP, discourse user will be linked to current user;

    Clearly enough, discourse user info will be used to fill the WP user data, in order to mantain some kind of sync.

    How to use

    You must fill discourse URL & SSO secret, then tick the Enable Discourse SSO & Add "Login with Discourse" on the login form checkboxes.

    This also implements a shortcode and also provides a functions & some hooks that can be used by developers.

    Shortcode can be used either simple : [discourse_sso_client] or with params, to allow customizing default anchor texts:

    [discourse_sso_client login="Login to discourse" link="Link your account to discourse"]
    

    Filters

    apply_filters( 'discourse/sso/client/login_anchor', $anchor, $sso_login_url, $options, $discourse_options );
    

    Allows you to alter default login anchor (i.e. if you want to use the shortcode in multiple place and you don't want to add the attributes every single time).

    $updated_user = apply_filters( 'discourse/sso/client/updated_user', $updated_user, $query );
    

    Allows you to change what data is saved from discourse payload to user meta.

    $redirect_to = apply_filters( 'discourse/sso/client/redirect_after_login', $query['return_sso_url'] );
    

    Allows you to specify a redirect url after successful auth.

    As a developer, you can also use get_discourse_sso_url() to get... well, the sso url.

    Quirks, issues & stuff

    • Discourse doesn't send on SSO payload either an user is blocked or not, hence a blocked user will be able to log in to WP
    opened by iamntz 45
  • Possible bug: using WordPress as SSO provider, logging in redirects to /wp-admin

    Possible bug: using WordPress as SSO provider, logging in redirects to /wp-admin

    I have a Discourse install and a WordPress site, with settings configured such that the WP site is the SSO provider.

    • When clicking "Log In" on the Discourse install, I'm taken to the WordPress /wp-login.php page as expected.
    • After logging in, I'm taken to the WordPress /wp-admin page, instead of to the Discourse install
    • If I then manually visit the Discourse install, I'm not logged in, and clicking "Log In" repeats this process.

    This is with the default twentysixteen theme active, and only the wp-discourse plugin active.

    Any ideas on how to proceed from here?

    Here are screenshots of the settings pages:

    image

    image

    image

    opened by tnorthcutt 22
  • Redirect to woocommerce login

    Redirect to woocommerce login

    First: Thank you very much for this awesome plugin!

    Second: I'd like to expand it: I have a wordpress install, where users login with woocommerce instead the default wp-login page: The login-site is therefore example.com/my-account

    Editing the url to redirect users to example.com/my-account https://github.com/discourse/wp-discourse/blob/master/lib/discourse.php#L153-167

    ...ends up in an endless loop of redirects with an increasing length of the url.

    example.com/my-account/?sso=abc....xyz%0B&sig=abc...xyz example.com/my-account/my-account/?sso=abc....xyz%0B&sig=abc...xyz example.com/my-account/my-account/my-account/?sso=abc....xyz%0B&sig=abc...xyz example.com/my-account/my-account/my-account/my-account/?sso=abc....xyz%0B&sig=abc...xyz ...

    Does anybody have a hint, how to handle this? Any help appreciated!

    Best! Bernd

    opened by bk1285 19
  • expired nonce while trying to link WP account to Discourse

    expired nonce while trying to link WP account to Discourse

    Hi, I installed the wp-discourse plugin and it works ("You are connected to Discourse!").

    I am now trying to configure login to WP with discourse as SSO provider.

    On http://wordpress.example.com/wp-admin/admin.php?page=wp_discourse_options&tab=sso_options I have:

    • Enable SSO Client.
    • Add "Login with Discourse" on the login form
    • SSO Secret Key

    In http://discourse.example.com/t/admin/site_settings/category/login I have:

    • enable sso provider
    • verbose sso logging
    • sso secret

    When I try to log in on WP with the "Login with Discourse", it says "There is already an account registed with the username supplied by Discourse. If this is you, login through WordPress and visit your profile page to sync your account with Discourse"

    But when I log in on WP with my WP account proper, then go to http://wordpress.example.com/wp-admin/profile.php and click on "Link your account to Discourse" it goes to http://wordpress.example.com/?discourse_sso=1&redirect_to=http://calomelano.it/wp-admin/profile.php, that immediately gets rewritten as http://wordpress.example.com/wp-login.php?discourse_sso_error=expired_nonce, bounces back to the WP login form and says "Expired Nonce":

    spectacle j13706

    Inside /var/www/discourse/log/production.log on the discourse docker image I find:

    Started GET "/session/sso_provider?sso=bm...&sig=09..." for w.x.y.z at 2017-03-03 09:58:29 +0000
    Processing by SessionController#sso_provider as HTML
      Parameters: {"sso"=>"bm...", "sig"=>"09a..."}
    Redirected to http://wordpress.example.com/wp-admin/profile.php?sso=bm...&sig=f4f...
    Completed 302 Found in 15ms (ActiveRecord: 5.2ms)
    

    whereas in wordpress.example.com inside the weserver log (/var/log/nginx/access.log) I find:

    w.x.y.z - - [03/Mar/2017:10:58:29 +0100] "GET /?discourse_sso=1&redirect_to=http://wordpress.example.com/wp-admin/profile.php HTTP/1.1" 302 5 "http://wordpress.example.com/wp-admin/profile.php" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36"
    w.x.y.z - - [03/Mar/2017:10:58:29 +0100] "GET /wp-admin/profile.php?sso=bm...&sig=f4... HTTP/1.1" 302 5 "http://wordpress.example.com/wp-admin/profile.php" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36"
    w.x.y.z - - [03/Mar/2017:10:58:29 +0100] "GET /wp-login.php?discourse_sso_error=expired_nonce HTTP/1.1" 200 1590 "http://wordpress.example.com/wp-admin/profile.php" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36"
    

    Any idea ?

    opened by simevo 16
  • FEATURE[WIP]: Improve WooCommerce support

    FEATURE[WIP]: Improve WooCommerce support

    Allows Discourse to be used for WooCommerce product reviews.

    • ~~Adds a 'plugin support' section to the settings page, with an 'Enable WooCommerce Support' setting~~
    • Adds a 'login-path' setting to the settings page SSO section. This makes it possible to override the default WordPress login page. To use the WooCommerce 'my-account' page for login, the login path should be set to '/my-account'
    • Increases the priority of the Discourse comments template so that it will be used in place of the comments template that is set through WooCommerce or other plugins
    • Adds a WoocommerceSupport class that sets the proper redirect from WordPress to Discourse when the WooCommerce /my-account page is used as the login page. ~~It also returns the name of the WooCommerce comments_number_filter, and hooks it into the Discouse::comments_number method.~~

    If the 'login-path' setting is not set, the default WordPress login page wp-login.php will be used. Setting the 'login-path' makes it possible to use any page on the WordPress site as the login page. An example of how to do this can be added to the documentation.

    Does this feature belong in the plugin? Most of these changes could also be made in the theme's functions.php file.

    see: https://github.com/discourse/wp-discourse/issues/173

    https://meta.discourse.org/t/wp-discourse-sso-plugin/23245/40?u=simon_cossar

    opened by scossar 15
  • Publish post to Discourse broken

    Publish post to Discourse broken

    I've been using the wp-discourse plugin for quite some time for SSO and auto-publishing of wordpress posts to the forum.

    Publishing posts somehow stopped working somewhere between version 1.3.2 - 1.3.5. The last post that got published was 20 march so I can't really tell exactly after which wp-discourse upgrade it stopped working.

    SSO works fine, the button shows up:

    publish

    No matter how many times I hit the publish button, it doesn't publish anything. Any idea how to debug or resolve this?

    opened by rmcs2002 14
  • Latest version not published on Packagist

    Latest version not published on Packagist

    Really strange since it's supposed to be automatic, but the latest release (1.5.6) doesn't seem to be published on Packagist...

    Maybe the webhook failed? Thanks a lot! đź‘Ť

    opened by LeoColomb 13
  • comment form on wordpress site ? impossible?

    comment form on wordpress site ? impossible?

    apologies if this is impossible or annoying

    I'd like to be able to display the comment form on wordpress site and then send that comment to discourse api and pre fill the reply field

    I am guessing this is impossible if not logged in already

    and maybe its impossible if you are logged in, although have seen some rest api editors and wonder if that can be used

    opened by niccolox 12
  • Published category being ignored

    Published category being ignored

    Since the change which allows posts to be created in different Discourse categories if they match Wordpress categories, the specified 'Published Category' in the plugin settings is now being ignored.

    All posts are being created under 'Off-Topic' rather than 'Article Discussion'.

    opened by pixeldynamo 12
  • SSO Causing Loss of Access to Backend

    SSO Causing Loss of Access to Backend

    I recently migrated my site from GoDaddy (where this wasn't an issue) to SiteGround. I had my website act as the SSO provider, since I have a paywall.

    Now, I lose access to the back end of my wordpress site due to the plugin. I had to disable the plugin initially to regain access, but found that this doesn't happen when the "Enable SSO Provider" option is disabled (which doesn't meet my needs for how I have site set up).

    I've tested this with multiple browsers and devices. Using the admin login credentials with SSO disabled, I get sent immediately to my back end. With SSO enabled (when the plugin is still active), I get redirected back to the login screen. But, I am logged in and can access protected content as a user browsing the front end, but cannot get to the admin areas. sso error

    opened by tom-nagle 11
  • Feature Request - SSO fills in discourse_username

    Feature Request - SSO fills in discourse_username

    It would be very useful if after a user auth'ed via SSO that their discourse_username field in WordPress got automatically populated. Currently requires a lot of manual labor to update this field on all of our authors (making the "Publishing username" override of individual user less useful).

    I realize this may be difficult due to username on Discourse being editable and therefore resulting in sync issues, but figured it would be worthwhile to at least suggest.

    opened by oburt 11
  • Bump json5 and @wordpress/scripts in /admin/discourse-sidebar

    Bump json5 and @wordpress/scripts in /admin/discourse-sidebar

    Bumps json5 to 2.2.3 and updates ancestor dependency @wordpress/scripts. These dependencies need to be updated together.

    Updates json5 from 1.0.1 to 2.2.3

    Release notes

    Sourced from json5's releases.

    v2.2.3

    v2.2.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    v2.1.0

    • New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

    v2.0.1

    • Fix: The browser builds in the dist directory support ES5. (#182)

    v2.0.0

    • Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

    • New: Support for Unicode 10 has been added.

    • New: The test framework has been migrated from Mocha to Tap.

    • New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

    • Fix: The warning has been made clearer when line and paragraph separators are

    ... (truncated)

    Changelog

    Sourced from json5's changelog.

    v2.2.3 [code, diff]

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1 [code, [diff][d2.1.1]]

    ... (truncated)

    Commits
    • c3a7524 2.2.3
    • 94fd06d docs: update CHANGELOG for v2.2.3
    • 3b8cebf docs(security): use GitHub security advisories
    • f0fd9e1 docs: publish a security policy
    • 6a91a05 docs(template): bug -> bug report
    • 14f8cb1 2.2.2
    • 10cc7ca docs: update CHANGELOG for v2.2.2
    • 7774c10 fix: add proto to objects and arrays
    • edde30a Readme: slight tweak to intro
    • 97286f8 Improve example in readme
    • Additional commits viewable in compare view

    Updates @wordpress/scripts from 14.0.1 to 25.0.0

    Release notes

    Sourced from @​wordpress/scripts's releases.

    14.8.4

    Changelog

    Various

    • Fixes an issue where gutenberg bundled theme.json was not utilized. (46810) This meant that Gutenberg features newer than the WordPress theme.json file were unavailable in 14.8.

    Contributors

    The following contributors merged PRs in this release:

    @​madhusudhand

    14.8.3

    Changelog

    Bug Fixes

    Plugin

    Fixes compatibility with WordPress 6.0.x. This includes the following PRs:

    Broadly, this needed to include the two refactors of the Theme_JSON compatibility files, along with two fixes switching wp_* and gutenberg_* function variants as needed.

    Contributors

    The following contributors were involved with this release:

    @​geriux @​Mamaduka @​oandregal @​noahtallen

    14.8.2

    Changelog

    Bug Fixes

    Block Editor

    • rich-text: Fix bug where bare tag name format types could not be registered. (46798)

    First time contributors

    ... (truncated)

    Changelog

    Sourced from @​wordpress/scripts's changelog.

    25.0.0 (2022-12-14)

    Breaking Changes

    • Updated dependencies to require React 18 (45235)

    24.6.0 (2022-11-16)

    24.5.0 (2022-11-02)

    24.4.0 (2022-10-19)

    24.3.0 (2022-10-05)

    24.2.0 (2022-09-21)

    24.1.0 (2022-09-13)

    New Features

    • Update the default webpack config to allow webp image format (#43880).
    • Update webpack configuration for the build and start commands to automatically copy PHP files listed in the render field of block.json files from the source to the build folder (#43917).

    24.0.0 (2022-08-24)

    Breaking Change

    • Increase the minimum Node.js version to 14 and minimum npm version to 6.14.4 (#43141).
    • The bundled @wordpress/eslint-plugin package got updated to the new major version and the default linting for Jest unit tests is now handled in the default config in this package (#43272).

    Bug Fix

    • Packages: Replace is-plain-obj with is-plain-object (#43511).

    23.7.2 (2022-08-17)

    Bug Fix

    • Jest Preset: Improve is-plain-obj transformation ignore (#43271).

    23.7.1 (2022-08-12)

    Bug Fix

    • Jest Preset: Ignore is-plain-obj transformation (#43179).

    23.6.0 (2022-07-27)

    Bug Fix

    ... (truncated)

    Commits
    • 1eb65aa chore(release): publish
    • bcb7752 Update changelog files
    • b0e6e34 Merge changes published in the Gutenberg plugin "release/14.8" branch
    • 7ac04f4 chore(release): publish
    • 640566e Update changelog files
    • 511f4cc chore(release): publish
    • 76b1b0e Update changelog files
    • a2ff0e6 chore(release): publish
    • 52149f9 Update changelog files
    • 433be2b Merge changes published in the Gutenberg plugin "release/14.4" branch
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by gutenbergplugin, a new releaser for @​wordpress/scripts since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • DiscourseUtilities::add_user_to_discourse_group() duplicate call necessary

    DiscourseUtilities::add_user_to_discourse_group() duplicate call necessary

    DiscourseUtilities::add_user_to_discourse_group() call adds the user to Discourse but not into group, a second identical call will do the group addition.

    Has anyone else experienced this?

    opened by paulkirspuu 1
  • Bump json-schema and jsprim in /admin/discourse-sidebar

    Bump json-schema and jsprim in /admin/discourse-sidebar

    Bumps json-schema and jsprim. These dependencies needed to be updated together. Updates json-schema from 0.2.3 to 0.4.0

    Commits
    • f6f6a3b Use a little more robust method of checking instances
    • ef60987 Update version
    • b62f1da Protect against constructor modification, #84
    • fb427cd Link to json-schema-org repository in addition to site, fixes #54
    • 22f1461 Don't allow proto property to be used for schema default/coerce, fixes #84
    • c52a27c Get basic test to pass
    • b3f42b3 Add security policy
    • 3b0cec3 Update version
    • c28470f Update readme to acknowledge the state of the package
    • 7dff9cd Merge pull request #81 from hodovani/patch-1
    • Additional commits viewable in compare view

    Updates jsprim from 1.4.1 to 1.4.2

    Changelog

    Sourced from jsprim's changelog.

    v1.4.2 (2021-11-29)

    • #35 Backport json-schema 0.4.0 to version 1.4.x
    Commits
    Maintainer changes

    This version was pushed to npm by bahamat, a new releaser for jsprim since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Add missing initialisation of optional parameter

    Add missing initialisation of optional parameter

    Before $comment_type was a required parameter following an optional parameter and this results in: Deprecated: Required parameter $comment_type follows optional parameter $perform_sync in [redacted]/wp-content/plugins/wp-discourse/lib/utilities.php on line 338 This then completely breaks login on our Wordpress instance. Adding = null seems to fix the problem.

    opened by drt24 1
  • Bump trim and @wordpress/scripts in /admin/discourse-sidebar

    Bump trim and @wordpress/scripts in /admin/discourse-sidebar

    Bumps trim and @wordpress/scripts. These dependencies needed to be updated together. Removes trim Updates @wordpress/scripts from 14.0.1 to 24.1.0

    Release notes

    Sourced from @​wordpress/scripts's releases.

    14.1.1

    Changelog

    Bug Fixes

    • Blocks: Fix searching of blocks when description is non-string. (44233) Resolves an editor crash which could happen when searching for blocks.

    First time contributors

    The following PRs were merged by first time contributors:

    Contributors

    The following contributors merged PRs in this release:

    @​tyxla

    14.1.0

    Changelog

    Features

    Block Library

    • Add select icon for Navigation Block's menu button. (43674)

    Full Site Editing

    • Add a zoomed out view to the site editor. (41156)

    Enhancements

    Design Tools support in Blocks

    • Archives: Add typography support. (43935)
    • Avatar: Add padding support. (43519)
    • Buttons: Add typography supports to button/s blocks. (43934)
    • Calendar: Add typography supports (except text-decoration). (43969)
    • Categories List: Add spacing support. (43647)
    • Comment Date: Add spacing support. (43656)
    • Comment Edit Link: Add spacing support. (43657)
    • Comment Reply Link: Add spacing support. (43658)
    • Gallery: Add padding and margin support. (43965)
    • Heading: Add missing typography support. (44003)
    • Home Link: Add typography support. (43307)
    • Latest Posts: Add typography supports. (43540)
    • List: Add missing typography block supports. (43311)

    ... (truncated)

    Changelog

    Sourced from @​wordpress/scripts's changelog.

    24.1.0 (2022-09-13)

    New Features

    • Update the default webpack config to allow webp image format (#43880).
    • Update webpack configuration for the build and start commands to automatically copy PHP files listed in the render field of block.json files from the source to the build folder (#43917).

    24.0.0 (2022-08-24)

    Breaking Change

    • Increase the minimum Node.js version to 14 and minimum npm version to 6.14.4 (#43141).
    • The bundled @wordpress/eslint-plugin package got updated to the new major version and the default linting for Jest unit tests is now handled in the default config in this package (#43272).

    Bug Fix

    • Packages: Replace is-plain-obj with is-plain-object (#43511).

    23.7.2 (2022-08-17)

    Bug Fix

    • Jest Preset: Improve is-plain-obj transformation ignore (#43271).

    23.7.1 (2022-08-12)

    Bug Fix

    • Jest Preset: Ignore is-plain-obj transformation (#43179).

    23.6.0 (2022-07-27)

    Bug Fix

    • Fix the incorrect exit error code when status missing in webpack call for build and start commands (#42396).

    23.3.0 (2022-06-15)

    Enhancements

    • The bundled wp-prettier dependency has been upgraded from 2.2.1 to 2.6.2 (#40542).

    23.2.0 (2022-06-01)

    Bug Fix

    • Fix incorrect handling in plugin-zip for root-level files and some specific platform conditions (#41439).

    23.1.0 (2022-05-18)

    ... (truncated)

    Commits
    • 0d732d4 chore(release): publish
    • 2a96ed3 Update changelog files
    • 7ef0628 Merge changes published in the Gutenberg plugin "release/14.1" branch
    • 171b87c chore(release): publish
    • b820929 Update changelog files
    • 4bc7458 Merge changes published in the Gutenberg plugin "release/14.0" branch
    • b5b9cf3 chore(release): publish
    • be84548 Update changelog files
    • 31244eb Jest Preset: Improve is-plain-obj transformation ignore (#43271)
    • e79de3d chore(release): publish
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by gutenbergplugin, a new releaser for @​wordpress/scripts since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 5
  • Compatibility issue with S3 Uploads plugin

    Compatibility issue with S3 Uploads plugin

    When installed in conjunction with S3 Uploads, enabling Discourse logging causes an error because the handler that validates the log file size unnecessarily opens in read-write mode, which the S3 API doesn't support.

    opened by Genyus 0
Releases(0.7.0)
  • 0.7.0(May 18, 2016)

    • Move templates out of options (#194)
    • Validate settings (#189)
    • Add notices to indicate connection status (#193)
    • Sanitize admin options page (#196)
    • Sanitize comment template output (#195)
    • Add type argument to text input method (#192)
    • Use cached categories when there is a configuration error (#191)
    • Fix name property not available in participants array (#187)
    • Use wp_get_current_user (#185)
    • Fix add_query_arg undefined offset notice (#184)
    • Update Discourse post on WP post update (#176)
    • Better method for including comments script and other small tweaks (#181)
    • Allow choosing Discourse category per post (#177)
    • Replace avatar URL function (#172)
    • Fix timezone for custom timestamp (#162)
    Source code(tar.gz)
    Source code(zip)
  • 0.6.6(Jul 31, 2015)

    • Add custom datetime format string to admin settings (#160)
    • Add a log entry when HTTP request fails (#159)
    • Log out of WordPress when logging out of Discourse (#158)
    • Fix security issue, add missing esc_url_raw() (#157)
    • Fix SSO login (#156)
    • Use wp_remote_get instead of file_get_contents (#155)
    • Fix user mention links (8b6fe46)
    • Allow showing existing WP comments under Discourse (#137)
    • Add <time> to allowed tags (#135)
    • Don't do a replace if already an absolute URL (#131)
    Source code(tar.gz)
    Source code(zip)
  • 0.6.5(Feb 28, 2015)

  • 0.6.4(Feb 25, 2015)

    • Minor re-organization of the settings page
    • Fetch categories from remote
    • Add fixes for allowed post types
    • Fix asset URLs on synced Discourse comments
    Source code(tar.gz)
    Source code(zip)
  • 0.6.3(Jan 31, 2015)

    • Add CHANGELOG
    • Move comments template into new folder
    • Move SSO and admin functions into separate files
    • Switch from register_uninstall_hook to uninstall.php
    • Move JS from separate file to inline
    • Remove unnecessary stylesheet
    Source code(tar.gz)
    Source code(zip)
Owner
Discourse
The 100% open source discussion platform built for the next decade of the Internet.
Discourse
Minimalist Forum and Community WordPress Theme ❤

SiForum a WordPress Forum Theme Minimalist Forum and Community Theme made with WordPress and BuddyPress Inspired from Discourse, Flarum and NodeBB. Bu

sinanisler 22 Oct 7, 2022
This WordPress Plugin Boilerplate is meant for you to develop your own plugin on.

WordPress Plugin Boilerplate This plugin boilerplate is meant for you to develop your own plugin on. Support & collaboration Features OOP plugin core

richardev 2 May 10, 2022
The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone.

Pronamic WordPress Basecone The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone. Table of contents Au

Pronamic 1 Oct 19, 2021
Create WordPress themes with beautiful OOP code and the Twig Template Engine

By Jared Novack (@jarednova), Lukas Gächter (@lgaechter), Pascal Knecht (@pascalknecht), Maciej Palmowski (@palmiak_fp), Coby Tamayo (@cobytamayo), Up

Timber 5.2k Jan 5, 2023
Classy is a framework for building WordPress themes, based on Blade template engine

Classy is a framework for building WordPress themes, based on Blade template engine. It's fast with beautiful architecture that allows you to write le

DigitalKwarts 75 Nov 23, 2022
Brings Laravel's great template engine, Blade, to WordPress

###This plugin is deprecated in favor of ekandreas/bladerunner WordPress Blade Brings Laravel's great template engine, Blade, to WordPress. Just insta

Mikael Mattsson 150 Nov 29, 2022
Automattic 10.7k Jan 2, 2023
WordPress plugin people can use to embed to their website: a Mintbase NEAR NFT and Mintbase NEAR store

mintbase-embed WordPress plugin people can use to embed to their website: a Mintbase NEAR NFT and Mintbase NEAR store This is demo plugin that allows

null 3 Oct 1, 2021
Beauty and simple Wordpress video player plugin. Powerfull and lite in use.

Sonic Spectre Video Player Beauty and simple Wordpress video player plugin. Powerfull and lite in use. Quick Start: Download plugin from this repo and

Halcyon 1 Jan 4, 2022
A WordPress plugin to re-use the same domain name for both your website and your Rebrandly links

By installing this plugin and configuring it to connect with your Rebrandly account, you will be able to create branded links using the same domain yo

null 3 Jan 19, 2022
This Plugin is used to install and activate multiple plugins in one go. I was facing problem uploading plugins one by one so I developed this to solve my problem. Hope you will enjoy using this plugin.

=== Bulk Plugin Installer === Contributors: jawadarshad Donate link: https://jawadarshad.io/ Tags: bulk plugin installer, import multiple plugins, up

Muhammad Jawad Arshad 2 Sep 20, 2022
WPCloudDeploy is a WordPress plugin that allows you to easily deploy servers at major cloud-server providers and then install apps

WPCloudDeploy is a WordPress plugin that allows you to easily deploy servers at major cloud-server providers and then install apps

WPCloudDeploy 41 Dec 24, 2022
EzPz Tweaks is an all-in-one WordPress plugin that helps you personalize the admin panel appearances

EzPz Tweaks is an all-in-one WordPress plugin that helps you personalize the admin panel appearances, clean your site code and remove unwanted features to increase its security and improve performance.

WP EzPz 7 Jul 24, 2022
A Wordpress plugin that allows you to customize a news feed on your home page

=== Plugin Name === Contributors: Noora Chahine Requires at least: 4.0.1 Tested up to: 5.4 Stable tag: 5.2 License: GPLv2 or later License URI: http:/

Noora Chahine 1 Nov 15, 2021
A simple platform information plugin for WordPress. Shows you environment variables, PHP settings and more.

A simple platform information plugin for WordPress. Shows you environment variables, PHP settings and more.

New To Vaux 2 Sep 7, 2022
A WordPress plugin to suspend WordPress sites automagically. Simple and lightweight, no annoying ads and fancy settings.

Suspend WP A WordPress plugin to suspend WordPress sites automagically. Simple and lightweight, no annoying ads and fancy settings. ?? Demo (coming so

Waren Gonzaga 3 Nov 15, 2021
Simple WordPress plugin to learn how to understand WordPress Crons and the Action Scheduler library.

Simple WordPress plugin to learn how to understand WordPress Crons and the Action Scheduler library. Import Jamendo playlists with tracks in WordPress posts.

Pierre Saikali 3 Dec 7, 2022
The easiest to use WordPress option framework.

Titan Framework The easiest to use WordPress options framework. Titan Framework allows theme and plugin developers to create admin pages, options, met

Gambit Technologies 374 Nov 14, 2022
A library to allow the use of PHP attributes for WordPress hooks

WordPress Hook Attributes This library should be considered experimental and not production ready. Installation composer require boxuk/wp-hook-attribu

Box UK 9 Nov 23, 2022