Discourse Sitemap Plugin

(Rafael dos Santos Silva) #75

By default a lot of Discourse internals will use HTTP until you check force_https. You should do that if your site works on HTTPS you shouldn’t allow HTTP anymore.

1 Like

(Hosein Naseri) #76

But I want the http to be available. because I have implemented the forum in my android application, However since older android versions have some issues with some ssl protocols, I do my api calls with http protocol. I don’t know if i enable force_https, am I able to still use http protocol in my api calls?


(Rafael dos Santos Silva) #77

Oh I see that’s a pretty strict requirement. Looks like in your case there is no way out.

Those are Androids below 4.3 ?


(Hosein Naseri) #78

I think so.

Since I’m really fine with not force_https ing my forum, I think an option for this plugin to list ssl urls would be the best thing for me.


(Vinoth Kannan) #79

I guess you should customize this plugin little bit for your requirements.


(Richard - DiscourseHosting.com) #80

Note: It seems like the caching mechanism is broken in Rails 5.

Looking into it later today, trying to get a fix out by today or tomorrow.
In the meanwhile: input and suggestions are welcome :slight_smile:
Details here https://github.com/discoursehosting/discourse-sitemap/issues/5

EDIT found it. render :text is deprecated in Rails 5 - should be render :plain instead. Pushed a fix.


Sitemap.xml for Google Webmaster
(Chaudhary) #81

the sitemap plugin of discourse do not update the sitemap urls to https:// (as usually seen in wordpress). It still shows http://. Please solve this issue. As it helps in faster https:// indexing after migrating to SSL


(Jay Pfaffman) #82

The better place to post this would be in the Discourse Sitemap Plugin topic.

Have you enabled the force https site setting?

@rgj, this might be worth a look.

1 Like

(Chaudhary) #83

yes force https is enabled.

1 Like

(Richard - DiscourseHosting.com) #84

The sitemap code uses Discourse.base_url so there is no bug there.

If you recently enabled force_https then you might be looking at the old (cached) sitemap.

The easiest way to get around that, is to change the sitemap_topics_per_page. Even a slight change is enough, for example from 10000 to 9999. This will cause the plugin to stop looking at the cache.


(Vaibhav Mule) #85

I have installed it but it does not generate /newssitemap.xml?

1 Like

(Vinoth Kannan) #86

You should try above.


(Vaibhav Mule) #87

Thanks, but why it is not mentioned in robots.txt?

1 Like

(Vinoth Kannan) #88

AFAIK you have to manually submit the news sitemaps.


(Richard - DiscourseHosting.com) #90

That was indeed an error in the documentation.
Thanks @vinothkannans for correcting it in the topic. I have updated the README.md as well now.

1 Like

(Bali Bebas!) #91

Those without a Google account can notify them of changes with:

curl http://www.google.com/ping?sitemap=/path/to/sitemap.xml

Here’s a rake task to notify a few different services simultaneously: made-mistakes/Rakefile.rb at master · mmistakes/made-mistakes · GitHub

1 Like

(Valon) #92

Not all our sites are news related, it’s more like forum or group based. Thats why we are getting error on Webmster Tools as a news

Your Sitemap is on a site that is not in the Google News database. Google News can only accept Sitemaps from sites that we crawl. If your site is crawled by Google News, please check that the URL of your Sitemap agrees with the URLs of your articles as they appear on Google News, including any leading “www”. If you would like to request inclusion of your site in Google News, pleasecontact the Google News support team.

1 Like

(@SenpaiMass) #93

Is sitemap a necessary evil? If i don’t use this plugin, will my community not get the exposure it seeks?


(Vinoth Kannan) #94

I don’t think so.


(Jay Pfaffman) #95

My understanding is that if you have migrated a large site, it might help. If you are starting a new community, then it’s not necessary.