Premium WordPress Integration

hrvoje_hr

That was the first I checked, it's on. This issue occurred after I upgraded Flarum from 1.3 to 1.6

clarkwinkelmann

Version 1.7.6 - December 13, 2022

Fix "WordPress" case in the extension name, documentation and English translations. The namespaces and attributes are unchanged and keep their lowercase "p".
Fix new comment threads with no replies not showing as unread in Flarum discussion list. It will now show as unread + zero replies which Flarum would not natively do.

This problem appeared in version 1.7.4 when the reply count was fixed for new discussions.

hrvoje_hr this should fix the issue. Thanks for your report! It wasn't actually caused by the Flarum update, but by the change I made in a previous version to fix the reply count.

hrvoje_hr

clarkwinkelmann it works, thank you!

cpluscc

@clarkwinkelmann
It seems that this extension is not compatible with php 8.0.
The dependency symfony/dom-crawler ⁴.0 requires php 7.3.The latest version of it is.v6.0
Here is the error.

Problem 1
    - kilowhat/flarum-ext-wordpress[1.7.0, ..., 1.7.6] require symfony/dom-crawler ^4.0 -> found symfony/dom-crawler[v4.0.0, ..., v4.4.45] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires kilowhat/flarum-ext-wordpress ^1.7 -> satisfiable by kilowhat/flarum-ext-wordpress[1.7.0, ..., 1.7.6].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require kilowhat/flarum-ext-wordpress:*" to figure out if any version is installable, or "composer require kilowhat/flarum-ext-wordpress:^2.1" if you know which you need.

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

cpluscc

Anyone?

hrvoje_hr

cpluscc I'm also waiting for this to upgrade my server on PHP 8

clarkwinkelmann

cpluscc can you share the entire Composer output, and maybe the output of composer why-not kilowhat/flarum-ext-wordpress 1.7 and php flarum info ? The output you shared makes no mention of a PHP version issue. Maybe it's a conflict between the dependencies required by different extensions.

I am not aware of any issue running this extension on PHP 8.0 or 8.1. I am pretty sure I worked on the last few updates on my PHP 8.1 dev setup. I just tried installing the extension on my PHP 8.0 dev setup and didn't encounter any issue. PHP 8.2 might be an issue, but I think the problems are with Flarum core and are already being addressed in Flarum version 1.7. I can try again this weekend on my PHP 8.1 computer if needed, but I'm really not seeing any issue dependency-wise. symfony/dom-crawler@v4.4.45 requires php: >=7.1.3 which will allow with 8.0 and 8.1 just fine.

Please delete the GitHub repository and Packagist repo you created with a copy of my source code, or I will have to reach out to GitHub to take it down. It's fine with me if you would like to maintain a private fork as long as an Extiverse license is active, but it must be only used and accessible within your organization.

hrvoje_hr

While you're here, do you plan to support Wordpress Multisite/Network function?

cpluscc

clarkwinkelmann
flarum/flarum - requires kilowhat/flarum-ext-wordpress (v1.7.6)
kilowhat/flarum-ext-wordpress 1.7.0 requires league/html-to-markdown (⁴.10)
flarum/flarum - requires league/html-to-markdown (⁵.1)
kilowhat/flarum-ext-wordpress 1.7.0 requires symfony/dom-crawler (⁴.0)
flarum/flarum - does not require symfony/dom-crawler (but v6.0.19 is installed)

cpluscc

clarkwinkelmann I'm so sorry, I have deleted them.

clarkwinkelmann

cpluscc can you share the content of your composer.json file (the one in the root folder of Flarum). Maybe you have manually installed a specific version of a dependency?

I'm really not sure what might be wrong otherwise. You could try deleting the composer.lock (.lock, not .json) file and vendor folder, and run composer install again to try getting a fresh version of everything or a clearer error message. This might cause some extensions or Flarum to update if you aren't already on the latest version. Make a backup of those files first in case there is an actual incompatibility so you can rollback.

hrvoje_hr

@clarkwinkelmann could you change the way we choose where to place commens threds?

Now, that option is selected on the Flarum side, but in my case, it would be better in Wordpress settings.

I have multisite Wordpress (two sites on the same database). Everything works great out of the box, but I would like to place comments from another site in ther own tag.

clarkwinkelmann

hrvoje_hr I'll see what I can do. Placing the setting on the Flarum side was easier as I can get access to the list of tags, but I could add an "advanced" setting in Wordpress where a tag slug can be typed instead.

hrvoje_hr

That would be great, ID or slug

hrvoje_hr

clarkwinkelmann hi, do you have any eta for that? And let me know if additional commission is needed

