I wasn't even aware I wrote the binary for 7.3; maybe I can correct that 🙈

    • [deleted]

    • Post #100

    luceos Given Flarum requires 7.3 minimum, I think it makes sense that Extiverse is the same, no ?

        • [deleted]

        • Post #102
        • Edited

        luceos 7.3 actually from recollection.... I could well be wrong though. If you're using composer 2.0 then you'll get a message stating you need 7.3 minimum

          luceos Oh please, if you can correct that.
          I'm using VestaCP on my vps, It is using PHP 7.2 so it is gonna be impossible for me to update PHP version unless VestaCP does it.

          [deleted] Thanks for your reply but I needed and had been waiting for your reply in another post here

                HD3D Oh please, if you can correct that.

                It won't be possible to change the php requirement for the helper as pointed out luceos . This is because the binary is created based on the latest Laravel Zero scaffolding and Laravel 8+ components.

                • HD3D replied to this.

                      luceos So is there no way left for me to use extiverse? That's a shame because I don't want to mess up during flarum update as I'm still on beta 13

                          I get:

                          PS C:\xampp\htdocs\flarum_extiverse_helper> php extiverse upgrade --path C:\xampp\htdocs\flarum

In Local.php line 135:

  file_put_contents(C:\xampp\htdocs\flarum\composer.json.back-2020-12-24T18:05:16+00:00):
  failed to open stream: No such file or directory

                          I think the filename composer.json.back-2020-12-24T18:05:16+00:00 that it tries to create is not a valid windows filename because it contains :

                          Hi,
                          is it better to upgrade to beta15 with php extiverse upgrade or manually?
                          Thank you.

                          • ctml replied to this.

                            Gatsu up to you, I prefer using extiverse as it takes care of extension compatibility and points out any potential issues for you.

                                ctml I have beta13. Can extiverse automatically upgrade beta13 to beta 15?

                                    Gatsu yes and it will give you feedback interactively. Always make sure to make a backup though, no matter what method you use.

                                        5 days later

                                        I've been encountering this error when attempting to use the upgrade feature (from beta13).

                                        Updated composer.json with wildcard extension constraints.

In Process.php line 1201:
                                                                                                         
  The process "/usr/sbin/composer update --prefer-dist --no-dev -a" exceeded the timeout of 60 seconds.

                                        I expect it's a server-related setting that needs tweaked, but unsure what setting might need adjusted. I thought maybe max_execution_time, but running php -i shows that it is set to 0. Any thoughts on how I can get past this? TIA!

                                          UaMV try composer config --global process-timeout 1000

                                          • UaMV replied to this.

                                              ctml still encountering the same after running that.

                                              • ctml replied to this.

                                                  UaMV ah sorry, I was going based off memory as I had run into the same issue with composer when I upgraded the other week. the above was one of my tests that did not work. I believe this is the thing that did the trick for me, add "process-timeout": 0 in your composer.json under the config block.

                                                  "config": {
    .....
    "process-timeout": 0
},
                                                  • UaMV replied to this.