MacCMS v10 (magicblack/maccms10): a PHP video CMS you install with install.php

What MacCMS v10 is for, and who actually needs it

MacCMS v10 targets a specific kind of site: a catalogue. The README describes it as a PHP and MySQL site-building system covering video, episodic series, articles, manga, images and site navigation. That list is the product definition. If your content is a set of items with titles, categories, cover images and episode or chapter relationships, the data model is already shaped for you. If your content is something else, you will be fighting the schema.

The audience is the individual site operator. The README repeatedly frames decisions around the station director (站长), and the stated goal is that an ordinary virtual host is enough to build the site, keeping cost low. That is a real constraint, not marketing filler: shared hosting with PHP and MySQL is a different deployment target from a container platform, and it shapes everything from the installer to the caching advice.

It is not aimed at application developers who want a content API to build a front end against. The repository has api.php at the top level, but the README does not describe an API contract, so treat the interface as undocumented.

ThinkPHP 5.x kernel and the template split

The README states that v10 is built on the tp5.x kernel and extends the template processing engine so that the backend program and the HTML templates are separated. In practice this means the PHP application and the theme files live apart, and the repository layout reflects that: application/ holds the code, template/ and theme-request-form/ hold presentation, and vendor/ and thinkphp/ hold dependencies and the framework itself.

The stated benefit is that designers and programmers can work without interfering with each other, and that plain HTML knowledge is enough to produce a personalised site. That claim is worth taking literally: the templating is tag-based, and the README mentions built-in tags and a custom function tag interface. So a theme author writes HTML with tags in it rather than writing PHP. The trade-off is that heavy logic in a template is not the intended path, and complex conditional layouts end up expressed through tags rather than normal code.

The README also mentions a custom collection (采集) function for pulling content in. It describes it as powerful but gives no field mapping, no scheduling rules and no source format. If automated ingestion is central to your plan, budget time to work out its behaviour from the admin interface rather than from documentation.

Installing MacCMS v10 on a PHP and MySQL host

The repository contains install.php at the top level, and the README says the program runs in a PHP and MySQL environment. So the install path is a browser-driven one rather than a command-line one. Upload the files to the document root, then open the installer in a browser. The installer's own form asks for the database connection details and the administrator account. The README does not enumerate the fields or the required PHP version, so check composer.json in the repository root for the dependency constraints before you pick a host.

Once the installer finishes, the two entry points named in the repository layout are the front site at index.php and the backend at admin.php. The README describes the backend module as clear at a glance and simple to operate. What it does not document is what you should do with install.php afterwards. Leaving a reachable installer on a live site is a common mistake, and nothing in the README tells you whether it self-disables, so verify that yourself before pointing a domain at it.

For a first real use, create one category and one entry, then open the corresponding theme file under template/ and change a heading in plain HTML. That single edit exercises the whole chain: the admin writes to MySQL, the ThinkPHP layer resolves the route, the template engine renders your tag markup. If the heading changes on the front page, the separation the README describes is working as advertised.

The licence is the first thing to resolve

The repository metadata reports the licence as NOASSERTION, which means the automated classifier could not map the LICENSE file to a known identifier. There is a LICENSE file in the repository root, so the terms exist; they simply are not machine-readable in the form the tooling expects. That is a practical problem, not a legal one: you cannot answer a compliance question from the metadata alone.

Read the LICENSE file directly and decide whether its terms fit how you intend to run the site. Do not infer the terms from the project's open-source framing, and do not treat the presence of a LICENSE file as confirmation of any particular licence. This article cannot tell you what that file says, because it is not reproduced here.

Where MacCMS v10 breaks down

The most concrete limitation is documentation. The README is a promotional introduction in several languages, not a manual. It does not document rollback, it does not describe an upgrade procedure, and it does not describe the collection feature's configuration. There is a 说明文档 directory in the repository, but the README does not state what is inside it, so you cannot assume it covers the gaps.

The second limitation is the release cadence. The most recent releases are v2026.1000.4056 on 2026-08-19, v2026.1000.4055 on 2026-07-31 and v2026.1000.4054 on 2026-07-17, and the last push to the repository was on 2026-09-18. Version numbers in this format carry no semantic meaning about breaking changes, and the README describes no upgrade path. If you modify core files, you own the merge on every release.

The third is the framework generation. The README states the kernel is tp5.x. ThinkPHP 5.x is an older line, and that matters if your organisation has a policy about supported framework branches. Nothing in the README indicates a migration to a newer kernel.

Finally, this is the wrong tool when you need a headless CMS. If your front end is a JavaScript application consuming JSON, the template-tag model is the opposite of what you want, and the README does not describe a documented API to replace it.

Alternatives and the real difference in approach

The obvious comparison is WordPress. Both are PHP and MySQL, both install through a browser, and both separate themes from backend code. The difference is the data model. WordPress is built around posts, pages and taxonomies, and a video catalogue is assembled on top of that with plugins and custom post types. MacCMS v10 starts from the catalogue: video, episodic series, manga, images and navigation are first-class content types in the product itself, and the README presents the built-in tag system as the way themes read them. If your site is a catalogue, the schema is already there. If your site is a blog with a video section, WordPress fits without a plugin layer.

A second comparison is a static site generator. That approach removes the database and the admin interface entirely and gives you a build step and version control for content. MacCMS v10 goes the other way: MySQL storage, a browser admin, and the README's claim that an ordinary virtual host is enough. Choose based on who edits the content. A static generator suits an editor who is comfortable with git. MacCMS v10 suits an operator who wants a login form and a category tree.

Upgrade cost and what to check before you commit

Upgrades are the ongoing cost. Three releases shipped between 2026-07-17 and 2026-08-19, roughly every two to three weeks, and the last push was on 2026-09-18. At that cadence, a fork of the core becomes expensive quickly. The cheap discipline is to keep your changes in template/ and theme-request-form/ and leave application/ and thinkphp/ untouched, so an upgrade is a file replacement rather than a merge.

The README does not document a database migration step between versions, so you cannot assume one exists. Take a MySQL dump before any upgrade and verify the site afterwards. That is the only rollback mechanism described in the repository.

Before adopting, verify three things in this order. Read the LICENSE file. Check the PHP and extension requirements in composer.json against your host. Then confirm that install.php is removed or unreachable once setup is complete, since the README does not say it disables itself.

Editorial conclusion

Adopt MacCMS v10 if you run a PHP and MySQL host and want a video or manga catalogue with a browser installer and templates you can edit in plain HTML. Do not adopt it if you need a documented public API, a formal upgrade path, or a licence you can read without ambiguity. Before committing, check the LICENSE file in the repository root, confirm your PHP version against composer.json, and test one template edit end to end on a throwaway database.

Frequently asked questions

Official sources

1. Issues
2. magicblack/maccms10 on GitHub
3. README
4. Releases