If the WordPress user account has the Discourse user specified then the post stub will be in their name, and show as one of their posts on the Discourse instance.
2 个赞
Newbie as well here. We’re in the process of setting up Discourse but we also have a Wordpress.org blog. Do you know how we can set up the url so it reads "www.blog.(our discourse name).com?
What’s the goal for doing this?
Hi Stephen, our goal is to allow the articles on our blog to show up in other news feeds, as well as introduce others to our discourse forum.
Sure, I was more referring to the use of ‘www.blog’ - your blog or publishing front-end can sit at:
and your discourse instance at:
community is just a example, you obviously use pretty much anything to denote your Discourse install.
There’s no need to go two-levels deep with a DNS name using ‘www’ and ‘blog’ in one URL, it’s lengthy and only serves to confuse users.
Didn’t you guys engage someone to set this up a while ago?
Hi Stephen, thank you for your quick replies, I appreciate it. Yes, Jay set up Discourse for us. Our url is www.hsp.world. We’re thinking of setting our blog url to be www.blog.hsp.world, right now we have it sitting at http://hspblog.modelsmith.com/ (we’re just tweaking the site and it should be ready in a few days). Is this the best way to go about this do you think?
Why not just blog.hsp.world?
Hi Hawk, thank you for suggesting, yes we thought that may be a good way to go, www.blog.hsp.world - we’re not sure how to go about creating or re-directing the url though…
I’m actually suggesting www.blog.hsp.world
What exactly are you getting stuck on?
Thank you @HAWK, well it sounds dumb (and I hope it isn’t too dumb), but how do we go about keeping the site hosted on the server it’s on, but changing the url to blog.hsp.world?
You need to repoint your domain – your DNS provider will be able to tell you how to do that.
I was just looking at my domain provider, I didn’t think it would be that simple. Thank you @HAWK, really appreciate you taking the time.
1 个赞
If it’s WordPress then you need to update the site settings too. If you don’t do that bit your permalinks won’t work, although there is a fix by hard-coding the new URL in the wp-config.php if you do lock yourself out.
If you’re using SSL on the blog the certificate will also need to be replaced every time you alter the URL.
Either way though this isn’t really a discourse question or related to the subject of this topic. I would reach out to whoever hosts your WordPress.
1 个赞
Absolutely thank you @Stephen I just wasn’t sure if anything would be different based on the main url being our discourse site. Thank you, I appreciate it.
If the Wordpress already uses wp-discourse and has posts or post stubs created for comments then those links will need to be changed, which includes manually updating database entries. Based on what you’ve said above though it’s hard to tell if this will be necessary.
Thank you @Stephen I think at this point it’ll just be on it’s own, we’ll have a link to Discourse on the blog. That may change in the future but we’ll start with this. Thank you again Stephen. 
It may be a bit late, but you might find blogging on Discourse and embedding on your website a useful alternative:
实际上，这甚至大多也不准确。nofollow 仅仅是一个提示，Googlebot 会根据具体情况选择是否遵循。如果该目标被 Google 认定为有效，它就会跟随并将其计为反向链接。即使没有 nofollow，如果 Googlebot 认为目标质量较低，它也不会跟随。
Bing 的情况则不同。它几乎会跟随所有内容，而且会反复尝试，即使遇到 404 错误，也不更新 301 重定向。
nofollow 几乎和 robots.txt 一样被高估了——Google 有时遵循它，但如果它发现哪怕一个链接（例如来自 Gmail 的链接），在这种情况下，它就不再理会 robots.txt 了。
1 个赞