• [deleted]

@IanM Same Error

  • IanM replied to this.
    • [deleted]

    • Edited

    Now what should I do please tell, It's too hard for me to wait in this situation I am literally afraid too much

    [deleted] I'm guessing you edited your composer.json entries to * as per the upgrade guide.. But, by the looks of things, your composer.lock file is outdated.

    Follow this exactly

    • Edit your composer.json, change "flarum/core": "^1.0", to "flarum/core": "0.1.0-beta.16",
    • Run composer update -W
    • composer remove antoinefr/flarum-ext-online
    • Edit composer.json, change "flarum/core": "0.1.0-beta.16", to "flarum/core": "^1.0",
    • Run composer update -W

    So long as the rest of your required extensions are 1.0 ready, you'll be upgraded

      • [deleted]

      IanM Same Error

      IanM 0.1.0-beta.16

      Note : I have beta 16.1 so what to write

      • IanM replied to this.
        • [deleted]

        • Edited

        @IanM It is also showing that it does not matches your minimum stability

        • IanM replied to this.

          [deleted] there is no flarum/core 16.1

          [deleted] add this to your composer.json:

          Change the line "prefer-stable": true to "prefer-stable": true,
          Add this on the following line "minimum-stability": "beta"

          Then run my instructions again

          i'm not sure this is a correct idea or not .. I have come across a similar problem.

          i just downloaded the composer file and replaced it with composer.json.back-xxx latest file and removed the extension using command line composer remove pluginname

          composer remove antoinefr/flarum-ext-online

            [deleted] Look at the steps I gave you here: IanM

            This is exactly what I'm trying to help you to do. You must read and try to learn what you are being guided on

            • [deleted]

            • Edited

            Package fof/console is abandoned, you should avoid using it. No replacement was suggested.
            What is this Please help

              Hari The problem here is that the composer.json and composer.lock files are out of sync after a manual edit.

              The way I have described will resolve this particular problem, and remove the problem extension at the same time

                IanM I'm guessing you edited your composer.json entries to * as per the upgrade guide.. But, by the looks of things, your composer.lock file is outdated.

                Follow this exactly

                Edit your composer.json, change "flarum/core": "1.0", to "flarum/core": "0.1.0-beta.16",
                Run composer update -W
                composer remove antoinefr/flarum-ext-online
                Edit composer.json, change "flarum/core": "0.1.0-beta.16", to "flarum/core": "1.0",
                Run composer update -W

                So long as the rest of your required extensions are 1.0 ready, you'll be upgraded

                this is the right procedure .. Correct

                • [deleted]

                IanM I removed Online Success and

                [deleted] Package fof/console is abandoned, you should avoid using it. No replacement was suggested.

                Only got this

                • [deleted]

                IanM I did all the steps properly

                • [deleted]

                IanM Should i remove it??

                  [deleted]

                  IanM When the time comes to upgrade your forum to 1.0, you'll need to remove this package prior to upgrading, using the following command:

                  composer remove fof/console

                  • [deleted]

                  Now what is this??

                  fof/console is not required in your composer.json and has not been removed
                  ./composer.json has been updated
                  Running composer update fof/console
                  Loading composer repositories with package information
                  Dependency "flarum/core" is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
                  Updating dependencies
                  Nothing to modify in lock file
                  Installing dependencies from lock file (including require-dev)
                  Nothing to install, update or remove
                  Package fof/console is abandoned, you should avoid using it. No replacement was suggested.
                  Generating autoload files
                  106 packages you are using are looking for funding.
                  Use the `composer fund` command to find out more!
                  Removal failed, fof/console is still present, it may be required by another package. See `composer why fof/console`.
                  • [deleted]

                  • Edited

                  @IanM
                  I asked composer why

                  He told me

                  fof/best-answer 0.4.0 requires fof/console (*)
                  fof/sitemap 0.7.0 requires fof/console (0.7.0)
                  I have to remove this also???