Dear Willem,
We have just released Views and a few days ago Types. I will test them on your test server and get back to you.
Regards,
Caridad
Dear Willem,
I thought I had access but I dont. Can you test yourself and report back? if it still happens, please fill in the access details in the boxes below the comment area.
Thank you,
Caridad
Hi Caridad,
I can confirm it's working, but I don't see how it's going to help me. That what I was afraid off and mentioned before is happening, this I what I said about it earlier:
Does it only affect the views inserted in the body or does it affect the complete body?
As you can understand, if it affects the complete body, it will be very time consuming to write <p></p> around every paragraph.
Hope to hear from you.
Kind regards,
Willem-Siebe
Dear Willem,
I have reviewed your site and it turns out to be in the page Content Template. I changed it to this and its working:
<div class="body-container">
[wpv-post-body view_template="None" output="raw"]
</div>
Does this solution have any problems?
Regards,
Caridad
Hi Caridad,
That's exactly what I did and why I confirmed it is working. However, it affects the complete body so is also removing all the <p></p> tags where it should be listed, the thing I was afraid for because I posted earlier:
Does it only affect the views inserted in the body or does it affect the complete body?
As you can understand, if it affects the complete body, it will be very time consuming to write <p></p> around every paragraph.
In theory it's very simple what I did ofcourse, I just inlcuded to views in the post which should be possible. This 'raw' solution isn't the solution while it affects the complete body, and that would mean that I (or clients) should mark their paragraphs with <p> elements themselves, which is not our and your intention I think.
Kind regards,
Willem
Dear Willem,
Actually we need the raw output for the views, not for the rest of the text.
Would it be possible to include both views inside a Content Template, and call that one with the raw attribute?
[wpv-view name="Ervaringen"]
[wpv-view name="Ervaring definitief ontharen"]
Regards,
Caridad
Hi, that is a good workaround and it works! Does it makes sense to still allow us to insert views directly in post content then, if HTML get confused?
Dear Willem,
It works well most of the time for our users. With the new output="raw" attribute we can take care of users that have problems. I think we have it all covered now.
Please let me know if you are satisfied with my answer and if I can help you with any other questions you might have.
Regards,
Caridad
Hi, yes it's covered, but I still don't understand why it is causing problems ;-).
This worked for me. The extra ps have been driving me crazy! I had been using a plugin called Raw HTML which let me pick and choose on the edit screen for every page/post whether to output it as raw but it wasn't working completely.
