Default Values for WYSIWYG not saving for MariaDB

[Rar9]

Describe the Bug

Defining a Default VALUE in a WYSIWYG Field is not saved on Directus 9.17.4

Is HTML Supported ?

How to add Tokens related to the given content?
How to generate multiple default values if this WYSIWYG Collection is used in Relation to content?

To Reproduce

Create content with WYSIWYG field.

Errors Shown

no error is saves an empty field

What version of Directus are you using?

9.17.4

What version of Node.js are you using?

16.7

What database are you using?

Mariad 10.6

What browser are you using?

Fire

How are you deploying Directus?

locally

[licitdev]

@Rar9 I am unable to reproduce your issue. Please assist to attach a screenshot of the schema tab for your wysiwyg field in the data model. It would be nice if you could attach a screen recording demonstrating the issue.

Here's a screen recording of my quick test.

Screen.Recording.2022-09-15.at.4.35.43.PM.mov

To answer your questions...

Is HTML Supported ?

Yes, shown in my screen recording

How to add Tokens related to the given content?

You should be able to use conditions for different static access tokens.

How to generate multiple default values if this WYSIWYG Collection is used in Relation to content?

This isn't possible as the default value is on the database level. However, you may make use of the filter event hook in Flows to set different values. Ref: https://docs.directus.io/configuration/flows/triggers.html#event-hook

[Rar9]

``

[Rar9]

My test is with MariaDB 10.6.7 Default value is even overwritten when it is defined in phpmyadmin once saved

If I compare with fresh install sqlite3 the default value works

I also notice that on your video the Length is undefined. in Mariadb its set to max 65k

It feels like the DEFAULT value will overwrite all once the default value is set.
EG Unticked NULLABLE is re-ticked oncce devault value is saved.

[licitdev]

In the quick test earlier, it was tested in a different database.
Just tested in a MariaDB instance and the issue can be replicated.

This issue may be related to knex/knex#2649 or knex-schema-inspector.

Further investigation is needed to pinpoint the root cause.

@Rar9 Thanks for reporting! 👍

[Rar9]

So an issue from 2018, so I believe there is very little hope to get this working anytime soon if its still not fixed after 4 years.

[benhaynes]

So an issue from 2018, so I believe there is very little hope to get this working anytime soon if its still not fixed after 4 years.

I mean, it's OSS, so anyone can take a stab at fixing it at any time. What @licitdev dev said is that it might be related... not completely sure. Also, this isn't in our codebase, so it's hard for us to track resolution.

[Rar9]

Any findings?

[rijkvanzanten]

Any findings?

Did you make a PR for knex/knex#2649 or this issue?

[rijkvanzanten]

Linear: ENG-188

[azrikahar]

I believe this is not resolved as of 9.22.1, keeping this open to make sure it is still tracked.