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.
It is a good point @izmeez and when I was researching repo discoverability I found that GitHub search does prioritise matches with more stars.
This is what I was researching for:...
Posted2 days 22 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
This link should work if the VIEW contains a Block and a Page - the link from the block will be directed to this page. I've never used it, so I might be wrong. But what can be done easier is to...
Thank you very much for your reply!
I understood that I first need to create a VIEW. I had assumed that the settings were configured via the block because it’s already included in Backdrop...
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.