HTML encoding issue in emails (&nbsp, &amp, etc)

Bugs
9

Quite honestly, not sure which package it was. The key issue was that the yarn.lock file, which does pin packages correctly, was not included in the build process. This happened both on Magic Pages, Ghost(Pro), and later on, on DigitalPress.

So, assumption: Hostinger is also ignoring the yarn.lock file. @ohyeahpaulchin, if you’re relying on their pre-built version, there isn’t really anything you can do about it. As Cathy pointed out, starting from scratch with the Ghost CLI would be the better option (and – if it is the same issue – has not been affected by this, when it first occurred in October 2024).

@jeremielondon, since this might also affect your hosting at Abstract27, these are the steps I took to include the yarn.lock:

  1. I run yarn archive on the Ghost repository to get the package
  2. Extract it
  3. Add the original yarn.lock file into it
  4. Repackage it
  5. Then use the Ghost CLI with --archive to install this newly packaged archive

I do all of this in a custom Dockerfile, so no manual intervention needed.

3 Likes