How to upgrade to 1.7.1??

Wellwisher

Can you try the common fixes here, check your config.php file to ensure it has the correct settings:
https://docs.flarum.org/troubleshoot

Wellwisher

Also try running:

composer why-not flarum/core 1.7.1

See if anything useful pops up about errors

zhanzhang

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires flarum/core ¹.7.1, found flarum/core[dev-main, dev-master, 1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 2
- Root composer.json requires flarum-lang/chinese-simplified ¹.2 -> satisfiable by flarum-lang/chinese-simplified[v1.2.0].
- flarum-lang/chinese-simplified v1.2.0 requires flarum/core ¹.0.0 -> found flarum/core[v1.0.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
Problem 3
- Root composer.json requires flarumtr/flarum-ext-mobile-search ¹.2 -> satisfiable by flarumtr/flarum-ext-mobile-search[v1.2].
- flarumtr/flarum-ext-mobile-search v1.2 requires flarum/core ¹.0 -> found flarum/core[v1.0.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
Problem 4
- Root composer.json requires ramesh-dada/mobile-flarum-newdiscuss ⁷.2 -> satisfiable by ramesh-dada/mobile-flarum-newdiscuss[7.2.0, 7.2.1].
- ramesh-dada/mobile-flarum-newdiscuss[7.2.0, ..., 7.2.1] require flarum/core ¹.0 -> found flarum/core[v1.0.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
Problem 5
- Root composer.json requires ramesh-dada/realtime ¹⁰⁰.1 -> satisfiable by ramesh-dada/realtime[100.1].
- ramesh-dada/realtime 100.1 requires flarum/core ¹.0 -> found flarum/core[v1.0.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
Problem 6
- acpl/mobile-tab[1.0.0, ..., 1.0.5] require flarum/core ¹.0 -> found flarum/core[v1.0.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
- acpl/mobile-tab[1.1.0, ..., 1.1.1] require flarum/core ¹.2 -> found flarum/core[v1.2.0, ..., v1.7.0] but it conflicts with your root composer.json require (¹.7.1).
- Root composer.json requires acpl/mobile-tab * -> satisfiable by acpl/mobile-tab[1.0.0, ..., 1.1.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals 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.

xiahuan710

I sent the URL, there is no too important information, I have opened the debug mode

www.haoquant.com

Wellwisher

xiahuan710

I think there's an issue with compatibility with extensions. Or I think you need to a certain type of composer install code. Luceos knows more about this so I'd wait for him or some of the other devs.

Whilst you're waiting on that, can I ask you to copy and paste the output of the composer.json file here (located in ur flarum folder install). It may prove useful to help support you.

Be sure to remove any passwords and sensitive information etc.

zhanzhang

Wellwisher

{
"name": "flarum/flarum",
"description": "Delightfully simple forum software.",
"type": "project",
"keywords": [
"forum",
"discussion"
],
"homepage": "https://flarum.org/",
"license": "MIT",
"authors": [
{
"name": "Flarum",
"email": "info@flarum.org",
"homepage": "https://flarum.org/team"
}
],
"support": {
"issues": "https://github.com/flarum/core/issues",
"source": "https://github.com/flarum/flarum",
"docs": "https://docs.flarum.org/"
},
"require": {
"acpl/mobile-tab": "",
"flarum-lang/chinese-simplified": "¹.2",
"flarum/approval": "",
"flarum/bbcode": "",
"flarum/core": "¹.7.1",
"flarum/emoji": "",
"flarum/flags": "",
"flarum/lang-english": "",
"flarum/likes": "",
"flarum/lock": "",
"flarum/markdown": "",
"flarum/mentions": "",
"flarum/nicknames": "",
"flarum/pusher": "",
"flarum/statistics": "",
"flarum/sticky": "",
"flarum/subscriptions": "",
"flarum/suspend": "",
"flarum/tags": "*",
"flarumtr/flarum-ext-mobile-search": "¹.2",
"ramesh-dada/mobile-flarum-newdiscuss": "⁷.2",
"ramesh-dada/realtime": "¹⁰⁰.1"
},
"config": {
"preferred-install": "dist",
"sort-packages": true
}
}

xiahuan710

Wellwisher It's just a test item, no need to delete the password

xiahuan710

php flarum info：

Flarum core: 1.7.1
PHP version: 7.4.33
MySQL version: 5.7.35-log
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, ctype, curl, dom, hash, filter, ftp, gd, gettext, SPL, iconv, intl, json, mbstring, session, standard, pcntl, mysqlnd, PDO, pdo_mysql, pdo_sqlite, Phar, posix, Reflection, mysqli, shmop, SimpleXML, soap, sockets, sodium, exif, sysvsem, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, SourceGuardian, imagick, fileinfo, memcache, memcached, redis, ionCube Loader, Zend OPcache
+--------------------------------+---------+--------+
| Flarum Extensions | | |
+--------------------------------+---------+--------+
| ID | Version | Commit |
+--------------------------------+---------+--------+
| flarum-flags | v1.7.0 | |
| flarum-approval | v1.7.0 | |
| flarum-tags | v1.7.1 | |
| flarum-suspend | v1.7.0 | |
| flarum-subscriptions | v1.7.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-chinese-simplified | v1.3.0 | |
| flarum-emoji | v1.7.0 | |
| flarum-bbcode | v1.7.0 | |
+--------------------------------+---------+--------+
Base URL: https://www.haoquant.com
Installation path: /home/www/web/www.haoquant.com
Queue driver: sync
Session driver: file
Mail driver: smtp
Debug mode: ON

Wellwisher

xiahuan710 I know sir, but it's a good habit 😂

luceos

Try disabling debug mode and see if that helps.

xiahuan710

luceos After turning off the debug mode, it is a blank page

Wellwisher

xiahuan710 it's working for me, maybe clear your cache?

xiahuan710

Inexplicable, it's automatically good。

After I went out to play, the program was repaired by myself. When I came back, I was surprised

Wellwisher

I wanted to solve this puzzle. 😂

All I can assume that caused the problem is once you updated Flarum to v1.7.1, and you got the error. You went through troubleshooting common fixes. Something that you tried in that article must have worked. But you left the debug mode on by accident.

This brings be back to my question, what actually solved this error?:

Flarum\Http\Exception\MethodNotAllowedException POST?

😂

But I am glad it's solved for you. 🙂

clarkwinkelmann

Wellwisher where are you seeing that error? What actions lead to the error? Do you know which URL the browser or Flarum is trying to load?

If the URL belongs to a Flarum extension and everything else works, there could be a bug in the extension.

If the bug happens on multiple pages including Flarum pages, maybe the rewrites are not correctly setup, or you are not accessing the website via the URL defined in config.php.

Wellwisher

clarkwinkelmann

I think there's a misunderstanding, the problem was resolved but I am unsure how lol.

It was the original poster that had the issue, I was not seeing the error he mentioned.

This was the error reported by him Flarum\Http\Exception\MethodNotAllowedException POST after upgrading to 1.71. He tried a few things and then it was resolved.

As you pointed out Clark, it's highly likely to be something not set up correctly in config.php

clarkwinkelmann

Wellwisher I only realized after posting my reply that you weren't the OP, but I think the hints still apply 👍️

If that error happens on the Flarum "upgrade" screen where the database password is asked, it could be because the form was already submitted previously but the page didn't refresh, or the back button might have been used after performing the upgrade. Or the upgrade screen was open but then the php flarum migrate command was run on the server.

Anyway if it's gone it probably wasn't anything major like broken webserver rewrites. Unless the rewrites module was indeed disabled and that a server restart fixed it.

xiahuan710

clarkwinkelmann It's similar to what you say，After I came back, I closed the browser and just opened the browser again. I can only determine that the browser cached

« Previous Page