clarkwinkelmann

Flarum changelog

Version 1.8.0 - March 26, 2023

Added WP author sync to discussion owner.
Added WP thumbnail sync and display options.
Added WP tag override feature for multi-site use cases.
Added more information to WP request log in Flarum log file and disabled logging completely when debug mode is off.

This update requires PHP 7.4 or PHP 8.0+. Support for PHP 7.3 has been dropped.

The new features require updating the WordPress plugin to version 1.5.
See below for WordPress plugin changelog.

Both versions 1.7 and 1.8 of the Flarum extension have been verified compatible with Flarum 1.7.

WordPress changelog

Version 1.5.0 - March 26, 2023

Added Flarum tags override feature.
Added post author ID synchronisation.
Added post thumbnail synchronisation.
Fixed capitalization of word "WordPress" in setting descriptions.

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

Suggestions on how to style the author and thumbnail are welcome. The default styling is extremely simple, but I expect the final users will want to customize it anyway so I don't want to invest too much time in the default CSS.

I am still planning to implement a proper import/sync feature that would help update existing discussions with the new features without having to go and edit them one by one, but I still haven't managed to finish that feature at this time.

hrvoje_hr JohnP your suggestions have been implemented!

hrvoje_hr

clarkwinkelmann thanks for the update, really appreciate

~~I've noticed that we can now add more than one tag for comments discussions separated by commas. What happens if we add more tags?~~

EIDT: Oh, I understand now. Such a stupid question

clarkwinkelmann

hrvoje_hr it was already possible to add multiple tags on the Flarum side when choosing "custom" at the bottom of the dropdown since many versions.

It's indeed the most basic solution, it just assigns all of the given tags at discussion creation (even if they don't match Flarum tag requirements)

One feature I have been thinking of adding is to automatically select Flarum tags based on assigned categories/taxonomies in WordPress. But I put the feature aside for now because the settings UI to configure it would be quite complex (which WP taxonomies match to which Flarum tags or Flamarkt Taxonomies, how to prefix taxonomy slugs if they conflict with non-blog tags in Flarum, whether to create new tags automatically, whether to sync titles and descriptions, how to sync tags after initial creation, etc). But it's still something I can add in a future update if there's interest.

chrisc297

Bought this plugin last night and having difficulty installing.

When I run:
composer require kilowhat/flarum-ext-wordpress

I get this:
`./composer.json has been updated
Running composer update kilowhat/flarum-ext-wordpress
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- kilowhat/flarum-ext-wordpress 1.0.0 requires flarum/core >=0.1.0-beta.10 <0.1.0-beta.11 -> found flarum/core[v0.1.0-beta.10] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress[1.0.1, ..., 1.2.3] require flarum/core >=0.1.0-beta.10 <0.1.0-beta.12 -> found flarum/core[v0.1.0-beta.10, v0.1.0-beta.11, v0.1.0-beta.11.1] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress 1.2.4 requires flarum/core >=0.1.0-beta.10 <0.1.0-beta.13 -> found flarum/core[v0.1.0-beta.10, v0.1.0-beta.11, v0.1.0-beta.11.1, v0.1.0-beta.12] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress[1.3.0, ..., 1.3.3] require flarum/core >=0.1.0-beta.12 <0.1.0-beta.13 -> found flarum/core[v0.1.0-beta.12] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress[1.3.4, ..., 1.6.0] require flarum/core >=0.1.0-beta.12 <0.1.0-beta.14 -> found flarum/core[v0.1.0-beta.12, v0.1.0-beta.13] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress 1.6.2 requires flarum/core >=0.1.0-beta.14 <0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress 1.6.3 requires flarum/core >=0.1.0-beta.15 <0.1.0-beta.16 -> found flarum/core[v0.1.0-beta.15] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress 1.6.4 requires flarum/core >=0.1.0-beta.16 <0.1.0-beta.17 -> found flarum/core[v0.1.0-beta.16] but it does not match your minimum-stability.
- kilowhat/flarum-ext-wordpress[1.7.0, ..., 1.8.0] require symfony/dom-crawler ⁴.0 -> found symfony/dom-crawler[v4.0.0, ..., v4.4.45] but the package is fixed to v5.4.21 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires kilowhat/flarum-ext-wordpress * -> satisfiable by kilowhat/flarum-ext-wordpress[1.0.0, ..., 1.8.0].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require kilowhat/flarum-ext-wordpress:*" to figure out if any version is installable, or "composer require kilowhat/flarum-ext-wordpress:².1" if you know which you need.

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

Please can someone assist?

« Previous Page Next Page »