CONFIG.md documentation and also fixed a bug where when ATOM files are
loaded the config.rss boolean is actually checked as opposed to config.atom, fixed by also adding string.atom_disabled to config.json :)
This commit is contained in:
@@ -101,9 +101,9 @@ app.get("/user/:username/rss", (req,res) => {
|
||||
});
|
||||
// global ATOM protocol gets
|
||||
app.get("/atom", (req,res) => {
|
||||
if (config.rss == false) {
|
||||
if (config.atom == false) {
|
||||
res.render("partials/message", {
|
||||
message: config.string.rss_disabled,
|
||||
message: config.string.atom_disabled,
|
||||
config: config,
|
||||
})
|
||||
}
|
||||
@@ -122,9 +122,9 @@ app.get("/atom", (req,res) => {
|
||||
app.get("/user/:username/atom", (req,res) => {
|
||||
const username = req.params.username;
|
||||
const userID = func.get_userID(username);
|
||||
if (config.rss == false) {
|
||||
if (config.atom == false) {
|
||||
res.render("partials/message", {
|
||||
message: config.string.rss_disabled,
|
||||
message: config.string.atom_disabled,
|
||||
config: config,
|
||||
})
|
||||
}
|
||||
|
Reference in New Issue
Block a user