Every feature, improvement, and fix since the 3.0 release. ScoopAdmin is actively developed — this page grows with the platform.
.htaccess files that were shipped alongside the live one. for.live_htaccess, https.live_htaccess, local.htaccess, old.htaccess and secure.htaccess are working copies of a server configuration, nothing reads them at runtime, and a docroot that still carries them is publishing a description of its own protection to anyone who asks for the filename. All five are now removed by the housekeeping pass that already prunes stray files from the docroot, and the same list is applied by client setup so a new site never receives them. example.htaccess is the reference copy and is deliberately kept — a site that keeps it should deny it in .htaccess, because nothing else will. A site is cleaned the first time it renders a page on this build, so a host that has not taken this release still carries the files.htaccess template now denies the member data directory by path rather than by file extension. Files written there are stored without an extension, which an extension-based rule cannot match. Sites are covered when they take an updated .htaccess, not on upgrade alone.htaccess template. The endpoint is documented as a public, unauthenticated read API, but the template denied every PHP file and re-permitted only a short list that left this one out — so it answered 404 everywhere, which is why the Workflow Recipes catalog could not load its own catalog. Access is still gated per collection inside the endpoint rather than by the web server: a collection saved as Private answers 403. Note that a collection file created before that flag existed carries no private key and is served as public, so review existing collections before deploying an updated templatedefault.html, which ships as a byte-copy of default.php with the PHP left in it — and a .html file is read rather than executed, so an entry with no SEO file of its own opened the panel with the template’s source code sitting in it, and saving made that the entry’s permanent SEO block. Both tools now resolve SEO the way the public render path does/dbladmin kept a plain-text password on the server for the life of the account. The upgrade runs on the next successful sign-in and costs the user nothing if it failssitemap.xml and AGENTS.md now resolve a page’s SEO settings exactly the way the page itself renders them. Both files reimplemented that lookup and each got it wrong differently, so a page set to noindex could still be listed in the sitemap. All three now share the renderer’s own resolution<style> block inside the template file is compiled, on every page, blog and news save, into theme/css/bands.css and theme/css/areas.css. A component’s styling travels with the single file, so moving a band into another client theme no longer means hunting through a stylesheet for the rules that belonged to it.htaccess check no longer reports a false warning on sites using the current template, and now also flags a docroot where dotfiles or PHP files are not denied</head> tag was emitted into the body of every pageAGENTS.md glued words together across line breaks, and could publish a structured-data organization name in place of the page title. E-commerce front-end endpoints also resolved their includes from the wrong depth/organization/{slug}AGENTS.md or llms.txt naming themselves canonical — a staging copy could point AI agents away from the client’s real domain. Existing files on non-production sites are removed automatically{social_feed:slug} short code/dbladmin/api/v1/ for pages, blogs, news, listings, forms, and the asset file managerAGENTS.md from site content and SEO datallms.txt for LLM and AI model indexingPartner agencies get access to staging releases before they go production-wide. Join the program and help shape what ScoopAdmin becomes.
Become a Partner