-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the process for updating wp-a2z.org #1
Comments
A couple of problems detected when processing the Genesis theme framework. Consequently, when files are being extracted from the zip file we get prompted about file replacement.
|
Extracting wordpress from wordpress.zip puts the files into the wrong directory - |
…z; use rename before and after unpack
I need to add some logic to prevent a true source repository from being updated from the runtime version. |
Also, update the logic to be able to use oik autoload when slog and/or slog-bloat are activated. slog uses shared library autoloading. |
I had a problem trying to update Gutenberg to 10.6.0-rc.1 from the zip file downloaded from GitHub. Perhaps the extract process should use a separate directory for the extraction and then move the extracted files taking into account the directory structure that's been created. |
I'm not going to close this yet. Using the Requirement
Proposed solutionFor plugins:
For themes: tbc |
I need to improve the method whereby updates to plugins and themes can be applied to wp-a2z.org efficiently. A time consuming part of the process has been downloading the latest runtime version of a component, extracting it to the WP-a2z repository, updating the repository and then running the batch process to rebuild the API reference.
This issue is to document the requirements and solution for building the API reference for the existing plugins and themes.
The logic has to cater for exceptions such as:
wp-a2z
.wp-a2z
has some hand cranked files:README.md
and.gitignore
The text was updated successfully, but these errors were encountered: