@MuriloPazzini the long loading is caused by port 44344 which is your server not listening on (probably).
Isn't it possible you have the wrong port number in the configuration?
- https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-5.0&tabs=visual-studio#port-configuration
- or https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-5.0#https_port
Asp.net core might automatically redirect you there
The app is only an empty asp.net core project with dotnet wordpress and I followed all the configuration and works fine locally, so I don't have the section https_port in my appsettings.json and the Program.cs is the default one.
@MuriloPazzini so the WordPress was installed on IIS already, with a wrong URL in DB.
Usually, site admins are forcing SITEURL and HOMEURL constants to override this settings (it also improves performance), the constants can be set in appsettings.json (or appsettings.production.json etc.)
https://github.com/iolevel/wpdotnet-sdk#appsettingsjson
I've got another odd issue that I can't seem to track down. The application i'm porting contains some quasi-restful endpoints written using laravel. I've got most of it working, but the endpoint returns the contents of the cached services.php before the actual json response every time. After inserting a bunch of echo statements, I tracked it down to this code:
/**
* Get the returned value of a file.
*
* @param string $path
* @return mixed
*
* @throws \Illuminate\Contracts\Filesystem\FileNotFoundException
*/
public function getRequire($path)
{
if ($this->isFile($path)) {--> return require $path;
}
throw new FileNotFoundException("File does not exist at path {$path}");
}The $path in this case is not compiled, it's on the filesystem. The output into the response stream looks like a dump of the variable returned by the loaded script, not the literal contents of the file because the file has a <?php tag, but the output doesn't.
Any idea what's happening here?
1.0.0 the compiler does not compile on the fly, so everything has to be pre-compiled. The use of readfile() was not the luckiest choice here. The recommendations are:- compile files you want to be compiled, including the one passed to
$path - watching Visual Studio's Output Window when debugging, where all the PHP/PeachPie notices and warnings are printed.
bzcompress is not (yet) implemented in peachpie. Since everything is in managed code, even extensions have to be reimplemented and native PHP DLL's cannot be loaded.PeachPie will notify you about the unknown function in compile-time in advance:
warning PHP5006: Call to undefined function: 'bzcompress'Namespaces are taken into account.
@jakubmisek I managed to put together a working docker-compose for the peachpie-wordpress app. For anyone interested, i forked the repo and added a 'docker' branch: scrawlon/peachpie-wordpress
The 'dotnet watch run' command executes in the container, so you need to view the container log to see when it's "ready".
Hi, newbie student here tasked with a peachpie investigation.
Would like guidance regarding the installation of the WordPress plugin "WooCommerce." I have successfully added other smaller php plugins and themes, in a separate php class lib as shown in a few available demos.
However when attempting to compile WooCommerce, I run into several Type name 'SomeClass' could not be resolved. errors.
This does make sense, because grepping through the the WooCommerce directory confirms that several of these classes are referenced but are not defined, which seems rather perplexing to me. I made doubly sure that all the files were available.
Any guidance would be appreciated. Thanks!
- Either exclude the files that won't compile in case they are not actually used. Usually, you can safely exclude test files, or files that are included conditionally but the condition never happens.
- and/or add missing sources that define those missing classes/interfaces.
