Libraries tagged by ndit

Every freelancer's dream just came true, as we've made T3 freelancer, Free TYPO3 Portfolio Template! Live-Demo: https://demo.t3terminal.com/?theme=t3t-freelancer PRO-version: https://t3terminal.com/t3-freelancer-free-typo3-portfolio-template

Go to Download

Agency TYPO3 template is an ultimate tool to kickstart your project, either a software development company, or a product startup or any new business. Live-Demo: https://demo.t3planet.com/?theme=t3t-agency PRO version: https://t3planet.com/t3-agency-free-business-typo3-template/

Go to Download

Are you facing speed and performance issues on your TYPO3 website? If yes, then install our ns_lazy_load plug-and-play extension, which can reduce HTTPS request mechanism and improve your loading time.

Go to Download

TYPO3 Event Manager - Event Manager is a full-featured events management extension that lets you create multiple events and get them listed on your website. Event Manager provides a user-friendly interface that allows you to effortlessly create and customize events.

Go to Download

Backup Plus - Easily backup your entire TYPO3 website. The Backup Plus extension for TYPO3 lets you save your code, files, and database with just a few clicks. Install Backup Plus and connect it to your cloud storage (like Google Drive, Dropbox, Amazon S3, SFTP, Rsync, etc.).

Go to Download

Yet anoyther object relational mapper

Go to Download

Xmpp bot client for Laravel PHP framework

Go to Download

NitroPHP — a lean, fast, Laravel-shaped PHP framework.

Go to Download

An XML driven simple database solution for projects where SQLite is not available and MySQL seems overpowered.

Go to Download

A laravel dependable soft delete package

Go to Download

Brings PHPTAL to Laravel

Go to Download

Zend Framework 2 ZfcUser LDAP Authentication

Go to Download

T3AI – TYPO3 AI Integration Extension

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

Extended nette/sandbox with integrated gulp, es6, nittro, sass, browsersync, ...

Go to Download