jakubmisek on master
realpath() fixes fixes https:/… (compare)
jakubmisek on master
SimpleXMLElement respects not e… (compare)
newinstead of statics, but now my wpdb extension classes is getting invalid SQL strings (truncated) in the same scenario
timezone_identifiers_list(or something else?) does not return your expected timezones.
Contextobject to its constructor which might be confusing.
Contextin the scope of what I was doing, the requirement seems a bit odd
Contextis 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
Contextwhich 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
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 packis 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