New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The letter "n" is inserted to the fetched posts #29

Closed
talgalili opened this Issue Jun 24, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@talgalili

talgalili commented Jun 24, 2014

Here is how the post looks like:

image

Here is how the feed looks like:

image

Here is the link to the feed:
http://blog.r-enthusiasts.com/rss/

This happens for feedwordpress version 2014.0506
but NOT for version 2013.0504

Any idea what might be causing this?

@zoul0813

This comment has been minimized.

Show comment
Hide comment
@zoul0813

zoul0813 Jul 24, 2014

Contributor

I can confirm that this is also happening on one of my sites. The "n" does not appear in the Feed's RSS/XML. I'm assuming that a string replacement was added/modified between the versions and is missing a "" ("n" should be "\n").

Contributor

zoul0813 commented Jul 24, 2014

I can confirm that this is also happening on one of my sites. The "n" does not appear in the Feed's RSS/XML. I'm assuming that a string replacement was added/modified between the versions and is missing a "" ("n" should be "\n").

@talgalili

This comment has been minimized.

Show comment
Hide comment
@talgalili

talgalili Jul 24, 2014

Thanks for confirming. I wish this would be resolved...

talgalili commented Jul 24, 2014

Thanks for confirming. I wish this would be resolved...

@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek Jul 25, 2014

Owner

I haven't put up an announcement yet on the project website, but this is a compatibility issue due to some changes in WordPress's expectations about when data being passed to the API should be slashed and when it doesn't neeed to be. the current version on Github should resolve this issue. The relevant fix is in commit b01c483 b01c483. Take a look and let me know whether it resolves the issue for you.

Owner

radgeek commented Jul 25, 2014

I haven't put up an announcement yet on the project website, but this is a compatibility issue due to some changes in WordPress's expectations about when data being passed to the API should be slashed and when it doesn't neeed to be. the current version on Github should resolve this issue. The relevant fix is in commit b01c483 b01c483. Take a look and let me know whether it resolves the issue for you.

@radgeek

This comment has been minimized.

Show comment
Hide comment
@radgeek

radgeek Aug 8, 2014

Owner

Hey y'all: So, as I mentioned, this issue was fixed a couple weeks ago in the development branch, and since I recently made a release including the fix (2014.0805), I'm going to mark this issue closed for the time being. If you're still encountering an issue like this, let me know and I'll be glad to re-open and take a look at it.

Owner

radgeek commented Aug 8, 2014

Hey y'all: So, as I mentioned, this issue was fixed a couple weeks ago in the development branch, and since I recently made a release including the fix (2014.0805), I'm going to mark this issue closed for the time being. If you're still encountering an issue like this, let me know and I'll be glad to re-open and take a look at it.

@radgeek radgeek closed this Aug 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment