Premium WordPress Integration

chrisc297

Flarum core: 1.7.1
PHP version: 7.4.33
MySQL version: 10.3.38-MariaDB-log-cll-lve
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bz2, calend ar, ctype, curl, hash, filter, ftp, gettext, gmp, SPL, iconv, pcntl, readline, R eflection, session, standard, shmop, SimpleXML, mbstring, tokenizer, xml, i360, bcmath, dom, fileinfo, gd, imagick, imap, intl, json, exif, mcrypt, mysqlnd, mys qli, PDO, pdo_mysql, pdo_sqlite, Phar, posix, sockets, timezonedb, xmlreader, xm lwriter, xsl, zip, ionCube Loader, Zend OPcache
+---------------------------------+---------+--------+
| Flarum Extensions | | |
+---------------------------------+---------+--------+
| ID | Version | Commit |
+---------------------------------+---------+--------+
| flarum-flags | v1.7.0 | |
| flarum-approval | v1.7.0 | |
| flarum-suspend | v1.7.0 | |
| flarum-subscriptions | v1.7.0 | |
| flarum-tags | v1.7.1 | |
| zerosonesfun-direct-links | 3.1 | |
| v17development-seo | v1.8.0 | |
| sycho-profile-cover | v1.3.3 | |
| michaelbelgium-discussion-views | v7.2.1 | |
| justoverclock-hashtag | 1.0.1 | |
| fof-user-directory | 1.2.3 | |
| fof-user-bio | 1.1.1 | |
| fof-split | 1.1.0 | |
| fof-spamblock | 1.1.0 | |
| fof-sitemap | 1.0.3 | |
| fof-share-social | 1.1.2 | |
| fof-secure-https | 1.1.1 | |
| fof-recaptcha | 1.1.1 | |
| fof-reactions | 1.1.5 | |
| fof-pretty-mail | 1.1.1 | |
| fof-polls | 1.3.0 | |
| fof-pages | 1.0.5 | |
| fof-nightmode | 1.5.1 | |
| fof-merge-discussions | 1.3.1 | |
| fof-links | 1.1.3 | |
| fof-impersonate | 1.1.1 | |
| fof-ignore-users | 1.1.1 | |
| fof-formatting | 1.0.3 | |
| fof-follow-tags | 1.1.7 | |
| fof-default-user-preferences | 1.2.0 | |
| fof-cookie-consent | 1.1.1 | |
| fof-ban-ips | 1.0.3 | |
| fof-analytics | 1.1.0 | |
| flarum-sticky | v1.7.0 | |
| flarum-statistics | v1.7.0 | |
| flarum-mentions | v1.7.0 | |
| flarum-markdown | v1.7.0 | |
| flarum-lock | v1.7.0 | |
| flarum-likes | v1.7.0 | |
| flarum-lang-english | v1.7.0 | |
| flarum-emoji | v1.7.0 | |
| flarum-bbcode | v1.7.0 | |
| datlechin-link-preview | v1.3.2 | |
| clarkwinkelmann-post-bookmarks | 1.0.0 | |
| clarkwinkelmann-mailing | 1.0.0 | |
| clarkwinkelmann-emojionearea | 1.0.0 | |
| blomstra-welcome-login | 0.1.0 | |
| blomstra-mark-unread | 0.2.0 | |
| askvortsov-moderator-warnings | v0.6.1 | |
| archlinux-de-anti-spam | 1.1.1 | |
| afrux-forum-widgets-core | v0.1.7 | |
+---------------------------------+---------+--------+
Base URL: https://forums.tellytips.com
Installation path: /home/listsbyc/forums.tellytips.com
Queue driver: sync
Session driver: file
Scheduler status: Active
Mail driver: smtp
Debug mode: off

chrisc297

@clarkwinkelmann I can't get the extension installed so can't shaere composer why-not kilowhat/flarum-ext-wordpress 1.8.0 output.

Appreciate any advice. I installed Flarum and the extensions, but anything too technical I will need guidance with. Keen to get this plugin ready asap.

hrvoje_hr

chrisc297 I've had a similar issue.The solution was to edit composer.json and add specific version next to this extension (instead of reccomended *)

clarkwinkelmann

chrisc297 I'll take a look tomorrow but in the meantime you should be able to run the why-not command. Its whole purpose is to analyze why a specific package or version cannot be installed so it should always produce some output.

chrisc297

hrvoje_hr I can't get it installed, so there's nothing for it in the composer.json for it if that makes sense.

hrvoje_hr

chrisc297 oh, yes, you're right. Wishing you to resolve that asap mate

chrisc297

clarkwinkelmann

So I've tried this:
composer require kilowhat/flarum-ext-wordpress:¹.8 -W

It gives me this result of:
Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update kilowhat/flarum-ext-wordpress --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires kilowhat/flarum-ext-wordpress ¹.8 -> satisfiable by kilowhat/flarum-ext-wordpress[1.8.0].
- kilowhat/flarum-ext-wordpress 1.8.0 requires symfony/dom-crawler ⁴.0 -> found symfony/dom-crawler[v4.0.0, ..., v4.4.45] but these were not loaded, likely because it conflicts with another require.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Then I tried this:
composer why-not kilowhat/flarum-ext-wordpress 1.8.0

