Additionally, all importers were removed with the exception of the importer that handles files generated by the native WordPress exporter2. Other items removed include the Google Gears plugin3, as well as any "auto-upgrade" "features" that any self-respecting citizen of the republic would neither need nor want to use.
This patch was first published and announced in #trilema last week but has since been reground to fit on top of hanbot's latest. Overall this patch proved to be an effective first step in mp-wp's healthy new lifestyle, resulting in a 14% reduction in total LOC and an 18% reduction in size-on-disk (21% when comparing gzipped directories).
|Lines of Code||162,594||139,205||14.4%|
|Bytes on Disk||6,053,039||4,962,628||18%|
Patch and Signature
- The acronym omits what you really get, which is typically HTML tag spew in the generated output. [↩]
- This may be worth removing later but I chose to leave it in for now so that one can at least export and re-import their existing mp-wp blog—and to keep as a reference in case someone eventually decides to re-write this functionality. [↩]
- Some local caching scheme that they in any case gave up on in 2011. [↩]
MP-WP's "native" exporter/importer is a very sad pile of xml, which is not practically useful (the files generated end up too large on non-trivial blog for the php-based importer to be able to import) and incomplete (images, for isntance, are not included, thus you're still stuck bashing the server into obtaining a proper, useful archive).
The only sane way to import/export MP-WP blogs is by doing a db dump of the tables and taring its directory structure.
Do you have your version running anywhere I could give a gander ?
Ah, I see. I'll mark it for deletion in the next patch then.
This site is currently running on the latest patch, for a full week now. I copied over the changes from hanbot's patch manually yesterday, so those are in as well.
I suppose I could make you a temporary contributor account on here to test out the post editing / image upload functionality -- if that's what you had in mind.
That's what I had in mind.
[...] billymg Do you read the logs? You should probably read the logs. « The mp-wp weightloss program [...]
[...] bug was introduced in the previous mp-wp patch that caused encoded ("escaped") html characters to be converted back to their symbols after being [...]
[...] mp-wp_remove-tinymce-and-other-crud.vpatch (billymg) (sauce) [...]
[...] out what I'm missing I'd be happy to update this article. [↩]23k of which have since been snipped. [↩]wpautop can also be disabled at the theme level via the addition of remove_filter( [...]
[...] if no one objects, the next patch will rip out js and whatever features depend on it. this will be similar in absolute terms (LOCs/bytes) to the first major round of trimming [...]
[...] After the first, which removed TinyMCE. [↩]of these remaining bytes, about 220k are dedicated to empty [...]
[...] lines removed from mp-wp, almost 30% and gets it under 100k lines (~97k). compare to previous round of [...]
[...] was trimmed3, a feature was added, patches were produced, and in 2020 TMSR was closed. I had also at [...]
[...] include support for other syntaxes besides UNIX diff files. [↩]Completion of the test suite, slimming patches, a proper theme or two, the addition of the new server-side select mechanism as a standard feature [...]
[...] leaves the larger (and likely ongoing) trimming project, as well as a proper republican theme. The first slimming patch was one of the most satisfying pieces of work I've completed in recent memory and I'd very much [...]