values to a displayable caracter. Have a look at the ASCII encoding table
for example and you'll see that many byte values do not map to any caracter
at all or map to non-displayable caracters such as \0, TAB or BEEP. So you
need to use a caracter encoding that can map every possible byte value to a
displayable caracter. Fortuanately, there is one and it's called Base 64.
Have a look at Convert.ToBase64String()."
new instead of statics, but now my wpdb extension classes is getting invalid SQL strings (truncated) in the same scenario
I am an armature .net developer/student. I make small scale websites to fund my education. One of my clients' requirements was to have a website for himself in .net core, he has no knowledge of .net or HTML so I decided to make it in WordPress as it requires no to very little knowledge of web development.
Earlier this month I came across peachpie and was stunt just by imagining the limitless possibilities. I have forked peachpie and WpDotNet from Github and was able to run WordPress on it. But as I went on adding the plugins I got into errors.
I needed help with documentation and how to go about migrating WordPress to this environment and PHP error solutions. Where will I find help?
Another thing I would like to know which one is better for WordPress and what is the difference between PeachPie and WpNotNet.
Moreover, when can we expect Peachpie 1.0 to be out? Can't wait to try it out!
- don't use any async code, you'll exhaust your threadpool eventually, there's no 100% safe way to wait on async in a sync context
- define all the constants that stop wordpress from trying to background update
- when using Microsoft's docker images as a base be sure to install timezone data
- if you instantiate an instance of a class exposed as a [PhpType] from C# and pass it back to PHP it's use is unstable
- should not be true, but it is more related to .NET itself and how you use your async methods. If done correctly the result is exactly the opposite - you'd need fewer threads.
- do you have a list of those constants? we will add them to wpdotnet by default
- timezone data are missing just on Linux images, right? Although we should be able to add them even on Linux, please file an issue on https://github.com/peachpiecompiler/peachpie/issues that
timezone_identifiers_list(or something else?) does not return your expected timezones. - instantiating PHP class from within C# should work fine, do you have an example of this unstable behavior? It is important to pass current
Contextobject to its constructor which might be confusing.
- is definitely true, it's not a peachpie issue, it's a .net issue, even MS don't have a method that works 100% of the time
- the constants are documented here: https://make.wordpress.org/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7/
- it's not really a peachpie issue, is it?
- I didn't have access to
Contextin the scope of what I was doing, the requirement seems a bit odd
Context is an odd thing; however internally PHP is bound to a request, and a lot of functionality depends on it. So objects need to know the Context which is like the request owning the object. If not provided, a default Context for current Async-Local is used. This behavior can be customized tho
<Project Sdk="PeachPied.WordPress.Build.Plugin/1.0.0-beta992">
<PropertyGroup>
<WpContentTarget>themes</WpContentTarget>
<TargetFramework>netcoreapp3.1</TargetFramework>
</PropertyGroup>
</Project>
@jakubmisek It started working after a machine reboot. Thanks!
`dotnet new mvc -au None
dotnet add package PeachPied.WordPress.AspNetCore -v 1.0.0-beta992
$theme = "nisarg"
$themeVersion = "1.2.9"
$url = "https://downloads.wordpress.org/theme/$theme.$themeVersion.zip"
$zip = "$PSScriptRoot\$theme.$themeVersion.zip"
$target = "$PSScriptRoot\Themes"
$msbuildpath = "$PSScriptRoot\Themes\$theme"
$localNugetDir = "C:\Projects\local\nugets"
(New-Object System.Net.WebClient).DownloadFile($url, $zip)
Expand-Archive -Path $zip -DestinationPath $target
$xml = '<Project Sdk="PeachPied.WordPress.Build.Plugin/1.0.0-beta992"><PropertyGroup><WpContentTarget>themes</WpContentTarget><TargetFramework>netcoreapp3.1</TargetFramework></PropertyGroup></Project>'
New-Item -Path $msbuildpath -Name "nisarg.msbuildproj" -ItemType "file" -Value $xml
cd $msbuildpath
dotnet build
dotnet pack
cd ..
cd ..
Move-Item -Path "$msbuildpath\bin\debug\$theme.$themeVersion.nupkg" -Destination "$localNugetDir\$theme.$themeVersion.nupkg"`
<?php /* Template Name: Example Template */ ?>? Extra variations of a page template. They don't seem to appear in the WP admin / Edit Page / Page Attributes Section. Any thoughts?
<PackageOutputPath>local/nuget/path</PackageOutputPath> or you don't have to call dotnet build, just dotnet pack is sufficient
@jakubmisek, Sorry, I should have clarified my question :) I fully understand that no changes to the theme/templates can be made after it’s been compiled. Everything has to be compiled. I 100% agree/understand.
I defined 5 custom templates pages (variation of the original page.php) within my theme before the theme was compiled. These pages all have the standard WordPress comment header <?php / Template Name: Example Template / ?>. Each with a different template name. However, these pages aren’t appearing in the WP admin / Edit Page / Page Attributes Section after the theme has been compiled, referenced, and activated. Everything else about the theme appears to work including the original page.php.
I’ve inspected the compiled nuget using JetBrains dotPeek, and I see all the pages listed in the compiled assembly including the extra template pages I defined. Is this a known issue or bug, or is there another process for defining extra page templates within a theme for PeachPied.WordPress? Thanks