I download 6 beta and try to test it but local server dont work.
I get this on console:
And on browser preview get this
Warning : Unknown: failed to open stream: No such file or directory in Unknown on line 0
Fatal error : Unknown: Failed opening required ‘/Applications/Wappler’ (include_path=’.:/usr/local/Cellar/php/7.4.4/share/php/pear’) in Unknown on line 0
Any idea??
Where is your Wappler folder?
I had some issues with path folder because previous beta versions were installed on local folder instead roaming.
I don’t know if that was fixed for beta 8 and if has something to do with your issue.
I am on Mac so is on applications folder.
Any advice @George
How is your project defined exactly? What are the project settings for general and what are for the development target?
I just setup with your advice to test Beta 6 and project was imported directly from 5. On Wappler 5 works fine but if I run the 6 generates me the error.
If I turn on the computer and run first the Beta 6 I need to restart and run Wappler 5 first on computer in order to work.
If I run Wappler 5 and close it and then try to run the beta 6. I click on the beta Icon as a separate app and it opens the wappler 5 instead of 6 that I click on.
Here is a screen for the targets
That is because you need to quit Wappler before running the other version!
You need to quit Wappler from the tray icon
Mac OS:
Windows:
And then run the beta. No need to restart the computer every time!
Ok the restart problem is solved but when I open the version 6 still getting this error
[Wed Sep 13 11:01:13 2023] PHP 7.4.4 Development Server (http://localhost:3000) started
[Wed Sep 13 11:01:14 2023] [::1]:54679 Accepted
[Wed Sep 13 11:01:14 2023] PHP Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
[Wed Sep 13 11:01:14 2023] PHP Fatal error: Unknown: Failed opening required '/Applications/Wappler' (include_path='.:/usr/local/Cellar/php/7.4.4/share/php/pear') in Unknown on line 0
[Wed Sep 13 11:01:14 2023] [::1]:54679 ClosingWell, I’m having the same issue too.
W10 Version 6.0.0 Beta 8
Checking PHP installation and version...
PHP 8.2.10 (cli) (built: Aug 29 2023 21:51:44) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.2.10, Copyright (c) Zend Technologies
PHP is correctly installed.
Checking PHP Composer installation and version...
Composer version 2.6.2 2023-09-03 14:09:15
PHP Composer is correctly installed.
Check completed successfully...
Checking PHP installation and version...
PHP 8.2.10 (cli) (built: Aug 29 2023 21:51:44) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.2.10, Copyright (c) Zend Technologies
PHP is correctly installed.
Checking PHP Composer installation and version...
Composer version 2.6.2 2023-09-03 14:09:15
PHP Composer is correctly installed.
Check completed successfully...
But on browser:
The react icon got me thinking on port issues.
I think changing (or removing) the port doesn’t really change as:
Also notice the Test connection brings that error prompt.
Last:
Stoping server returns:
Error: Channel closed at __node_internal_captureLargerStackTrace (node:internal/errors:477:5) at new NodeError (node:internal/errors:387:5) at target.send (node:internal/child_process:742:16) at PtyEmitter.destroy (C:\Users\Fran\AppData\Local\Wappler Beta\resources\app\Shared\DMXzone\dmxAppCreator\UI\lib\pty.js:7:1490) at PtyEmitter.<anonymous> (file:///C:/Users/Fran/AppData/Local/Wappler%20Beta/resources/app/Shared/DMXzone/dmxAppCreator/UI/w2editor_term.js:7:8093) at PtyEmitter.emit (node:events:513:28) at ChildProcess._exitHandler (C:\Users\Fran\AppData\Local\Wappler Beta\resources\app\Shared\DMXzone\dmxAppCreator\UI\lib\pty.js:7:849) at ChildProcess.emit (node:events:513:28) at ChildProcess._handle.onexit (node:internal/child_process:291:12)
@Teodor
I found that Wappler was running with no administrator privileges.
Changed that, Wappler runs with administrator mode now, but I have some cmd process without that.
Sometimes I opened Wappler and starts running some cmd on the backend and then closes and starts Wappler normally.
My question is, besides Wappler, can be there some task running with no admin privileges?
(That doesn’t fix the bug btw)
How to solve this on Mac??
Bump…
Found the problem, was indeed in the Wappler beta only, we just had some path escaping issues, will be fixed in the next beta.
I found that is only on PHP project. Over node JS works fine.
Yes this applies only for the local php server
Fixed in Wappler 6 beta 9
