Problems updating to 1.8

headwear

GreXXL Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]? y
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals

Upgrading hehongyuanlove/flarum-auth-qq (1.3.5 => 2.5.1)
Writing lock file
Installing dependencies from lock file
Package operations: 0 installs, 1 update, 0 removals
Upgrading hehongyuanlove/flarum-auth-qq (1.3.5 => 2.5.1): Extracting archive
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
Generating optimized autoload files
103 packages you are using are looking for funding.
Use the composer fund command to find out more!
Found 2 security vulnerability advisories affecting 2 packages.
Run composer audit for a full list of advisories.

GreXXL

headwear your php flarum info still shows tags as version 1.7?

headwear

GreXXL Flarum core: 1.8.1
PHP version: 7.4.33
MySQL version: 5.7.40-log
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, ctype, curl, dom, filter, ftp, gd, gettext, hash, iconv, intl, json, mbstring, SPL, session, pcntl, standard, PDO, mysqlnd, pdo_sqlite, Phar, posix, Reflection, pdo_mysql, shmop, SimpleXML, soap, sockets, sodium, mysqli, sysvsem, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, zip, openrasp, exif, fileinfo, Zend OPcache
+----------------------------------+---------+------------------------------------------+
| Flarum Extensions | | |
+----------------------------------+---------+------------------------------------------+
| ID | Version | Commit |
+----------------------------------+---------+------------------------------------------+
| flarum-flags | v1.8.0 | |
| flarum-tags | v1.7.1 | |
| flarum-sticky | v1.7.0 | |
| flarum-bbcode | v1.8.0 | |
| afrux-forum-widgets-core | v0.1.7 | |
| flarum-suspend | v1.8.0 | |
| flarum-approval | v1.8.0 | |
| ziiven-post-number | v0.1.2 | |
| wanecho-mobilelogin | 1.0.6 | 3c3e38cab8c6e00c8d9176c7a7aaf26e68c9bbbe |
| v17development-seo | v1.8.0 | |
| the-turk-stickiest | 3.0.1 | |
| pipecraft-id-slug | v1.1.0 | |
| littlecxm-reply-to-see | 1.0.2 | |
| justoverclock-custom-html-widget | 0.1.4 | |
| isaced-email-verification-switch | 1.0.0 | |
| fof-user-directory | 1.2.3 | |
| fof-user-bio | 1.1.0 | |
| fof-upload | 1.2.3 | |
| fof-sitemap | 1.0.3 | |
| fof-profile-image-crop | 1.1.0 | |
| fof-pretty-mail | 1.1.1 | |
| fof-pages | 1.0.5 | |
| fof-oauth | 1.3.1 | |
| fof-links | 1.1.4 | |
| fof-linguist | 1.1.1 | |
| fof-forum-statistics-widget | 1.1.0 | |
| fof-drafts | 1.2.2 | |
| fof-disposable-emails | 1.0.0 | |
| fof-cookie-consent | 1.1.1 | |
| flarum-subscriptions | v1.8.0 | |
| flarum-statistics | v1.8.0 | |
| flarum-nicknames | v1.8.0 | |
| flarum-markdown | v1.8.0 | |
| flarum-lock | v1.7.0 | |
| flarum-likes | v1.7.0 | |
| flarum-lang-chinese-simplified | v1.2.0 | |
| davwheat-ads | 1.2.0 | |
| darkle-fancybox | 1.1.2 | |
| cccyun-clogin-oauth | v1.0.2 | |
| afrux-news-widget | v0.1.1 | |
+----------------------------------+---------+------------------------------------------+
Base URL: https://www.8uid.com
Installation path: /www/wwwroot/www.8uid.com
Queue driver: sync
Session driver: file
Scheduler status: Never run
Mail driver: smtp
Debug mode: off

Wellwisher

Site seems to be operational?

I used Clark's tool: https://lab.migratetoflarum.com/

Seems like there were number of sever related cURL errors:

cURL error 7: Failed to connect to 8uid.com port 443: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://8uid.com/

cURL error 52: Empty reply from server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.8uid.com/vendor/composer/installed.json

etc. Not sure if that helps devs better.

clarkwinkelmann

Wellwisher Empty reply from server [...] /vendor/composer/installed.json

It's a bit odd for the server to not return a proper reply, but if it always returns the same empty reply then it might be the intended way the server admin protected themselves against accessing the restricted files. That request just probes a filename that should never be accessible but might be if the server is incorrectly configured.

