CKEditor Inline Images not saved as Permanent in Term descriptions
Any inline image I insert with CKEditor ends up being flagged as temporary. Which of course, means that they are deleted during garbage collection/cron.
I have seen this many years ago in a few contexts (e.g. CKEditor fields inside Paragraphs, etc.) -- in what context are you using these CKEditor fields?
Actually, that caused me to look a bit closer. This is in description fields on taxonomy terms. It looks like it doesn't do that on standard nodes.
I am building a "catalog" (although it's not an online store) that uses the description field as a landing page kind of thing. Long blurb at the top of a list of items.
I suppose that I could just use a block attached to each term I need it on. But that could get unwieldy.
My suggestions, if there is time to look at recent bug reports:
(1) Not sure if the fix for this issue still needs a code review to get labeled as RTBC:
Editor link autocomplete...
Posted9 hours 41 min ago by Olaf Grabienski (Olafski) on:
Just to say I discovered an issue with doing this, which I have documented here.
https://github.com/backdrop/backdrop-issues/issues/7168
To make this work, before this issue is...
Posted2 days 11 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
You could probably do this with a View where the exposed filter is the node id
Ah, interesting idea. Thanks!
Would you kindly consider creating links in the...
Comments
I have seen this many years ago in a few contexts (e.g. CKEditor fields inside Paragraphs, etc.) -- in what context are you using these CKEditor fields?
Actually, that caused me to look a bit closer. This is in description fields on taxonomy terms. It looks like it doesn't do that on standard nodes.
I am building a "catalog" (although it's not an online store) that uses the description field as a landing page kind of thing. Long blurb at the top of a list of items.
I suppose that I could just use a block attached to each term I need it on. But that could get unwieldy.
It looks like it's a known issue with a PR. You might want to test this PR and respond in the issue itself.
I adjusted the subject slightly.