You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebAssembly WordPress applies a few WordPress patches once it's started. The method is quite peculiar – a PHP code snippet reads these files from the in-memory filesystem, runs some str_replaces, and then writes these files back:
The bundling pipeline could be updated to also apply a few .patch files to WordPress. This way, WebAssembly environment would already boot with the patched version.
The text was updated successfully, but these errors were encountered:
36013ef switched from patching WordPress with eval() to JavaScript function calls. WordPress build pipeline exists in prepare-wordpress.sh and can be updated to apply arbitrary patches when needed. However, at the moment, patching via JavaScript seems to be fine.
What problem is this issue looking to solve?
WebAssembly WordPress applies a few WordPress patches once it's started. The method is quite peculiar – a PHP code snippet reads these files from the in-memory filesystem, runs some str_replaces, and then writes these files back:
https://github.com/adamziel/wordpress-wasm/blob/9d04a113a97f53a1303fefba642f65f1b5a5a5f6/src/shared/wordpress.mjs#L128-L137
How does this issue proposes to solve it?
The bundling pipeline could be updated to also apply a few .patch files to WordPress. This way, WebAssembly environment would already boot with the patched version.
The text was updated successfully, but these errors were encountered: