Yggy

Thanks!

It seems that I am still having an old DateTime component in the Gutenberg library. So I need to get that fixed so the LZB dependency is fixed with it. Not your problem. (-:

Hi,

Bummer!

Since {{#}} is handlebars as well, I was hoping that helpers were possible too, just not turned on or something.

Thanks for your reply!

Since additional code was needed for the extra options anyway, I went for the simplest way. Just adding the br tag, or actually changing the string, by right after the Writing effect headline widget adding the HTML widget with following code:

<script>
document.getElementsByClassName("written-lines")[0].textContent = "Title<br>This is the subtitle";
</script>

It doesn’t show in the back end, but in the front end it works.

I thought of that too at the time of the original post, but then both would write simultaneously. While it would be preferable when the subtitle begins when title is finished. And there seems no option in the widget GUI to serialize the 2 titles, or delay the sub title long enough to have the title finished being written.

While typing this reply, I found the readme of the original js library used.

Normally it should be possible to break the lines using P tags, but apparently that gets filtered out by your widget, Elementor or WordPress.

It also shows a way to delay text, by adding ^1000 in the text string to delay 1000 ms. This does seem to work in the widget.

There are also other options not present in the widget. Will play around with those to see what works with the widget for my scenario.

• This reply was modified 2 years, 7 months ago by Yggy.

With a little code change, you can achieve this.
See my topic: Admin subpage show specific fields as columns

Reason for installing this plugin became obsolete due to programming a custom solution instead. For future projects it might still be interesting to have this plugin working, so was able to test the suggested guide today.

The following lines were already in place of the MariaDB config:

innodb_large_prefix     = on
innodb_file_format      = barracuda
innodb_file_per_table   = true

Added the following line to the config:

innodb_default_row_format = DYNAMIC

After rebooting of the MariaDB service and doing a clean install of the plugin in the site, the additional install seems successful.

No time yet to fully test the plugin, but it is probably safe to say this topic is resolved. Thanks!

Tried to create the table wp_cjtoolbox_templates manually in the database by using the code from /css-javascript-toolbox/includes/installer/installer/db/mysql/structure.sql

This results in following error

MySQL said: Documentation
#1709 - Index column size too large. The maximum column size is 767 bytes.

Trying to find the cause + solution, but currently not succesful.

I use MariaDB 10.1.44

Hi Daryll,

Thank you for updating the FAQ and add a working code example here!

The allowed tags and attributes were easily found in the code, where I did the edit myself. Regarding the reference it was more why the current disallowed tags and attributes are a risk.

Like for the target attribute I couldn’t find (search parameters for) resources why it is a risk. I assume you did research which to allow and which to disallow. Reason why I asked. ??

Anyway, thanks.

Kind regards,
Yggy