Is there anyone willing to develop/upgrade the Reply2See extension?

mceyes

I am willed to do it by myself, I work in cyber security so I kinda know about programming/scripting languages and fundamentals.
I was thinking to force the installation of the kvothe/reply-to-see extension, but there was no way to do so without having composer stopping because the incompatibility with the new version of the Core.

Can anyone help me to debug this? Could anyone find out what needs to be upgraded in the new version of the Flarum Core in order to fix this extension? I think it could be a fundamental feature for a lot of admins, me included

Justoverclock

mceyes if you have a local instance of flarum, you can fork the repository and install the extension with *@dev constraint.

mceyes

I just looked up how to get the *@dev version, but it still gives me the same error.

$ composer require kvothe/reply-to-see:*@dev Problem 1 - kvothe/reply-to-see[dev-master, v0.1.2] require flarum/core ^0.1.0-beta.8 -> found flarum/core[v0.1.0-beta.8, ..., v0.1.0-beta.16] but it does not match your minimum-stability. - kvothe/reply-to-see[0.1.0, ..., 0.1.1] require flarum/core ^0.1.0-beta.6 -> found flarum/core[v0.1.0-beta.6, ..., v0.1.0-beta.16] but it does notmatch your minimum-stability. - Root composer.json requires kvothe/reply-to-see *@dev -> satisfiable by kvothe/reply-to-see[dev-master, 0.1.0, 0.1.1, v0.1.2].

Did I do something wrong?

IanM

mceyes Before you can even require the @dev locally, you'll need to update the flarum/core constraint. I've you're building for v1, then that'll need to be ^1.0.0

After that, you've got a fair amount of updating/refactoring to do, as it looks like that extension was written for beta.8. Follow the update docs here. You'll need to start at the beta.10 section, and slowly make your way up the list until to complete the requirements for 1.0

Justoverclock

mceyes remember to set a workbench first
https://discuss.flarum.org/d/1608-extension-development-using-composer-repositories-path