Premium WordPress Integration

EvelinaAdamovi

[deleted] It was just ironic / sarcasm.

clarkwinkelmann

EvelinaAdamovi I think it's better when the user post a comment and only then on Flarum will be created new topic

Theoratically this could be done, but for UX and technical reasons I mentioned in clarkwinkelmann I have decided to not implement that solution.

For now, all Wordpress posts that you want users to be able to comment on must have an existing Flarum discussion. As discussed above I will add a tool that lets you import old posts into the commenting system now that I see there is demand for it. It should be ready within a week.

EvelinaAdamovi And I believe that on some sites there may be even more posts, 5000-1000, etc. And for each of them to do a new discussion thread in Flarum? Hmmm....

I don't think this would be too much of an issue. Performance-wise, Flarum will have no issues. The only difficulty might be moderation. Without an extension that auto-locks old topics, you will have a lot of topics to moderate, but that's probably expected if you willingly enable commenting on all those old discussions.

I will try to provide a "date" option in the import so you can choose how far back you want to create discussions. And if that's not too complicated, I will also add an option so existing Wordpress comments can be imported into Flarum.

[deleted]

clarkwinkelmann I will also add an option so existing Wordpress comments can be imported into Flarum.

A way to export comment made in Flarum back into WordPress would also be beneficial. Currently, if you disconnect Flarum from WordPress, you'd lose every single comment created via Flarum. That in itself creates quite a lock-in for this extension making the decision to no longer use if difficult if you want to keep your comments.

[deleted]

I've had to reinstall my server today thanks to another issue, and now, I am seeing all sorts of issues with this extension - to the point where I cannot get it to work. I get

{"success":false,"data":[{"code":"http_request_failed","message":"cURL error 60: SSL certificate problem: unable to get local issuer certificate"}]}

It's 100% caused by the extension or the WordPress plugin - I have disabled the WordPress extension and now no longer get the error above. This concerns me a great deal. I have over 1,000 posts on my site which rely on this plugin and extension to function correctly, and now the integration in terms of SSO and comments etc no longer works.

My concern is that there may be a bug here - I removed the extension, uninstalled, etc, but on enabling again, still no joy.

clarkwinkelmann

[deleted] is this error visible in Wordpress or in the Flarum log files ?

Most likely the certificates used by your PHP are not the most up to date, and it can't validate the certificate of the other website. Both Wordpress and Flarum rely on making HTTPS request to the other site. If you search for that error message along with the name of your webserver and operating system you should find instructions to update it.

If both were previously installed on different servers and are now on the same server, it's also possible a different self-signed certificate is being served by your server for requests originating from localhost. This can be checked by making a curl call to the HTTPS url from the server SSH shell, there is a way to inspect the returned certificate that way.

In any case it does not look like an issue with the extension code itself, it seems like an issue with the local certificates used by PHP or the certificate served by your server.

benjaminschultz

Hey everyone - I've been on a journey to get this working on my site over the weekend. For anyone having these problems in the future, here's what I've had to do so far:

Move my flarum site from a separate domain to a subdomain of my wordpress domain because it seems in 2020 there is almost literally no way to share cookies between domains (this is a shame because with the prevalence of the new TLDs, I expect many sites will want to adopt something like "example.community" as their forum address). As an interesting note, stack exchange seems to have figured this out, but it does not appear to have been an easy process and they're not sharing the exact details.
I had the exact same problem as troymccann (and troymccann ) of getting the error "We could not authenticate with the given credentials. Double-check the URL, username and password." I spoke with SiteGround at some length and they could not figure out why I got a 401 error when trying to use the api token. Finally, while troubleshooting, I installed "miniOrange API Authentication" which gave a more verbose error. In their documentation they recommend the following specific instructions which fixed my problem (I had tried something similar before but I must not have put the code in just the right spot in .htaccess)

This error may occur because of server environment,If Apache server then put the below line in your htaccess file after the RewriteBase.

RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]

If NGINX server then put the below line in your conf file.

add_header Access-Control-Allow-Headers "Authorization";

