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.
@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...
Now, now calm down! :)
I based my statement "Since Bee doesn't seem to have any active sites using it - I wonder if that is a viable option?" on the following:
Note active installs...
Since Bee doesn't seem to have any active sites using it - I wonder if that is a viable option?
What do you mean by that? Loads of sites use it but it is not a module, rather...
Posted5 hours 33 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
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...
Posted1 day 4 hours ago by Olaf Grabienski (Olafski) on:
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.