Which gives me this:

In BaseDependencyCommand.php line 98:

Could not find package "kilowhat/flarum-ext-wordpress" in your project

prohibits [-r|--recursive] [-t|--tree] [--locked] [--] <package> <version>

clarkwinkelmann

chrisc297 thanks. I have identified which extension also uses the Symfony DOM Crawler, it's https://discuss.flarum.org/d/30011-link-preview

I'll publish an update to my extension later today to use a newer version of the DOM Crawler.

clarkwinkelmann

Flarum changelog

Version 1.8.1 - March 30, 2023

Fix WP thumbnail change not always synchronising.
Fix WP post URL slug change not synchronising.
Update Symfony dependencies to prevent conflict with other Flarum extensions.

chrisc297 the installation command from the documentation should now work without any tweak required.

chrisc297

clarkwinkelmann

Awesome thank you!

Quick question re the plugin. If sign up is left enabled on Flarum. Does this create an account in WordPress too?

clarkwinkelmann

chrisc297 If sign up is left enabled on Flarum. Does this create an account in WordPress too?

No. Accounts must be created first on the WordPress side and the "Log in with WordPress" button must be used to perform global single sign on.

If a standalone Flarum account is created, it will be separate from WordPress until the first time the same email is logged in or registered in WordPress. Then the user will no longer be allowed to login using password and will have to use WordPress to login. Accounts don't need to exist in WordPress to comment though. If you don't have an existing userbase and don't have any community feature in WordPress itself, you can leave SSO off and let users create accounts on Flarum directly to comment.

chrisc297 the video doesn't fit in line

The WordPress preview only has minimal CSS. I have added a max-width of 100% for images but never tested with iframes. I could add some explicit CSS for this in a future update since I see WordPress includes the aspect ratio with the .wp-embed-aspect-16-9 class. In the meantime you have 2 options: add some custom CSS to Flarum to force the iframe size in .KilowhatWordpressSummaryPost-Article or use the HTML tag whitelist in the extension settings to exclude iframes from the preview, forcing users to visit the post on WordPress to see the video.

chrisc297 is this how comments are supposed to look

I assume you disabled the extension/comments since your post because I don't see any Flarum comment thread on the page.

chrisc297

Also, is this how comments are supposed to look:
https://tellytips.com/netflix/were-building-something-new-stay-tuned/

hrvoje_hr

chrisc297 yes, those are comments from this plugin. But you can customize the looks with your own css

chrisc297

Sorry, another thing. This is a post with a YouTube video from WordPress - the video doesn't fit in line
https://forums.tellytips.com/d/4-swarm-streaming-now

chrisc297

clarkwinkelmann

Thanks for explaining. Appreciate all your help.

hrvoje_hr

clarkwinkelmann I had only one issue with multisite support so far. Comment numbers only updating on the main site

clarkwinkelmann

hrvoje_hr ah yes... I'm not sure if there's any easy solution for this without making Flarum aware of which comments are under which multisite.

WordPress is probably getting the API request for each post ID, but it ignores the IDs that aren't part of the main site.

Do you have anything logged in the Flarum log file by my extension? WordPress API errors should be logged in there. If you can share the logs with me it might give me some hints as to how I could implement this without having to setup a multisite environment myself just yet.

hrvoje_hr

No API errors whatsoever in Flarum logs

At this moment, the extension updates comments only on the main site. It fires API requests even for comments threads of another site. But posts IDs on both sites are different (on the main site increment is from 0, on the other is from 500k), so there are no overwrites. Because of that, I would be fine if it fires the same requests to both sites on the network without any logic.

hrvoje_hr

One new (maybe) unrelated issue. I've migrated Flarum to another server. After that, I noticed that the comments count doesn't update anymore even on the main site, so I tried to reenable Wordpress extension. After that, I'm getting this in Admin:

This extension has no settings.

I've tried to reinstall, purge data, clear cache, and run migrate command... Nothing helps.

All other extensions work as expected.

clarkwinkelmann

hrvoje_hr the most likely causes are either an outdated Flarum cache or a javascript error. Can you check if there is anything in the browser console?

You could also try removing the extension with Composer and then install it again. Don't click "purge". Just remove with Composer, clear Flarum cache, then re-install and clear the cache again.

I've seen few but regular reports on Discuss of random extensions that would not show their settings. But nobody has ever identified the cause. Most likely it's something to do with server resources, like a file permissions problem on the disk or the memory/time allocated to PHP being insufficient and causing some resources to be missing from the final javascript or CSS files. I wish I'd knew exactly what it was so I could provide better guidance. It doesn't seem to be extension specific.

hrvoje_hr

clarkwinkelmann There were no errors in the browser console. Hovewer, I've managed to get it back after reinstalling extension few times via Composer. Thank you.

The same issue appeared on some other extensions after migration as well. I think a low PHP memory_limit was responsible. After raising from 128 to 512MB and reinstailling affected extensions, everything is fine.

Also, after that fixed comments count on the main site as well

hrvoje_hr After that, I noticed that the comments count doesn't update anymore even on the main site

However, the issue about updating comments count on other sites on network still persists

« Previous Page Next Page »