Download the PHP package magna-cms/blog without Composer

On this page you can find all versions of the php package magna-cms/blog. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package blog

Magna Blog

A blog plugin for Magna CMS, the open-source Laravel headless CMS — public post pages through Magna Pages, and a delivery API for headless frontends.

Magna CMS

Magna Blog is a plugin for Magna CMS. It manages blog content through the Magna admin panel using an Editor.js block editor, and exposes a read-only delivery API for any frontend — a headless site, a static build, or a native app.

With Magna Pages installed, every published post is also served as a page of your site, at its permalink and inside your theme's layout. Without Pages the blog stays headless: it owns authoring, organisation and delivery, and presentation is left to your frontend.


Screenshots

The full-screen post builder

An Editor.js canvas beside a tabbed sidebar for post settings, block settings and SEO.

Blocks and paragraph templates

Insert from the block toolbox, then restyle the selected block from the Block tab — thirty-six paragraph treatments, all sanitised server-side, no CSS required.

Posts

Every post with its category, status, visibility, author and schedule, filterable and searchable.

Per-post SEO

With the optional Magna SEO plugin installed, each post gains a search-appearance panel: SEO title, meta description, canonical URL, focus keyword, robots directives and social cards.

Settings

General, slugs, permalinks, editor, fonts, content, custom fields and comment options — all in the admin panel.


Overview

Features

Requirements

Installation

Magna Blog is installed from the Plugin Marketplace inside Magna CMS — no Composer commands, no manual file copying, no build step.

  1. Sign in to your Magna CMS admin panel.
  2. Go to Plugins → Add New Plugin.
  3. Find Magna Blog in the marketplace and click Install.
  4. Activate the plugin when the install finishes.
  5. Open Blog → Posts and write your first post.

Updates arrive the same way: when a new version is published, the Plugins page shows it under Update Available.

Configuration

Backend and content settings are edited from Admin → Blog → Settings (general, slugs, permalinks, editor, fonts, content, custom fields and comments). Infrastructure options — the comment spam driver and reaction types — live in config/blog.php and are environment-driven:

Usage

Create and manage posts from Admin → Blog. The full-screen builder pairs an Editor.js canvas with a tabbed sidebar for post settings, block settings and (when the Magna SEO plugin is installed) SEO.

Artisan commands

Command What it does
php artisan blog:import-wxr <file> Import posts, categories and tags from a WordPress WXR (.xml) export
php artisan blog:export [--out=<file>] Export all blog content to a JSON bundle (default storage/app/blog-export.json)
php artisan blog:import <file> Import a JSON bundle created by blog:export (idempotent, matched by slug)
php artisan blog:reindex Rebuild the search index column for all posts
php artisan blog:publish-scheduled Publish scheduled posts whose date has passed (runs every minute via the scheduler)
php artisan blog:flush-views Save buffered view counts to the database (runs every five minutes via the scheduler)

Public post pages

With Magna Pages installed, each published, public post is served at the Permalink pattern set in Blog → Settings (default /blog/{slug}), inside the site's layout, with the post's title and description as the page's meta. For the /blog listing, place the Blog posts block on a Pages page.

Known limits

Editor

Content is authored with Editor.js and stored as a structured block document. The tool set is open for extension without modifying this plugin — register a tool before an editor mounts:

Server-side security allowlists (block types, templates, code languages, social networks) live once, in PHP, and are shared by the sanitiser and renderer. See docs/adding-a-block.md for the full block-authoring checklist.

API

The delivery API is auto-prefixed at /api/v1/blog/ and protected by the magna.api middleware (delivery-token auth with per-token rate limiting). Only published, public posts are ever returned.

Method Path Returns
GET /api/v1/blog/posts Paginated, filterable, searchable list
GET /api/v1/blog/posts/{slug} A single published public post
GET /api/v1/blog/categories The category tree with post counts
GET /api/v1/blog/tags Tags with post counts
GET /api/v1/blog/posts/{slug}/comments Approved comments (threaded one level)
GET /api/v1/blog/posts/{slug}/comments/stamp A signed _ts for a comment form (no-store)
POST /api/v1/blog/posts/{slug}/comments Submit a comment for moderation
POST /api/v1/blog/posts/{slug}/reactions Toggle a reaction

Responses are frontend-agnostic and never expose internal fields (password hashes, soft-delete state). Fields are only ever added: since 1.2.0 a post also carries summary (its excerpt, else one generated from the body) and url (its public, language-prefixed path). Since 1.2.1 adjacent prev/next stay in the post's own language, and each entry in translations carries the url it is served at.

Comment bot check. Fetch GET …/comments/stamp when your comment form is shown and send the returned _ts with the submission. A stamp younger than blog.comments.min_submit_seconds (default 2) is treated as a bot and quietly not stored. The unsigned form_started_at field is deprecated: it is still honoured (it can only make a submission look automated, never admit one) and will be removed in 2.0.

Permissions

Per-record post actions follow a permission-plus-ownership rule: an author acts on their own posts, while blog.posts.edit-others lifts the ownership restriction for editors and administrators.

Content blocks

The editor ships a broad block set, including paragraph (with visual templates), headings, lists, checklists, quotes and pullquotes, tables, code, callouts, CTAs, buttons, FAQ, details, galleries, cover, image, video and audio, embeds, maps, social icons, footnotes, RSS, table of contents, related posts, group and columns layouts, and dynamic post blocks (excerpt, featured image). Every block is validated server-side before it can be persisted.

Contributing

Working on the plugin itself (rather than using it) needs Node.js, because the editor bundle is a build artifact:

Testing

The plugin ships an extensive Pest suite (feature and unit) that runs inside a Magna CMS application.

Security

Content is protected in depth: an allowlist sanitiser cleans every Editor.js block before it is persisted, and the renderer escapes on output. Outbound editor requests (link preview, RSS) are SSRF-hardened with special-use IP-range blocking and connection pinning. CSV export is protected against formula injection, imports parse XML with network access disabled, and per-record authorisation is enforced server-side on every mutation.

To report a security issue, please contact the Magna CMS maintainers privately rather than opening a public issue.

Changelog

See CHANGELOG.md.

License

Magna Blog is open-source software licensed under the MIT license.


All versions of blog with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
magna-cms/plugin-sdk Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package magna-cms/blog contains the following files

Loading the files please wait ...