@julian said in May Docker Discussion:
Interesting recent discussion re: Docker
Some parallels to what was discussed here
Totally true. People put so much into each new thing that they hear about thinking that it is going to change the world, without any clear idea of what problem it is even trying to address!
@baris said in Problem to reach replied/original post in paginated forum:
What version of NodeBB are you using? This seems to be fixed in 1.11.0 https://github.com/NodeBB/NodeBB/issues/6948
Thanks a lot. Yes, ours is older than 1.11 but we will be upgrading soon to the latest 1.12
Good to hear that will resolve the issue.
djensen47 created this issue in NodeBB/NodeBB
Replied-to button has the wrong URL on forum installed in "subfolder"
I did a very quick wiki page on Administrator Functions. I realize this is really somewhere between user help and development. The value added might be in (1) explaining some of the features where its needed or helpful (I made a few NOTEs), and (2) linking out from that page to other more technical pages that are managed in ACP. Can't necessarily expect an Administrator to be a developer but also want to give them a heads up whats there and how its all connected.
Very rough still - If you would prefer different formatting let me know.
Totally missed this.
thanks for doing this @KTys!
is NodeBB "rendering-and-writing" the "ajaxified" pages for the crawlers to read?
@bentael -- no way, I made the decision early on not to do this because it is a drain on resources (how much, I did not test, as the alternatives were enticing enough)
Every link on NodeBB is accessible by direct link, and if you try viewing the source, you'll see the page content in <noscript> tags. I have heard arguments for and against this approach, but as we are being crawled properly by Google, it seems to be working just fine
Always open to suggestions for improvements, of course!
This is also the approach that Discourse has taken, btw.
or run node app --setup again and configure it. In general you would need to run NodeBB via sudo to gain access to port 80, and if you have something else listening to port 80 (ex. apache) this will not work. I know that @OutlawedOffroad recently managed to figure this out!
Here's the thread with my back and forth battle with this.. I'm on CentOS 6.4 so your miles may vary:
Still a work in progress. We fixed the issue then uncovered additional issues.. Once we complete it all and everything is aces I'm going to ask server support for a rundown of what they did since a lot of trial and error. Hopefully populate that Wiki link that goes nowhere with some info.
I made a Spanish translation for NodeBB, i dont know how to uplaod it to my server to test it.
If anyone want it, just ask.
And if anybody can help me to install it to test it before release, please chat me or reply above.
Have a look at this pull request to add german language pack:
If you're interested, you could do it for spanish as well, that would be pretty cool
And as I said on the other thread, DigitalOcean is supported, check out the guide
I have the files to translate it. When i get i will upload
Hooray for forward-thinking
Initially, we kicked around the idea of supporting multiple categories per topic (so, more like a "tagging" approach, as opposed to categories).
In the end, we felt that having a "middle-ground" between statically defined categories and user-defined tags was not a proper compromise (since it ended up not being greater than the sum of its parts), so we stuck with static categories.
A tagging plugin can be built, of course........
I just posted that question on SO to flamebait Jeff Atwood Just kidding
Yes we figured it out, as per the link above, we are showing up on the discussions tab on Google now Not sure if discourse has yet...
I don't think so..
Hey @RefinedSoftware, @caske33,
There's an ongoing issue right now with plugins not being "ajaxified" in the admin panel. "Ajaxifying" is our pet name for our shorthand method that loads pages in NodeBB (since it is a one-page application, it doesn't truly do a page reload when you click links).
Give it a try, if you'd like:
Open up your console (hit F12), and navigate to the console tab, if it is not open already
Type in ajaxify.go('users/online') ;
Also, it looks like I found a bug with the Skype Emoji -- darnit.