Libraries tagged by html code to image

tecnickcom/tc-lib-barcode

305 Favers
9556656 Downloads

PHP library to generate 73 types of linear, 2D and postal barcodes as SVG, PNG, HTML or GD images

Go to Download


jeffersongoncalves/laravel-html-sanitizer

1 Favers
1078 Downloads

This Laravel package provides a simple wrapper around the Symfony HTML Sanitizer to safely clean untrusted HTML. It strips scripts, inline event handlers, and Alpine attributes while keeping the presentational subset (headings, lists, tables, code blocks, images, links) that rendered Markdown and READMEs need. The package is easy to install and configure, seamlessly integrating with your existing Laravel application.

Go to Download


asignua/filament-rich-editor-toolkit

1 Favers
273 Downloads

Ten independent plugins for the Filament 5 RichEditor (TipTap): PasteCleanPlugin removes Word and Google Docs junk (mso-* styles, fonts, colour spans), can upload the pictures of such a paste instead of dropping them (SSRF-guarded) and, in strict mode, cuts a paste down to the field's toolbar, LinkOptionsPlugin sets rel (nofollow, sponsored, ugc) and new-tab options on links, CustomAttributesPlugin keeps class, id, style and data-* attributes both in the browser and through the server sanitizer, EmbedPlugin allows safe iframe and video embeds from an allow-list, ImageUrlPlugin inserts an image by URL, ImagePropertiesPlugin adds alt text (with decorative images), captions and alignment to images, FullscreenPlugin adds a fullscreen mode, SourceCodePlugin adds an HTML source view, CharacterCountPlugin and the RichTextLength rule count and limit plain-text characters and words, and StickyToolbarPlugin keeps the toolbar visible on long content, even inside sections, tabs and repeaters.

Go to Download


aspose/aspose-email-cloud

2 Favers
146 Downloads

This repository contains Aspose Cloud SDK for PHP source code. Aspose Cloud SDK for PHP lets PHP developers convert and process a variety of file formats in the cloud quickly and easily.

Go to Download


componist/code-block

0 Favers
0 Downloads

Laravel client for Template Archive API – fetch code blocks, categories, template images and write Blade templates to resources/views/pages

Go to Download


apiverve/htmltoimage

0 Favers
2 Downloads

HTML to Image is an HTML to image API that renders HTML code into a high-quality PNG image. Paid plans add custom dimensions and JPEG or WebP output.

Go to Download


superipey/phpword

1 Favers
100 Downloads

Based on PHPOffice/PHPWord, some code modification for Any Image in Document to be recognized in TemplateProcessor

Go to Download


katoga/texy-minified

1 Favers
1177 Downloads

Texy converts plain text in easy to read Texy syntax into structurally valid (X)HTML. It supports adding of images, links, nested lists, tables and has full support for CSS. Texy supports hyphenation of long words (which reflects language rules), clickable emails and URL (emails are obfuscated against spambots), national typographic single and double quotation marks, ellipses, em dashes, dimension sign, nonbreakable spaces (e.g. in phone numbers), acronyms, arrows and many others. Texy code can optionally contain HTML tags. Minified version.

Go to Download


zactonz/zactonz-php

0 Favers
3 Downloads

Official PHP client for the Zactonz REST APIs: QR codes, barcodes, screenshots and PDFs, social card images, image conversion, link previews, web page to Markdown, DNS, SSL, WHOIS, email checks and translation.

Go to Download


matthewbaggett/docker-api-php-client

0 Favers
7 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


leibbrand-development/php-docker-client

0 Favers
30 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


magepal/magento2-checkout-success-misc-script

29 Favers
19328 Downloads

Add Miscellaneous HTML and JavaScript codes to Magento2 checkout confirmation page

Go to Download


aleron75/webgriffe_tph-pro

9 Favers
107 Downloads

An enhanced Template Path Hints extension for Magento that inserts references to used Magento Blocks inside HTML code, avoiding the usage of the more invasive built in Template Path Hints.

Go to Download


ecomdev/magento-translate-tool

8 Favers
6 Downloads

Magento translation tool that utilizes PHP Tokenizer in order to generate csv files from PHP, XML, PHTML code

Go to Download


webmaster-ramos/module-google-tag-manager

0 Favers
1 Downloads

Google Tag Manager container loader for Adobe Commerce and Magento Open Source, Luma and Hyva. Loads the container only on listed production hosts, so staging and local copies of the production database send no hits or test orders. Hands the CSP nonce to gtm.js and to Custom HTML tags, so tags keep working on the strict-CSP checkout of Magento 2.4.7 and later. Sets Google Consent Mode v2 defaults before the container loads (denied in the EEA, UK and Switzerland) and updates them from Magento's cookie notice or leaves updates to an external consent platform.

Go to Download