Post Only Displays & Outputs First Paragraph When Using WYSIWYG Editor (Pictures) about blog-plugin HOT 6 CLOSED

Same problem here, however, had a workaround for this at the moment.

Instead of using {{ post.content_html | raw }} I used {{ post.content | raw }} and enclosed it within a conditional tag post:

{% if post %}
    <h2>{{ post.title }}</h2>

    {{ post.content | raw }}

    {% if post.featured_images.count %}
    <div class="featured-images">
        <div class="row">
            {% for image in post.featured_images %}
            <div class="image">
                <a href="{{ image.path }}" data-caption="{% if image.title %}<h3>{{ image.title }}</h3>{% endif %}<p>{{ image.description }}</p>">
                    <img
                        data-src="{{ image.filename }}"
                        src="{{ image.path }}"
                        class="img-rounded"
                        alt="{{ image.description }}" />
                </a>
            </div>
            {% endfor %}
        </div>
    </div>
    {% endif %}

{% else %}
    <h2>Post not found</h2>
{% endif %}

For displaying images, as seen above, was from here: #57

As you notice the preview window still doesn't update with the content, but when you access the post page it works as usual.

Hope this helps, as we wait for the proper fix for this.

from blog-plugin.

@justanne appreciate the suggestion. I will implement this for the time being, though it does cause some pretty annoying layout problems.

e.g. it adds a completely unnecessary <p><br></p> tag at the end of the article (even though it is not at all present in the back-end blog article even when looking at the pure html), which adds a lot of empty padding/margin at the bottom of the post. I could of course use some CSS to go target specifically the last <p> & <br> and hide all of it, but again, like you said, it's just a quick temporary fix until it is properly resolved. So thank you for the suggestion!

Hopefully @daftspunk sees this issue eventually. I assume it probably isn't too crazy of a fix, though I could be wrong. Dealing with WYSIWYG editor output is never fun when compared to just basic raw + markdown. Unfortunately clients never want to learn markdown, so there's that.. 😜

from blog-plugin.

This is really a problem and even though i love october very much, i have troubles with users who are going to interact with the website, so, i decide to postpone usage of october untill the problem is fixed!

from blog-plugin.

@beemankg yeah, I just pushed a site live today for a client and I'm really nervous about this now. Hopefully this issue is seen and remedied in the near future.

from blog-plugin.

@flip4bytes Hopefully! I have two clients waiting for the results! And i just figure that out, that the editors suck :))) so, i gotta use another cms for them i guess, and will wait for the fixed bug in this thing! Thanks for the post though!

from blog-plugin.

This issue relates to a third party plugin? Please log this fault with the author of the "WYSIWYG Editor" plugin.

As a side note, we should be adding WYSIWYG natively in a few days.

from blog-plugin.