PHP version change not working

Wappler Version : 7.7.1
Operating System : win 11
Server Model: PHP
Database Type:
Hosting Type: wappler server

Expected behavior

What do you think should happen?

Version should change

Actual behavior

What actually happens?

Error

I was pllaying with the new platform change feature and converted the same dashboard project to php.
I got this error:
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires phpunit/phpunit ^12.0 -> satisfiable by phpunit/phpunit[12.0.0, ..., 12.5.11].
- phpunit/phpunit[12.0.0, ..., 12.5.11] require php >=8.3 -> your php version (8.2; overridden via config.platform, actual: 8.1.31) does not satisfy that requirement.

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.
Error
Error Installing PHP Packages!

I tried changing to PHP latest

but get an error
Updating Scoop...
git: 'remote-https' is not a git command. See 'git --help'.
ERROR Update failed.
PHP installation failed!

log file:
wappler.zip (3.3 KB)

Any update @Teodor, still getting this error when switching PHP version

Video and logfile (now on 7.7.3)

wappler.zip (3.2 KB)

Bump

For info, did full clean install, still seing this error:

aha this is something new, try the following commands in a cmd window:

git -v

where git

E:\webs\php extension repository>git -v
git version 2.53.0

E:\webs\php extension repository>where git
C:\Users\brian\AppData\Local\Wappler\resources\app\Shared\DMXzone\dmxAppCreator\UI\bin\win64\usr\bin\git.exe

Any ideas on what i can do to fix this @George , even if manual fix pending wappler fix. I cant run local server or Wamp so totally locked out of php.

the git issue is now fixed with the last Wappler update 7.7.5

So install it and try again

1 Like

Thanks George, hadn't actually been home since the update, just didn't see it marked as fixed and assumed it was still outstanding.
Can confirm issue seems fixed.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.