Finally, I can connect and get a "Health check good", now though I'm having the error upon user login: {"success":false,"data":[{"code":"http_request_failed","message":"cURL error 60: SSL certificate problem: unable to get local issuer certificate"}]} which was shared by [deleted]

[deleted] says it turned out to be a caching problem but I have cleared by siteground and cloudflare caches and confirmed the two sites are using the same SSL certificate from cloudflare. (According to chrome, at least)

What's my next troubleshooting step?

[deleted]

clarkwinkelmann is this error visible in Wordpress or in the Flarum log files ?

In WordPress, and prevents login

clarkwinkelmann Both Wordpress and Flarum rely on making HTTPS request to the other site. If you search for that error message along with the name of your webserver and operating system you should find instructions to update it.

They are both using the same certificate - it's a wildcard

clarkwinkelmann If both were previously installed on different servers and are now on the same server, it's also possible a different self-signed certificate is being served by your server for requests originating from localhost.

They were always on the same server

clarkwinkelmann In any case it does not look like an issue with the extension code itself, it seems like an issue with the local certificates used by PHP or the certificate served by your server.

The certificate is valid, because WordPress has no issues with it

clarkwinkelmann

[deleted] the Wordpress plugin uses the built-in Wp_Http classes so any certificate error must be related to the Wordpress or webserver configuration.

