You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RainLab's Blog has two panels when editing or creating a blog post: one for the raw text and the other for the formatted text. As you type the raw text, it formats the text in the preview pane as it would appear when viewing the blog post on the website.
However, when enabling any WYSIWYG editor for RainLab's Blog plugin, it no longer generates the formatted text. Instead, it saves the formatted content in the raw entry field. Here is RainLab's blog post table definition:
rainlab_blog_posts
id
user_id
title
slug
excerpt
content
content_html
published_at
published
The raw text should be saved in the content field and the formatted text in the content_html field.
I personally do not care too much about having the preview pane open while I'm typing. However, upon saving, it should save the formatted text in the content_html field instead of in the content entry field.
Thank you for considering.
The text was updated successfully, but these errors were encountered:
RainLab's Blog has two panels when editing or creating a blog post: one for the raw text and the other for the formatted text. As you type the raw text, it formats the text in the preview pane as it would appear when viewing the blog post on the website.
However, when enabling any WYSIWYG editor for RainLab's Blog plugin, it no longer generates the formatted text. Instead, it saves the formatted content in the raw entry field. Here is RainLab's blog post table definition:
rainlab_blog_posts
The raw text should be saved in the content field and the formatted text in the content_html field.
I personally do not care too much about having the preview pane open while I'm typing. However, upon saving, it should save the formatted text in the content_html field instead of in the content entry field.
Thank you for considering.
The text was updated successfully, but these errors were encountered: