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.
As I work through things I flush the caches after every change I make.
As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
If you haven't already, flush all the caches.
If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
Posted11 hours 1 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
... had a status of '0' that I changed to '1' directly in th edb, in line with other custom modules
Awful idea! That's not how modules get installed! The number in db...
Yes that much I know :)
Thanks for the quick reply...
My info file contains:
name = Fix Zero Search
description = Fixes leading zeros in search.
type = module...
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.