Hey,
I had a little problem if I want to use reCaptcha in wordpress when I want to login. This message appear :
{"success":false,"data":[{"code":"http_request_failed","message":"Too many redirects"}]}
Wordpress plugin in use to do this : Advanced noCaptcha & invisible Captcha
And another to customize the login page : GS Custom Login Lite
Maybe it can help. But without the Advanced noCaptch all work fine.
sorry for my bad english :S
Amarok hi! Could you try temporarily disabling the single sign on of this extension by going to Wordpress settings > General > Enable SSO integration and turning it off?
Then you can try connecting again and see whether the error still happens. If it continues to happen, then it's likely not related to my extension. But if it only happens when "Enable SSO integration" is turned on, I'll investigate to see what might be causing the incompatibility.
Unfortunately Wordpress doesn't have a proper log file so I think we have no way to know which URL is being caught in a redirect loop unless looking at the webserver access logs if they exist.
Could you share links to the Wordpress plugins you are using? That way I can test with the exact same plugins on my test website.
clarkwinkelmann Hi.
It's appear it was an Edge Navigator problem... and coockies. Deleted all of them and all work perfectly with SSO turning on.
Sorry for the sorry for the inconvenience :S
Amarok no inconvenience, I'm here to help 
That seemed an odd error to be caused by a specific browser since the error appears to be related to a background request made by the server itself. But glad to hear it's solved!
I am aware of an issue regarding cookies when my extension is used in a cross-origin context. Using the extension in such a context has so far been unsupported (see requirements in documentation), but it was mostly working.
Up until recently, only global login would be unavailable on cross-origin, but connecting and disconnecting from Flarum side would work.
Now with Chrome defaulting cookies to SameSite=Lax, cross-origin iframes can no longer access Flarum session cookies, which means the iframe comments has effectively become read-only and it's impossible to connect or interact with Flarum inside of it.
The upcoming Flarum beta 14 will also mark Flarum cookies explicitely as SameSite=Lax, which means this behavior will be experienced across all browsers.
As I said this should only affect users that were using my extension in an already unsupported manner. But if you are affected and have suggestions regarding the handling of cookies, feedback is welcome.
I could offer an option to force Flarum cookies to use SameSite=None, but that seems counter-productive for security. Especially since my extension still wouldn't fully support global login for such setups.
My recommendation continues to be to only use this extension for contexts where Wordpress and Flarum share a common origin.
@clarkwinkelmann is it safe to upgrade Flarum to 0.14?
hrvoje_hr no, the extension is currently incompatible with Flarum beta 14. The constraints will prevent you from upgrading.
An update was prepared a few weeks ago I just need to test it against the final beta 14 release. It will be released within a week.
Is it able to import existing WordPress comments? I'm thinking about to migrate from existing comments to the plugin one.
codemotion not yet, but this might be coming in a future update.
In the meantime it's still possible to manually import them, but that does require a fair amount of manual work.
Version 1.6.1 contained a bug. 1.6.2 fixes it.
This version can only be installed on Flarum beta 14.
The new version will automatically be installed when you migrate to Flarum beta 14 with Flarum's official instructions.
Requires version 1.4 or greater of the Wordpress plugin.
clarkwinkelmann So now with updated API is a better comment integration in plans?
clarkwinkelmann I'm hoping to offer a javascript embed as well in the future, but no timeline on that.
I'm mostly waiting for beta 14 and the Mithril v2 update as I don't want to take too much time digging into the older Mithril version to see whether a javascript embed would play nice with Wordpress.
BigMinnie I still can't offer any timeline. There are other requested features that I will most likely implement first.
Having studied other comment embed platforms, it seems most of them do use an iframe. They just load it with javascript and have a more polished design that makes it look like the iframe is part of the website. The fully no-iframe implementation will likely be a lot of work and also add some additional constraints on cookies and headers for the host.
I'm still not sure how the current solution impacts your load time? The iframe shouldn't prevent the page from rendering. If there's an actual problem on that side I can add some way of delaying the rendering of the iframe in Wordpress.
clarkwinkelmann They just load it with javascript and have a more polished design that makes it look like the iframe is part of the website.
For the start this could probably work but when I tried the current iframe load times jumped + few seconds, it does not sound a lot but it didn't work for my website.
BigMinnie how do you measure the load time?
If you're using a tool that waits until everything renders including the iframe, it will definitely increase the time. But the iframe loading shouldn't be blocking. The user should see the base page render and it should be interactive before the iframe is ready. And because the iframe is lower in the page the additional load time for the iframe shouldn't very noticeable by the visitor since they can't see the iframe at first anyway.
Loading the iframe with JS could trick an analytics script into thinking the load time is faster. But in practice I don't think it wouldn't change anything for the visitor. But it could have SEO benefits if that value is indeed used to lower your SEO score.
One benefit of JS+iframe is that we can delay the iframe rendering until it gets into view. This can save up on data usage and server load if you've got many page views but not everyone scrolling to the comments, but won't make things any faster for the visitors who actually scroll to the comments (in fact, the opposite, depending on how late we trigger the loading when the user scrolls).
If there's something slowing down the initial page render of Wordpress, I will definitely fix it. Just let me know which tools return bad scores and I will try to optimize based on their suggestions.
clarkwinkelmann Hello, I tried to install your extension after you annonce beta 14 compatibility on my fresh flarum install. But, it apparently can't install on this version
[InvalidArgumentException]
Could not find a matching version of package kilowhat/flarum-ext-wordpress. Check the package spelling, your version constraint and that the package is available in a stability which matches your
minimum-stability (stable).
It's maybe me, but not sure, so is your extension on a fresh Flarum 14 installation compatible or not?
Thx for answer
Best regards
Amarok have you configured your composer.json for Extiverse? The instructions can be found at https://kilowhat.net/flarum/extensions/wordpress#installation Is this your first premium extiverse Extension? The error message looks like what appears when Composer cannot find the package at all, which could mean missing Extiverse repository.
If Composer is correctly configured for Extiverse, you could use the following commands to maybe get more details: composer why-not kilowhat/flarum-ext-wordpress.
clarkwinkelmann it's not the first time I install this and checked with my other installation. It's seems to be a clone (without other extensions)
With the command just have this answer :
[InvalidArgumentException]
Could not find package "kilowhat/flarum-ext-wordpress" in your project
I had cherck many times, and redo all from 0 but.. still same answer when I want to install it :S
so, another question, is it possible to have multi-installation of this extension or not? 
Amarok if you moved hosting or something like that, make sure you re-run the Extiverse commands to re-configure the repository and the access token. If you have multiple forums, make sure you use the same token everywhere, because requesting a new token on Extiverse invalidates the old one. But there should be a different error message if you have an invalid token...
You could try to install a specific version, but I'm not sure whether it would give much more success if the base command doesn't work: composer require kilowhat/flarum-ext-wordpress:^1.6.2
Amarok so, another question, is it possible to have multi-installation of this extension or not
If you are referring to the licensing, you should check Extiverse terms. You are allowed to install on multiple of your own forums but not re-sell or subcontract hosting.
If you are referring to Wordpress multi-site, this has not been tested.
clarkwinkelmann You could try to install a specific version, but I'm not sure whether it would give much more success if the base command doesn't work: composer require kilowhat/flarum-ext-wordpress:1.6.2
I redo again all and checked 2 times
But nothing changed :S
clarkwinkelmann If you are referring to the licensing, you should check Extiverse terms. You are allowed to install on multiple of your own forums but not re-sell or subcontract hosting.
Just installing on different wordpress installation Thx for answered.
sorry for my bad english ^^
