wpdesk/wp-view 问题修复 & 功能扩展

解决BUG、新增功能、兼容多环境部署,快速响应你的开发需求

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

wpdesk/wp-view

Composer 安装命令:

composer require wpdesk/wp-view

包简介

README 文档

README

Tests Latest Stable Version Total Downloads License

WP View

WP View is a lightweight PHP library for rendering PHP templates. It can be used as a standalone renderer and also provides resolvers for WordPress theme overrides and WooCommerce-style template loading.

Requirements

  • PHP 7.4 or later, including PHP 8.x.
  • Composer.
  • WordPress is required when using WPThemeResolver or PluginViewBuilder.
  • WooCommerce is required when using WooTemplateResolver.

Installation via Composer

Install the package with Composer:

composer require wpdesk/wp-view

Composer autoloads the library with the WPDesk\View\ namespace.

Basic usage

SimplePhpRenderer renders a PHP template resolved by a resolver. The renderer adds the .php extension, so template-name resolves to template-name.php.

<?php

$resolver = new \WPDesk\View\Resolver\DirResolver( __DIR__ . '/templates' );
$renderer = new \WPDesk\View\Renderer\SimplePhpRenderer( $resolver );

$html = $renderer->render( 'template-name', [ 'param1' => 'test' ] );

Inside templates/template-name.php, array keys passed to render() are available as local variables:

<?php echo htmlspecialchars( (string) $param1, ENT_QUOTES, 'UTF-8' ); ?>

Multiple template directories

Use ChainResolver when templates can be loaded from more than one location. Resolvers are checked in the order in which they are added, and the first matching template is used.

<?php

$resolver = new \WPDesk\View\Resolver\ChainResolver(
    new \WPDesk\View\Resolver\DirResolver( __DIR__ . '/templates/overrides' ),
    new \WPDesk\View\Resolver\DirResolver( __DIR__ . '/templates/default' )
);

$renderer = new \WPDesk\View\Renderer\SimplePhpRenderer( $resolver );

$html = $renderer->render( 'template-name', [ 'param1' => 'test' ] );

In this example, templates/overrides/template-name.php is used when it exists. Otherwise, the renderer falls back to templates/default/template-name.php.

WordPress plugin usage

PluginViewBuilder creates a default renderer for plugin templates. It looks for theme overrides first and falls back to templates bundled with the plugin.

<?php

$builder  = new \WPDesk\View\PluginViewBuilder( __DIR__, 'templates' );
$renderer = $builder->createSimpleRenderer();

$html = $renderer->render( 'template-name', [ 'param1' => 'test' ] );

For a plugin directory named example-plugin, the default lookup order is:

  1. Child theme path: example-plugin/template-name.php.
  2. Parent theme path: example-plugin/template-name.php.
  3. Plugin path: templates/template-name.php.

You can also render directly through the builder:

<?php

$builder = new \WPDesk\View\PluginViewBuilder( __DIR__, 'templates' );

$html = $builder->loadTemplate( 'template-name', '.', [ 'param1' => 'test' ] );

WooCommerce templates

Use WooTemplateResolver when templates should follow WooCommerce's template lookup behavior, including theme overrides handled by wc_locate_template().

<?php

$resolver = new \WPDesk\View\Resolver\WooTemplateResolver( __DIR__ . '/templates/' );
$renderer = new \WPDesk\View\Renderer\SimplePhpRenderer( $resolver );

$html = $renderer->render( 'emails/example', [ 'param1' => 'test' ] );

Main components

  • WPDesk\View\Renderer\SimplePhpRenderer renders PHP templates and returns output as a string.
  • WPDesk\View\Renderer\Renderer defines the renderer interface.
  • WPDesk\View\Resolver\DirResolver resolves templates from a directory.
  • WPDesk\View\Resolver\WPThemeResolver resolves templates through WordPress locate_template().
  • WPDesk\View\Resolver\WooTemplateResolver resolves templates through WooCommerce wc_locate_template().
  • WPDesk\View\Resolver\ChainResolver tries multiple resolvers in order.
  • WPDesk\View\Resolver\NullResolver is a resolver implementation that always fails.
  • WPDesk\View\Resolver\Exception\CanNotResolve is thrown when a template cannot be resolved.
  • WPDesk\View\PluginViewBuilder builds the default WordPress plugin renderer.

Development

Install dependencies before running local checks:

composer install

Available Composer scripts:

composer phpcs
composer phpunit-unit
composer phpunit-unit-fast
composer phpunit-integration
composer phpunit-integration-fast

License

This package is released under the MIT License.

wpdesk/wp-view 适用场景与选型建议

wpdesk/wp-view 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 66.67k 次下载、GitHub Stars 达 0, 最近一次更新时间为 2018 年 05 月 18 日, 在 PHP 生态内属于活跃度较高的组件。

我们在过去多个企业项目中使用过 wpdesk/wp-view 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 wpdesk/wp-view 我们能提供哪些服务?
定制开发 / 二次开发

基于 wpdesk/wp-view 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 66.67k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 0
  • 点击次数: 12
  • 依赖项目数: 17
  • 推荐数: 0

GitHub 信息

  • Stars: 0
  • Watchers: 0
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2018-05-18