=== Aumcreate === Contributors: aumcreate Requires at least: 6.2 Tested up to: 7.1 Requires PHP: 7.4 License: GNU General Public License v2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Tags: custom-background, custom-logo, custom-menu, featured-images, threaded-comments A theme built around the Aumframe visual editor: you design templates, and each template draws every page it matches. == Description == Aumcreate is the front end for designs made in the Aumframe editor. You do not lay out pages one at a time — you design a **template**, give it a rule (the front page, every post in a category, single products, search results, 404), and every page that matches is drawn by that one design. What the theme itself brings: * A day/night palette with a toggle, where both modes are checked for contrast rather than guessed * Site-wide design settings — colours, fonts, container width, logos — that designs read from, so a palette change moves the whole site * No CSS framework and no jQuery on the front end; the only styles are the ones your design compiled to * Menus, widgets, featured images, comments and translation support, all in their usual WordPress places = Aumframe is required for the editor = The theme renders designs; **Aumframe** creates them. Without the plugin the theme still works as an ordinary theme, but there is nothing to design with. Install Aumframe from the Plugins screen. = Optional engines = * **WooCommerce** — shops * **AumNexCart** — a product catalogue with enquiries instead of a checkout * **AumReserva** — appointment booking * **AumViso** — structured data and AI-readable summaries Each is optional. The theme notices which one is active and offers the matching design surfaces; with none of them it is a content site. == Installation == 1. Appearance > Themes > Add New > Upload Theme, or upload the folder to `/wp-content/themes/` 2. Activate it 3. Install and activate the **Aumframe** plugin when prompted 4. Open **AumCreate** in the admin menu to set your palette, fonts and logos == Frequently Asked Questions == = Does it work without Aumframe? = Yes, as a plain theme — your posts and pages render, menus and widgets work. What you do not get is the template designer, which is the reason to use this theme. = Can I still use the block editor? = Yes. On a page that a design draws, the block editor still opens and still stores your content; the design decides where that content appears. Pages no design matches are rendered the ordinary way. = Does it send anything to your servers? = No. The theme makes no requests to aumcreate.com. The one place it looks outward is the plugins screen in its own settings, which asks wordpress.org — through WordPress's own API — whether our free plugins are installed. = Where do the colours come from? = From the theme's settings, as a small set of named tokens (brand, ink, paper, accent…) with a light and a dark value each. Designs refer to the names, so changing a token changes every design that uses it. == Changelog == = 2.16.0 = * 商品目录的抽象层(`AumCreate_Catalog` 和四个引擎适配器 + AumViso 桥,1434 行)搬进 aumframe。 WooCommerce / AumReserva / AumNexCart 的**表现层和 kit 播种留在主题**(1550 行)—— 切开的判据是一个数:搬走的那批调主题函数 0 次,留下的那批调 16 次。 * 需要 aumframe 1.20.0。 = 2.15.0 = * 点赞 / 收藏的存储、AJAX 和按钮标记搬进 aumframe,它们在别人的主题上也能用了。 **作者关注留在主题** —— 它用同一张表,但唯一界面是 `author.php`,那是主题的功能。 * 顺带删掉三个死的 AJAX 端点(`aum_toggle_like` / `aum_toggle_favorite` / `aum_add_comment`), 数过:注册之外零个调用方,和前端真正在用的那三个重复。 * 需要 aumframe 1.19.0。 = 2.14.0 = * 内容模型(自定义类型、分类法、字段,2950 行)搬进 aumframe。 在此之前 kit 里的内容模型**只有装了这个主题才导得进导得出**,而且一声不响。 * 需要 aumframe 1.18.0。 = 2.13.0 = * 表单系统(1592 行 + 32KB 资源)整体搬进 aumframe,不只是注册那一行。 `[aum_form]` 现在在任何主题上都能用。 * 需要 aumframe 1.17.0。 = 2.12.0 = * 后台菜单挪回顶级菜单。2.11.0 把它挪进「外观」的理由是错的 —— **wordpress.org 允许主题 建一个顶级菜单**,那条 requirement 是四条限制(只能一个、子页面建议 ≤3、`$position` 必须是 `null` 或 59、不能和 `add_theme_page` 同时用),不是禁止。 我们原来那个坏在 `$position` 写了 20、子页面 4 个。现在 position 59、子页面 3 个。 * 同套件插件不受影响:它们问 `aumcreate_admin_parent_slug()` 而不是写死。 = 2.11.1 = * 删掉 `inc/libs/class-tgm-plugin-activation.php` —— **3853 行、126 KB,全主题没有一处 require 它**。 它同时是 Theme Check 那条「多个文本域」里 `tgmpa` 的来源,和两条 WP_Filesystem INFO 的来源。 * 修 `search.php` 里 8 个字符串写成 `'aum'` 文本域 —— **那些字符串在任何站上都从来没被翻译过**, 这不只是一条警告。全主题现在只剩 `aumcreate` 和 `woocommerce` 两个域。 * 去掉 `add_filter('show_admin_bar', '__return_false')` —— wordpress.org 明确禁止主题隐藏管理工具条 (那是每个用户在「个人资料」里自己的开关)。只有登录用户看得见它,访客从来看不见,所以对外观感无变化。 * `style.css` 头:`Tested up to` 写成纯数字(`WordPress 6.7` → `7.1`);去掉 `custom-logo` 和 `custom-background` 两个标签 —— 主题并没有 `add_theme_support` 它们,**标签不能claim没实现的功能**。 * 新增 `searchform.php`,把主题自己的搜索表单交给核心 `get_search_form()` 那条链路, 多语言和搜索增强插件才接得到手。 ⚠️ 它**不会**让 Theme Check 那条 `role="search"` 警告消失(实测过:那条是 grep 字符串的)。 == 上架前刻意保留的两条 Theme Check WARNING == 1. **`role="search"` was found in inc/helpers/search.php** —— 警告的实质是「表单绕过了核心的 过滤器链,插件接不到手」。2.11.1 加的 `searchform.php` 解决了实质;那条警告本身是 grep 字符串,不会消失。表单本身要留(下拉框类型来自主题设置,多实例需要唯一 ID)。 2. **File write operations(`inc/catalog/adapters/woo-kit.php`)** —— 写的是 WooCommerce 的下载 保护文件(`index.html` / `.htaccess`),缺了它们 `woocommerce_uploads/` 会被目录列出。 改成不写能少一条警告,但要把一个真实暴露交给「Woo 的 install 一定跑过」这个假设。选择留着。 另外「多个文本域:aumcreate, woocommerce」这条:21 处 `'woocommerce'` **全部在 `woocommerce/` 目录下的模板覆盖里**,那里必须用 Woo 自己的文本域,否则拿不到 Woo 的翻译。这条是本例的误报。 = 2.11.0 = * 主题的后台页从顶级菜单挪进「外观」(wordpress.org 不允许主题建顶级菜单): 外观 → AumCreate / Inquiries / Content Model,表单列表(`aum_form`)也在那里。 * ⚠️ **同套件插件要改一行。** AumViso / AumLang / AumNexCart 把设置页挂在 `add_submenu_page('aumcreate-settings', …)` 上,那个 slug 不再是顶级菜单,它们的页面会 从后台消失**且不报错**。改成 `function_exists('aumcreate_admin_parent_slug') ? aumcreate_admin_parent_slug() : 'aumcreate-settings'` 即可,老版本主题上照样能用。主题这边加了一条警告横幅,会把落空的页面名字念出来。 = 2.10.1 = * `aumcreate_woo_request_is_gated()` 不再进入 WooCommerce 的 `Internal` 命名空间,也不再复制它的 判断规则。改读 aumframe 记下的 Woo 公开信号 `woocommerce_coming_soon_exclude` (`Aumframe\ScreenedRequest::woo_is_gating()`)—— 同样精确到页,而且不会随 Woo 内部改动静默失效。 客户预览链接(`?woo-share=KEY`)那一步仍留在主题里:Woo 的 private link 判断排在那个过滤器之后。 * 需要 aumframe 1.15.1(新增的那个读取口)。 = 2.10.0 = * The head tags this theme stripped on a WooCommerce "coming soon" page are now stripped by the Aumframe plugin instead, and the theme just tells it when a page is screened. Behaviour is unchanged. **Needs Aumframe 1.15.0 or newer**; on an older one those tags come back on screened pages, which means the page's metadata names the content it is hiding. = 2.9.0 = * The last four shortcodes this theme registered — the cart link, the product action button, and the like and favourite buttons — are now registered by the Aumframe plugin. Everything behind them is unchanged and still lives here. **Needs Aumframe 1.14.0 or newer.** * Removed `[aum_comments_section]`. It was registered but never implemented: using it printed the shortcode text onto the page. No template has ever used it. = 2.8.0 = * Removed the stand-in handlers the theme registered for AumViso's shortcodes. Aumframe now does the same thing for any of our shortcodes whose plugin is missing, without a list of names to keep up to date. **Needs Aumframe 1.13.0 or newer.** = 2.7.0 = * The post types and taxonomies your template defines are now registered by the Aumframe plugin instead of the theme, through the same channel added in 2.6.0. Nothing about them changes — same names, same slugs, same labels, same archives — and your content is untouched. Custom fields are still registered here. **Needs Aumframe 1.12.0 or newer**; on an older one those types do not exist, so their admin screens and archive pages are gone until it is updated. = 2.6.0 = * The `[aum_form]` shortcode and the `aum_form` post type are now registered by the Aumframe plugin. Your forms, fields, entries and settings are untouched and still live here — only the two registration calls moved. **Needs Aumframe 1.12.0 or newer**; on an older one the Forms screen disappears, because nothing registers the post type. = 2.5.0 = * The `[aum_search]` shortcode is now registered by the Aumframe plugin. The form itself is unchanged and still comes from this theme — same markup, same dropdown, same script. **Needs Aumframe 1.11.0 or newer.** = 2.4.0 = * Removed the "Clean Up <head>" performance switch. It stripped legacy tags (RSD, Windows Live Writer manifest, shortlink, adjacent-post links, the WordPress version tag) — things wordpress.org considers a plugin's job, not a theme's. It was off by default. If you had it on, those tags come back; a head-cleanup or SEO plugin does the same thing. * "Disable Embed Scripts" no longer removes the two oEmbed discovery links from the document head, for the same reason. It still does what its description says: no `wp-embed.min.js`, and other sites cannot embed your content. = 2.3.0 = * The day/night switch is now rendered by the Aumframe plugin instead of the theme. The setting that turns it on stays here, and the button is the same button. **Needs Aumframe 1.10.0 or newer.** = 2.2.1 = * The audio-field player is now provided by the Aumframe plugin instead of the theme. **Needs Aumframe 1.9.1 or newer.** = 2.2.0 = * Pagination on archive pages is now provided by the Aumframe plugin instead of the theme. It looks and behaves exactly as before — the theme still styles it — but **this release needs Aumframe 1.9.0 or newer**. On an older Aumframe the settings screen says so, and archive pages would show `[aum_pagination]` as text until it is updated. = 2.1.0 = * The theme no longer updates itself. Updates now come from wordpress.org, the same place as every other theme on your Themes screen. * Removed the licence check. It did more than show a notice: until a site was verified, the settings screen forced you onto the licence tab and greyed out every other one — so a site could not reach its own settings. All tabs are always available now. * The "Your template" panel no longer asks our server whether a newer version of your template kit exists. It still shows which kit you have and when it was imported. * Added this readme, and a feed link in the document head. = 2.0.77 and earlier = * These releases predate this readme. Rather than reconstruct their notes from memory they are left unlisted.