Simplicity and validation

[zerosonesfun]

These changes make things simple, ensure the feeds validate, and keep the feed post content text only versus trying to include HTML. This last part is admittedly a personal preference. I do not think we need the feeds to include the full HTML for posts. Plain text descriptions/summaries should suffice and help to ensure validation and feed reader compatibility.

The main reason I started making these changes is because the ID portion of the atom feed wasn’t validating. It was only pulling in the post ID which happens to be “1” every time. This pull request makes the ID the full permalink which validates.

[dexif]

+1

[AmauryCarrade]

Hi, Thank you for your PR! I'm not home right now so I won't be able to review and test it until next week, but it's very appreciated :)

[AmauryCarrade]

H, and again sorry for the delay. I added a few comments to be addressed before the merge, but thanks a lot for the PR :) .

[zerosonesfun]

I noticed another small issue when validating the atom feed. It did not like the site URL not ending with a “/“. Therefore, I added a slash in the code.

There is just one more warning at times but it is not a big deal. Sometimes, depending on the post (a post with no text, just an image, for example), the summary may end up being blank. The feed validator still marks the feed as valid, but gives a warning that there shouldn’t be blank summaries. In the future, some type of if/else coding could solve this... if summary is blank, add the text, “No summary found.” This way, there is never a blank summary.

Here are screenshots of my feeds validating. As I state above in my replies, the couple changes you suggest are not necessary; the feeds are valid (you will see a warning about the utf-8 encoding but that’s just something with my server. Others may not get that warning...

RSS valid:

ATOM valid:

[zerosonesfun]

@AmauryCarrade,

Please review my latest changes. Here is what I have done:

• Changed atom.blade.php so that it will now include the full HTML content of the post; and it includes the type=html attribute.
• Changed rss.blade.php so that it will also include the full HTML content of the post.
  • By default, the extension will use these full HTML versions.
• Added a new atom.blade.nonHTML.php file and a rss.blade.nonHTML.php file which are the same feeds except they will only show plain text excerpts of the posts.
  • This means, if users want, they can remove or rename the original blade.php files, and remove the "nonHTML" part in these filenames and then the extension will use the non HTML / excerpt versions instead.

[AmauryCarrade]

This means, if users want, they can remove or rename the original blade.php files, and remove the "nonHTML" part in these filenames and then the extension will use the non HTML / excerpt versions instead.

One should never change anything in the vendor directory, so I'm not convinced. This being said, I'll merge these changes and add a settings interface to configure:

• full text vs extract;
• plain vs HTML;
• how many entries per feed.

Thanks for your contributions!