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.
I'm also now getting a 403 when trying to access admin/reports/updates - it seems to be Backdrop generated but there is nothing in the Recent Log messages other than my login as admin...
Since this is still possibly Cloudflare related I'll post here:
I'm now experiencing what I think is caching issue - since installing Bee I've run bee cc all, bee cron, bee mm 1, then,...
My thanks to you both... I understand now that Bee is not a module but a stand alone utility.
I've installed it and see that it is similar to Drush which I have used before. I'll now...
@ian Let's try to stay on the rails here. As the project page, https://backdropcms.org/project/bee, says: "Bee is a command line utility for Backdrop CMS." It is equivalent to drush. It is not...
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.