Hi Matthew,
try using ‘show clean html’ and make sure the tags you aish to show are in the allowed html tags list
please let me know if that helped
Chrome doesn’t seem to want to validate it with “show clean html”
=======================================================
This page contains the following errors:
error on line 61 at column 34: Encoding error
Below is a rendering of the page up to the first error.
Simply Better Living SHARP | Simply Better Living https://simplybetterliving.sharpusa.com Thu, 10 Oct 2019 15:34:20 +0000 Thu, 10 Oct 2019 15:34:20 +0000 Matthew Vecera 11524 2019-10-10 15:34:20 2019-10-10 15:34:20 111
=======================================================
-
This reply was modified 6 years, 7 months ago by
vecerama.
Firefox doesn’t care for it, either.
=======================================================
XML Parsing Error: not well-formed
Location: https://simplybetterliving.sharpusa.com/?call_custom_simple_rss=1
Line Number 61, Column 277: <content:encoded><![CDATA[
Hi
it opens for me fine
if you are having issues – try to change – xml by dom – in plugin settings.
let me know if it solved the issue please
best regards
danikoo
Oh, wow. That blew up in my face… I am removing anything that looks like a tag now… π
As I was saying… π
I’m sorry. The only reason that it works now is because I had to re-set it. to NOT use CLEAN HTML… sorry. This is a production environment. You will notice that the formatting, specifically the (P) tags are not present.
=====================
[CDATA[
We are so excited that our…
=====================
I will reset it for you.
I’m leaving it as:
=====================
Default: post
Default post_status: publish
posts_per_page: 25
show post_meta in feed: Yes
show post thumbnail in feed:Yes
show post content in feed: show clean html
allowed html tags: All the defaults including [p], plus I added [description]. Then I tried to include [content:encoded] and CDATA tags, but any tag that included punctuation, like :, [, ], or !, get dropped in the editor.
Build output xml with: BY STRING
***Both options will not render in Firefox and Chrome
pubDate date format: RFC 2282
protect my feeds with a key: NONE
Please let me know. I am really in a bit of a bind here.
THANK YOU!
-
This reply was modified 6 years, 7 months ago by
vecerama.
Oh, wow. That blew up in my face… I am removing anything that looks like a tag now… π
As I was saying… π
I’m sorry. The only reason that it works now is because I had to re-set it. to NOT use CLEAN HTML… sorry. This is a production environment. You will notice that the formatting, specifically the (P) tags are not present.
=====================
[CDATA[
We are so excited that our…
=====================
I will reset it for you.
I’m leaving it as:
=====================
Default: post
Default post_status: publish
posts_per_page: 25
show post_meta in feed: Yes
show post thumbnail in feed:Yes
show post content in feed: show clean html
allowed html tags: All the defaults including [p], plus I added [description]. Then I tried to include [content:encoded] and CDATA tags, but any tag that included punctuation, like :, [, ], or !, get dropped in the editor.
Build output xml with: BY STRING
***Both options will not render in Firefox and Chrome
pubDate date format: RFC 2282
protect my feeds with a key: NONE
Please let me know. I am really in a bit of a bind here.
THANK YOU!
Hi
you do not need to add [description] or [content:encoded] – these are xml tags.
the problem with your feed – is that you have invalid chars in your content. did you copy it from word or pdf?
please see here
https://drive.google.com/file/d/1-dS-heN325HBIpXYp_b_DDpp5Uv6tqol/view?usp=sharing
i will try to solve it on my end, but that will require plugin version upload.
sorry i couldn’t help more
INTERESTING!!! I see now! π
I will clean up an article and test again. Does a plugin exist that will change the text encoding that you are aware of?
By the way, I thought that ANYTHING, any encoding, would work as long as it was inside a CDATA tag. Is that not true?
Thank you!
By the way, I thought that ANYTHING, any encoding, would work as long as it was inside a CDATA tag. Is that not true?
If only life were simple π
some chars will break any xml even in CDATA
i am already working on a solution
hope i will have good news soon
Yes, Please! It seems that choosing FILTERED HTML and debugging all the content for non-ascii characters is BRUTAL manually. I’m hoping that it will be easier to just retain the (P) tags in the unfiltered view. π
THANK YOU THANK YOU THANK YOU!
I’m sorry @danikoo. I had to revert the settings back to UNFILTERED. We are working on an app that retrieves a block of XML in the rss feed. Although the ALLOWED TAGS does contain (CODE), it does not work with a comment (!–), so the below package was blank:
(content:encoded)
(![CDATA[
(code)
(!– (collection name=”general”)
(image url=”spotlight_icons/general/cooking_graphic.png” name=”Cooking”/)
(image url=”spotlight_icons/general/ideas_graphic.png” name=”Ideas”/)
(image url=”spotlight_icons/general/safety_graphic.png” name=”Safety”/)
(image url=”spotlight_icons/general/tips_graphic.png” name=”Tips”/)
(/collection) –)
(/code)
]])
(/content:encoded)
They are doing the testing now, so I have to keep it like this for a little while. Is that OK?
SETTINGS:
=====================
Default: post
Default post_status: publish
posts_per_page: 25
show post_meta in feed: Yes
show post thumbnail in feed:Yes
show post content in feed: SHOW UNFILTERED CONTENT
Sorry, I know you were testing too.
Matthew
-
This reply was modified 6 years, 7 months ago by
vecerama.
hi
Must say i lost you there
if you are still having issues because of bad encoding and have access to the plugin code files
try changing line 713 on custom-simple-rss.php
from
$the_content = apply_filters(‘the_content’,get_the_content($post_id));
to
$the_content = apply_filters(‘the_content_feed’, get_the_content($post_id));
let me know if that solved the issue of text encoding
best regards
danny
Hi @danikoo.
We are the company that developed the blog that @vecerama has been discussing with you.
We attempted the latest fix you suggested but it did not solve the problem.
To help troubleshoot this issue, we’d like to establish a few items:
1. The plugin is stripping out the {p}{/p} tags in the output of the RSS. We see the tags in our HTML so are originally there.
2. We are attempting to feed this RSS data into an external app. With the missing tags, the formatting is messed up and the content is difficult for user to consume.
Please review our blog and the implementation of your plugin:
https://simplybetterliving.sharpusa.com/
Does your plugin require a certain version of:
– WordPress?
– PHP?
– mySQL?
Upon looking at the blog, reviewing tech requirements, are there any other solutions that come to mind?
We appreciate your help troubleshooting this. Thank you!
Hi
the plugin is definitely DOES NOT strip p tags !
I am using it myself for several of my clients sites and it works perfectly π
you can see example here
https://www.danikoo.com/?call_custom_simple_rss=1&csrp_tag=test
* please make sure that the p tag is in the list of allowed html tags inside the plugin settings – maybe someone removed it from the list by accident
Hope that helps
let me know
Best Regards
Danny