Searching for the error I see various threads of people fixing it via either updating their CABUNDLE or adding flags to the Wordpress config to disable certificate validation (I don't recommend that last option).

What CA issued your certificate ? Is it Cloudflare, Let'sEncrypt, other ? If it's let's encrypt they have "recently" moved to their own CA so some operating systems might not ship with compatible CABUNDLE files by default.

Another option could also be that maybe your PHP or Curl configuration is not enabling the required cyphers that your webserver accepts.

[deleted]

clarkwinkelmann Well, I have other more severe issues which I can't explain. Even when running php flarum info I get

Stack trace:
#0 /var/www/vhosts/phenomlab.com/forum.phenomlab.com/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(27): PDO->__construct('mysql:host=loca...', 'community', '...', Array)
#1 /var/www/vhosts/phenomlab.com/forum.phenomlab.com/vendor/illuminate/database/Connectors/Connector.php(67): Doctrine\DBAL\Driver\PDOConnection->__construct('mysql:host=loca...', 'community', '..', Array)
#2 /var/www/vhosts/phenomlab.com/forum.phenomlab.com/vendor/illuminate/database/Connectors/Connector.php(46): Illuminate\Database\Connectors\Connector->createPdoConnection('mysql:host=loca...', 'community', '..', Array)
#3 /var/www/vhosts/phenomlab.com/forum.phenomlab.com/vendor/illuminate/database/Connectors/MySqlConnector.php(24): Illuminate\Database\Connectors\Connector->createConnection('mysql:host in /var/www/vhosts/phenomlab.com/forum.phenomlab.com/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php on line 31

Yet the website itself works fine ??

[deleted]

clarkwinkelmann What CA issued your certificate ? Is it Cloudflare, Let'sEncrypt, other ?

The certificate is issued by IONOS and worked fine before. I've even revoked this and reissued with the same result. If I look at the cert chain, it's also fine.

Hmmm - WAIT.... looks like a cache issue, as the cert chain fails when tested, so I've fixed that. Extension now works correctly.

clarkwinkelmann

Not a joke, there is an update today !

This is a double update. You will need to update both the Wordpress plugin and Flarum extension to use the new features.

The boring changelog is below. First, some screenshots:

New dashboard

Same settings, new look. Now in a dedicated page and with tabs for each integration.

Health check

Every time you open the dashboard, a health check runs. It should catch the most common configuration errors.

Installation wizard

For new users that have not yet connected Wordpress and Flarum, there is a new screen in Flarum which will take care of it.

The only things left to configure in Wordpress afterwards is to manually enable the integrations you want. But I also plan to synchronise those settings in a future version so that you don't need to edit anything from inside the Wordpress admin.

You still need to first install and enable the Wordpress plugin.

Full changelog

I've put April 2 to make it extra clear it's not a joke. But it's also really the 2nd of April where I live at the time this post goes live.

Flarum extension version 1.3.0 - April 2, 2020

New admin dashboard for Wordpress
Added Installation wizard
Added Health check
Added "Use post date" option for the comments integration
Tags for the "Tag for new comment threads" option can now be selected from a dropdown
Fix for user tokens that would end up in the log file

You can update the Flarum extension via Bazaar or Composer.
Requires version 1.2 or greater of the Wordpress plugin.

Wordpress plugin version 1.2.0 - April 2, 2020

Added Wizard and Health check features
Added "Use post date" option
Stop pinging Flarum API about post types that are not synchronized
Fix posts not being synced when they are created and published at the same time. This was causing issues with plugins that auto-publish posts from feeds

The plugin must be manually updated.
The new version can be downloaded via this link.
Works with any version of the Flarum extension.

The import features are coming in a future update.

[deleted]

clarkwinkelmann unless I'm imagining things, the download link points to 127.0.01 ?

jordanjay29

clarkwinkelmann Not a joke, there is an update today !

[deleted] the download link points to 127.0.01 ?

🤔

danielunited

clarkwinkelmann 🤯 Looks absolutely amazing!

clarkwinkelmann

[deleted] jordanjay29 fixed. Sorry about that.

That was a multi-layer fail. Last time I copied the relative link which obviously didn't work when pasted here. So this time I remembered to copy the fully qualified link. But I went and copied it from the locally running Jekyll website while thinking I was on the next tab that had the live website 🙈

If a link doesn't work here, you can always visit the documentation page. I always double-check the links there before copying the content here. The fails are usually during that last copy-pasting.

hrvoje_hr

The new UI really looks beautiful 😍

Hoping for the different wp categories <-> Flarum tags option in the next release.

clarkwinkelmann

[deleted] danielunited I didn't test that properly apparently. I relased a fix:

Version 1.3.1 - April 2, 2020

Fix Wordpress URL HTTPS health check

You can update the Flarum extension via Bazaar or Composer.
Requires version 1.2 or greater of the Wordpress plugin.

hrvoje_hr Hoping for the different wp categories <-> Flarum tags option in the next release.

This will come at some point 😉

danielunited Also the comments on my WordPress posts show an iframe for the first discussion in my community - instead of the relevant associated discussion to the post

This is quite odd. I'm not sure how to troubleshoot that 😬

[deleted]

Amazing, yes - however, mine insists on telling me I need to use https:// whereas I am already !

danielunited

[deleted] Same here. Also the comments on my WordPress posts show an iframe for the first discussion in my community - instead of the relevant associated discussion to the post.

clarkwinkelmann

Just a heads-up, the premium Wordpress integration is incompatible with Flarum Help Tags. If you enable Help Tags, then a logged in user will always see the oldest discussion they authored in the iframe instead of the intended comment thread.

Most likely @askvortsov will be able to fix it. I opened an issue here with the details if anyone is curious askvortsov1/flarum-help-tags1

This is the issue that was affecting danielunited

hrvoje_hr

clarkwinkelmann hrvoje_hr Hoping for the different wp categories <-> Flarum tags option in the next release.

This will come at some point 😉

Any news about this feature?

clarkwinkelmann but the alternative will be a javascript integration, like Disqus.

This would be great. With every visitors spike on my WP we have serious issues with CPU impact.

Generally, yearly plan is a great offer, but before that kind of commitment I would like to know the future plans and roughly timeframes.

clarkwinkelmann

Version 1.3.2 - April 3, 2020

Add session dropdown to iframe and make title translatable

You can update the Flarum extension via Bazaar or Composer.
Requires version 1.2 or greater of the Wordpress plugin.

You can now customize the "Comments" text via Linguist.

[deleted]

@clarkwinkelmann is it possible to use the URL set by the permalink in WordPress for each forum post ? I typically provide direct attribution on imported posts to the original location, but the forum link points to my own site.

« Previous Page Next Page »