Translators

@Simos Try removing the View Users privilege. Although that will disable the other routes as well like /api/user/uid/<uid>

Yes, best posts is in v1.13.0

@PitaJ I believe the original issue was that the WP site is hosted via a service that does not do Node.js, so that option is out.

Perhaps @Mickola can set up a reverse proxy on that Ubuntu VM to send traffic to either WP or NodeBB... instead of having the reverse proxy on the WP server...

Could be that the plugin templates were not built? Try running ./nodebb build and restart NodeBB.

@Mickola It doesn't look like you've added http://domain.com/forum:* to the list of socket.io origins?

I opened a PR here, for @pitaj to review, but it's more than likely he has his own plans for how he will handle compatibility.

I'm sorry to hear that the calendar is broken on latest -- in the future, please consider spinning up a staging instance with a copy of your production database to test upgrades like this, as it is not possible to roll back the database changes between version bumps like from 1.12.x to 1.13.x

Hi @dcook, just so @pitaj can debug, can you let us know the version of plugin-calendar installed?

@Abhinov-Singh-0 You can check which NodeBB version you are running by starting NodeBB. The version is one of the first lines output. You can also look inside the package.json file, which should say the version number.

Regarding your second issue, the git error is suggesting that you've edited the file public/language/en-GB/category.json. Did you?

You'll want to reset the file back to the version that came with NodeBB. To do this, run git checkout public/language/en-GB. Remember, this will discard any changes you've made to this file.

Once done, you can run git checkout v1.13.x again.

I'm assuming you're referring to the chart in the main admin control panel?

The two main analytics tracked are pageviews and unique visitors.

• Page views are fairly self-explanatory, one page load or transition to a new page counts as a new page view.
• Unique visitors is based on the IP address, and so every time a new IP address shows up in that hour, the count is incremented by one. We also track unique visitors on a daily, weekly, monthly, and all-time basis, for the numbers here:
  • 
• The "registered", "guest", and "bot" variants for pageviews increment alongside each pageview, but depending on whether the user is logged in (or not), or whether that request came from a bot.
  • "registered" and "guest" should add up to the total pageviews, since you're either registered or not.
  • "bots" are usually also guests, but we use some basic logic to detect whether they're a bot or not (probably user-agent string)
  • For a variety of reasons, the "bot" count is not always predictable, since some bots are rather obscure, or fudge their user-agent strings, so take this number with a grain of salt.

I hope that answers your questions, let me know if there's anything else you'd like to know.