Premium WordPress Integration

JohnP

clarkwinkelmann I am working on an improved embed, but I'm still testing what works and what doesn't. Flarum's infinite scrolling makes it hard to design the iframe in a way that doesn't look like a box.

We've actually just got rid of any borders and made the iframe scrollbar fit with the site design and it already looks quite a lot less boxy...

JamminMB

Hi @clarkwinkelmann - I'm having some problems on my site with the Flarum iFrame comments box not displaying correctly.
I've tried disabling a few extensions to see if one of them was causing conflict but no luck.

Edit: Here's a link to a WordPress post if it helps... https://dronesumo.com/meekaah-real-life-vs-uncrashed-sim-fpv-freestyle-blend/

Second edit: There only seems to be a problem with the iFrame when I am logged in with Flarum. When I'm loged out or logged in on my test account, there is no problem.,

clarkwinkelmann

JamminMB hi! It looks like the known (in)compatibility issue with FoF Night Mode.

I have not created an account but I see you have the Night Mode extension enabled so that's probably it. It causes the CSS to not load in the iframe. Unfortunately there isn't any solution to have both work together at this time. It also affects Flarum's own embed extension. There's a GitHub issue for it here FriendsOfFlarum/nightmode47

Try disabling Night Mode extension and see it it fixes it. If there are still issues I'll sign up to take a look as a logged in user.

JamminMB

clarkwinkelmann okay. Thanks

com_monstrous

I am wondering why I should pay a monthly fee whereas most vendors sell a yearly license that you may renew if you want update. The recurring model you are trying to put in place apply to hosted solutions like saas or paas if you are familiar with those terms but certainly not to your open source integration ... Just my 2 cents if you want more subscribers.

clarkwinkelmann

com_monstrous that's exactly how the yearly license on Extiverse works 👍️

I have kept the monthly license in addition to the yearly license because it's a good way for people to try out the extension with minimal investment, but I made the yearly plan cheaper to encourage switching to it.

Edwiin

How to solve this problem

[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).

require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-scripts] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>]...

luceos

Edwiin resolved through discord.

clarkwinkelmann

Version 1.7.2 - December 15, 2021

Hide Wordpress login button when SSO is disabled
Add support for query string inside of the Wordpress custom login path

pxnji

clarkwinkelmann
hello, any update regarding this feature?

clarkwinkelmann

pxnji this is in the work. I'm hoping to release this update later in January.

pxnji

clarkwinkelmann Okay, im glad to try this when its out. Thanks!

pxnji

clarkwinkelmann

Any update regarding this? or any workaround?

clarkwinkelmann

Version 1.7.3 - January 16, 2022

Fix incompatibility with extensions that load firstPost discussion relationship (including Blomstra Flag Duplicates)

Amarok

Thx again for quick fix @clarkwinkelmann ,
Just have a little problem to update.. I have this message when i try with your command (composer require kilowhat/flarum-ext-wordpress) :

[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).

Or this if I use the usual command (composer update kilowhat/flarum-ext-wordpress) :

[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).

luceos

Amarok are you sure you have followed the extiverse instructions? Your composer.json should mention extiverse under repositories.

Amarok

luceos yup, make some updates before without any problems and found the line for extiverse

"repositories": [
        {
            "type": "composer",
            "url": "https://extiverse.com/composer/"
        }
    ],

It's probably my fault, did many manipulations and maybe broke something :S

clarkwinkelmann

Everything is looking good on my side. Either require or update should work to get the latest version.

Can you double-check the Composer command is run in the correct directory?

Amarok

clarkwinkelmann I did a triple check (reinstall the token too). Nothing had change. It's maybe because I used the "composer update" one time and replace one obsolete package by new... 😅

clarkwinkelmann

Amarok you can check what's inside composer.json after "kilowhat/flarum-ext-wordpress":

Either "*" or "^1.0.0" (or other valid ^1.x.x versions) should be fine.

You can also try removing the package and adding it again. But if there's a deeper problem you might then be unable to add it again 😅

Amarok

clarkwinkelmann mmh, not your fault.. my token seems to be.. broken ^^ I redo one and all work again like a charm 😅

Thx for your patient !

« Previous Page Next Page »