The problem at the root domain not accepting HTTPS will not cause any other issue, it's just good practice to answer on both HTTP and HTTPS on the root domain and serve the appropriate redirect to the canonical URL, which seems to be the www subdomain in this case.

Neither of those issues seem to relate to the problems described higher in the thread though.

headwear

After running Composer why not flash/tags 1.8

Problem 1 -Root composer.json requires flash/tags *, found flash/tags [v1.0.0,..., v1.7.1] but it conflicts with your temporary update constraint (flash/tags: 1.8) Problem 2 -The tour/fare stickiest is locked to version 3.0.1 and an update of this package was not requested -The tour/fare stick 3.0.1 requires flare/tags ^ 1.0.0->find flare/tags [v1.0.0,..., v1.7.1] but it conflicts with your temporary update constraint (flare/tags: 1.8)
Is this helpful for developers?

abczoujin

headwear

headwear After running Composer why not flash/tags 1.8

Problem 1
-Root composer.json requires flash/tags *, found flash/tags [v1.0.0,..., v1.7.1] but it conflicts with your temporary update constraint (flash/tags: 1.8)
Problem 2
-The tour/fare stickiest is locked to version 3.0.1 and an update of this package was not requested
-The tour/fare stick 3.0.1 requires flare/tags ^ 1.0.0->find flare/tags [v1.0.0,..., v1.7.1] but it conflicts with your temporary update constraint (flare/tags: 1.8)

Step 1. Make sure you have disabled or removed the "tour/fare" extension
Step 2. Try updating the composer.json file to allow the flash/tags plugin to use its latest version. You can add the following to your composer.json file:

 "minimum-stability": "dev",
 "prefer-stable": true

Step 3. Execute the tags expansion upgrade command

If the update is still unsuccessful, please continue to run Composer why not flash/tags 1.8

headwear

The problem has been solved. Thank you to the friends in the Chinese group for their enthusiastic help. The problem lies in the fact that I am using Alibaba Source for the domestic composer in China. Alibaba Source did not promptly remove the official source package, resulting in the tags plugin and other updates not being updated. Finally, Thank you very much for the help of the developers!

spiridon

Hi guys!

Can you help me solve the problem after the update? When I am trying to enable some of the extensions I get errors like these:

flarum.ERROR: Error: Call to undefined method Flarum\Extend\Model::cast() in ..../vendor/flarum/sticky/extend.php:31
or
flarum.ERROR: Error: Call to undefined method Flarum\Extend\Model::cast() in ...../vendor/flarum/flags/extend.php:49

Several extensions work fine. For example, statistics.

For better understanding, I am updating the instance of Flarum from 1.1.1 to 1.8
With disabled extensions, it works. But... What I missed and what should I do?

luceos

spiridon I am not 100% sure, but I think it relates to renaming 1st party extensions from flarum/flarum-ext-sticky to flarum/sticky; so inside your composer.json look for any entries under require starting with flarum/ and remove after / the flarum-ext-, then run composer update --prefer-dist --no-dev -a.

spiridon

luceos Looks like I have made such update.

"require": {
        "flarum/approval": "*",
        "flarum/bbcode": "*",
        "flarum/core": "^1.0",
        "flarum/emoji": "*",
        "flarum/flags": "*",
        "flarum/lang-english": "*",
        "flarum/likes": "*",
        "flarum/lock": "*",
        "flarum/markdown": "*",
        "flarum/mentions": "*",
        "flarum/pusher": "*",
        "flarum/statistics": "*",
        "flarum/sticky": "*",
        "flarum/subscriptions": "*",
        "flarum/suspend": "*",
        "flarum/tags": "*",
        "fof/analytics": "*",
        "fof/formatting": "*",
        "fof/links": "*",
        "fof/oauth": "*",
        "fof/pages": "*",
        "fof/recaptcha": "*",
        "fof/secure-https": "*",
        "fof/sitemap": "*"
    },

Probably I need to try to upgrade step by step, version to version, and see at what stage it breaks.

Maybe there are some other ideas?

luceos

spiridon have you run composer update?

spiridon

luceos
I solved the problem created with my own hands. I've tried updating the Flarum instance on the copy of Flarum dir. But I missed updating the path to autoload. As a result instead of fresh flarum packages it still used the old version of packages. Stupid mistake. Sorry, guys! Thanks @luceos!

« Previous Page