Legacy CMS JPEG: upload allowlists, KB caps, and a second server-side resize are the usual “triple blur”
`legacy-cms-gif-jpg` targets decade-old CMS stacks: uploads may accept only `.jpg`, cap a few hundred KB per file, and re-sample once through old GD/ImageMagick. Raw GIF uploads can be rejected or stripped to frame zero, so editors pre-convert to JPG. The real trap is double scaling—crush locally then let the CMS stretch to template width and captions turn to soup. Filenames with CJK or spaces sometimes 500. EXIF camera data can violate internal redaction rules.
`legacy-cms-gif-jpg`: read the real template width first, then ensure ingest performs only one lossy resize
- Read the template’s real output width and upload KB ceiling; size the long edge so the backend only scales once; rename to ASCII plus a version token and strip EXIF when policy requires.
- On staging walk the full publish pipeline, grab the final HTML image URL, and check watermark plugins or CDN recompression—compare local JPEG bytes to what the edge serves.
- Store default matte color and quality tier per section in config—block editors from dragging quality sliders; after a minor CMS upgrade regression-test three canonical stills.
Legacy CMS Q&A: watermark plugins, derivative sizes, filename encoding
Looks sharp locally but mushy after CMS ingest—is that an auto watermark pass or a second long-edge resize?
Compare HTTP `content-length` and pixel dimensions before vs after upload; inspect themes/plugins that mint derivative sizes. If derivatives are baked from an over-compressed master, raise upload quality or disable “compress brutally then crop” plugin ordering.
Editors see “not a valid JPG”—progressive markers or CMYK/grayscale modes?
Old libraries often accept only baseline RGB JPEG; convert to sRGB 8-bit baseline and strip odd APP segments. Use `file` or a hex header peek to confirm the SOF type quickly.
The article shows two different sharpness levels for the “same” image—responsive srcset or duplicate embeds?
Audit HTML for mixed full-size and thumbnail URLs; standardize on media-library references instead of pasted hotlinks. Removing duplicates cuts bandwidth and duplicate-content SEO risk.
Colors drift slightly after a PHP GD upgrade—re-export everything?
Sample ΔE against an agreed tolerance; if only edge cases fail, re-export high-traffic banners first. Log the library version for the next upgrade diff.
Internal policy bans EXIF—how do we batch-strip GIF-to-JPEG uploads automatically?
Run `strip-all` in the export pipeline and validate before ingest; forbid “honor system” manual saves. The CMS should reject violations with a clear error, not silent uploads.