@Nearata thanks for the PR!

Version 0.3.1 has been released which should fix "auto more" not working on the user directory. For extra measure, it should also work pretty much everywhere else, too. Again, thank you @Nearata 😃

    NorioDS lovely. Doesn't work on ranking page (page added by fof gamification extension)

        a month later
        2 months later

        NorioDS Hi, after Flarum 1.0 has been released auto more cannot be anymore installed.
        I hope this plugin can find some way to be updated, sorry I cannot help on this because is programming and I have no idea on what do 😃

            NorioDS Isn’t it just the composer.json file that needs to be updated? Unless someone reported an issue I don’t immediately see any coding changes needed.

                010101 Looks to be this way. I would do it, but not sure how to PR, and I don't remember my github password. PS, you should see their new recovery password crap, holly sh#t!!!

                      Problem 1
    - noriods/auto-more[0.1.0, ..., 0.2.0] require flarum/core ^0.1.0-beta-7 ->
found flarum/core[v0.1.0-beta.7, ..., v0.1.0-beta.16] but it does not match your
 minimum-stability.
    - noriods/auto-more 0.3.0 requires 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-sta
bility.
    - noriods/auto-more 0.3.1 requires flarum/core ^0.1.0-beta-15 -> found flaru
m/core[v0.1.0-beta.15, v0.1.0-beta.16] but it does not match your minimum-stabil
ity.
    - Root composer.json requires noriods/auto-more * -> satisfiable by noriods/
auto-more[0.1.0, 0.2.0, 0.3.0, 0.3.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and re
movals for packages currently locked to specific versions.
Running update with --no-dev does not mean require-dev is ignored, it just means
 the packages will not be installed. If dev requirements are blocking the update
 you have to resolve those problems.

                      Anonymous43 if you’re familiar with workbench you can use the repo that’s in my GitHub, alternatively it’d be a case of waiting for a tagged release (something I cannot do as I don’t have write access to the repo)

                        Anonymous43 you’re better off waiting for a tagged release then. Workbench is a fairly advanced setup for developers to test extensions etc.
                        It allows you to have a folder to pull extension files to and load them from here instead of relying on a tagged release in packagist.

                        I’d just wait for the release to be tagged once confirmed though, if I were you Anonymous43 😄

                            Anonymous43

                            You might be able to get it working by adding @katos's git repository to your list of repositories in your composer.json file.

                            {
  // existing composer.json
  "repositories": [
    {
      "type": "git",
      "url": "https://github.com/katosdev/automore"
    }
  ]
}

                            Then you can run...

                            composer require noriods/auto-more:dev-master

                            This just worked for me locally. Can I please stress that if you don't know what this does, please don't do it. It will cause more harm in the future than it saves you from now.

                              I know what it will do. But it will cause more headace down the road. When new updates gonna be awvailable from Nord. But thanks.