定制 springworks/pdf-maker 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

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

springworks/pdf-maker

Composer 安装命令:

composer require springworks/pdf-maker

包简介

PDF creation using api2pdf v2

README 文档

README

PDF creation using the v2 API headless chrome services from api2pdf.com. You can also use Api2Pdf for rendering PDFs in Formie or Craft Commerce.

Requirements

This plugin requires Craft CMS 3.0.0-beta.23 or later.

Formie integration requires Formie 1.5 or later.

Commerce integration requires Commerce 2.0 or later.

Installation

To install the plugin, follow these instructions.

  1. Open your terminal and go to your Craft project:

     cd /path/to/project
    
  2. Then tell Composer to load the plugin:

     composer require springworks/pdf-maker
    
  3. In the Control Panel, go to Settings → Plugins and click the “Install” button for Pdf Maker.

Settings

The only required setting is a valid Api2Pdf API key. It is recommended to set this using an environment variable.

The plugin will automatically detect if either Formie or Craft Commerce is installed and enabled and will offer additional settings to override the PDF generation for these plugins if detected.

Default PDF creation options are set in the config file. Rename config.php to pdf-maker.php and place in your config folder. Change the default options as required.

<?php

return [
    'options' => [
        'pdf' => [
            "landscape" => false, // Set to `true` for landscape PDFs
            "width" => "8.27in", // width of the page in inches
            "height" => "11.69in", // height of the page in inches
            "marginTop" => ".4in", // top margin of the page in inches
            "marginBottom" => ".4in", // bottom margin of the page in inches
            "marginLeft" => ".4in", // left margin of the page in inches
            "marginRight" => ".4in", // right margin of the page in inches
        ],
        'image' => [
            "fullPage" => true,
            "viewPortOptions" => [
                "width" => 1920, // Viewport width in pixels 
                "height" => 1080 // Viewport height in pixels
            ]
        ]
    ]
];

For details of what options are available, please see the following:

Examples

For any of the methods below, you can pass in an options array as hidden inputs in the forms to override the default config options, for example:

<input type="hidden" name="options[landscape]" value="1" />
<input type="hidden" name="options[width]" value="8.5in" />
<input type="hidden" name="options[height]" value="11in" />

Generate PDF from URL

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/pdf-from-url">
    <input type="hidden" name="url" value="https://example.com" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.pdf" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create PDF" />
</form>

Generate PDF from HTML

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/pdf-from-html">
    <input type="hidden" name="html" value="<p>HTML content for PDF</p>" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.pdf" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create PDF" />
</form>

Generate PDF from Template

To generate a PDF from a template, set the hidden template input to the hashed value of the path to the template to render. The path is hashed to prevent it being tempered with in the browser. For example, if you wanted to use a template called page, which lived in a folder called _pdfs in your templates folder, you would set the value of the hidden template to {{ '_pdfs/page'|hash }}.

You can pass variables into the template by setting them as hidden variables[variableName] inputs. Each of these values must also be hashed. So, for example, if your template required an entryId to tell it what entry to render, you could pass that in like this:

<input type="hidden" name="variables[entryId]" value="{{ entry.id|hash }}" />

Full example:

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/pdf-from-template">
    <input type="hidden" name="template" value="{{ 'path/to/template'|hash }}" />
    <input type="hidden" name="variables[entryId]" value="{{ entry.id|hash }}" />
    <input type="hidden" name="variables[someVariable]" value="{{ 'value'|hash }}" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.pdf" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create PDF" />
</form>

Merge PDFs

{% set urls = [
    'https://example.com/one.pdf',
    'https://example.com/two.pdf'
] %}

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/merge">
    {% for url in urls %}
        <input type="hidden" name="urls[]" value="{{ url }}" />
    {% endfor %}
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.pdf" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create PDF" />
</form>

Generate Image from URL

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/image-from-url">
    <input type="hidden" name="url" value="https://example.com" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.png" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create image" />
</form>

Generate Image from HTML

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/image-from-html">
    <input type="hidden" name="html" value="<p>HTML content for image</p>" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.png" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create image" />
</form>

Generate Image from Template

To generate an image from a template, set the hidden template input to the hashed value of the path to the template to render. The path is hashed to prevent it being tempered with in the browser. For example, if you wanted to use a template called page, which lived in a folder called _pdfs in your templates folder, you would set the value of the hidden template to {{ '_pdfs/page'|hash }}.

You can pass variables into the template by setting them as hidden variables[variableName] inputs. Each of these values must also be hashed. So, for example, if your template required an entryId to tell it what entry to render, you could pass that in like this:

<input type="hidden" name="variables[entryId]" value="{{ entry.id|hash }}" />

Full example:

<form method="post" action="" accept-charset="UTF-8">
    {{ csrfInput() }}
    <input type="hidden" name="action" value="pdf-maker/pdf/image-from-template">
    <input type="hidden" name="template" value="{{ 'path/to/template'|hash }}" />
    <input type="hidden" name="variables[entryId]" value="{{ entry.id|hash }}" />
    <input type="hidden" name="variables[someVariable]" value="{{ 'value'|hash }}" />
    
    {# Set the filename (optional) #}
    <input type="hidden" name="filename" value="test.png" />

    {# Redirect to the PDF URL (optional) #}
    <input type="hidden" name="redirect" value="1" />

    <input type="submit" value="Create image" />
</form>

Brought to you by Steve Rowling

springworks/pdf-maker 适用场景与选型建议

springworks/pdf-maker 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 671 次下载、GitHub Stars 达 0, 最近一次更新时间为 2022 年 01 月 22 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「cms」 「Craft」 「craftcms」 「craft-plugin」 「pdf maker」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

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

围绕 springworks/pdf-maker 我们能提供哪些服务?
定制开发 / 二次开发

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

BUG 修复 & 性能优化

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

项目外包 & 长期维护

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

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

统计信息

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

GitHub 信息

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

其他信息

  • 授权协议: proprietary
  • 更新时间: 2022-01-22