You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Atom, which will be accessible on https://.coding.blog/_feed.atom
RSS2.0, which will be accessible on https://.coding.blog/_feed.rss
JSON Feed, which will be accessible on https://.coding.blog/_feed.json
I would prefer to use a relative URL that would work both when locally hosting and when deployed to my live site.
In its current form, I couldn't test the link locally before publishing. Then after publishing and some change, the link still points the old (deployed) file.
In both cases, my workaround was to directly open the generated files to inspect them. I have no workaround for testing the link before deploying the first time.
The text was updated successfully, but these errors were encountered:
The coding-blog-plugin documentation for RSS says to link to the feed files using an absolute URL.
I would prefer to use a relative URL that would work both when locally hosting and when deployed to my live site.
In its current form, I couldn't test the link locally before publishing. Then after publishing and some change, the link still points the old (deployed) file.
In both cases, my workaround was to directly open the generated files to inspect them. I have no workaround for testing the link before deploying the first time.
The text was updated successfully, but these errors were encountered: