Hi everyone,
I’m currently working on a theme built with Sage 10 and attempting to submit it to the official WordPress.org Theme Directory. However, I’ve hit a significant roadblock that I hope the community can help with.
The Problem: Every time I upload the theme zip (approx. 7.9MB), I receive a 504 Gateway Time-out. After discussing this with the WP Meta team (Otto and dd32), they confirmed that the issue isn’t the file size, but the total number of files (over 8,000 files in the vendor directory). The WP.org SVN process chokes and times out before it can complete the commit.
What I’ve tried:
-
Optimizing
.distignore: I’ve excludednode_modules, tests, and various documentation files (README,CHANGELOG, etc.) from thevendorfolders. -
Theme Check: The theme passes the local
theme-checkplugin perfectly. -
Composer: I used
composer install --no-dev --optimize-autoloader.
The Conflict: The WP.org reviewers mentioned that themes with massive vendor folders are rare and difficult to review. They suggested removing unused files, but as we know, with Sage/Acorn, the dependency tree is essential for the theme to function. Since WordPress.org does not run a build process (no composer install on their end), all built assets and dependencies must be included in the zip.
My Questions:
-
Has anyone successfully submitted a Sage 10 theme to the WordPress.org Directory recently?
-
Are there recommended practices for “shaking” or slimming down the
vendorfolder specifically for Sage to make it more “WP-Directory friendly” without breaking Acorn? -
Is there a way to bundle or prefix the dependencies to reduce the total file count?
I am using:
-
Sage version: v10
-
Acorn version: v5
I’ve spent over a week troubleshooting this with the WP team, and it seems like a structural issue between how modern Sage projects are built and how the WP.org SVN handles file counts. Any advice or workarounds would be greatly appreciated!
Thanks in advance!
