And you need to run ./nodebb build after making changes.

You need to use the translator module to translate the string. require(['translator'], function (translator) { translator.translate('[[user:bookmarks]]', function (translated) { //use translated string }); });

Does it work with just this <small class="timeago" title="{element.timestampInISOFormat}"></small>

@julian I have a timestamp and I need to schedule the topic at this timestamp. So suppose that I want schedule topic at 01/12/2017(only) how can I modify the code to schedule the topic at these date?

filter:topics.get does not provide that data, you can probably use one of the page build hooks like filter:category.build filter:recent.build etc. each page has one and it provides alot more data including the url.

You might need to update openssl.

The relevant notification functions are Notifications.create and Notifications.push When a notification is created, the time is always set to the current time, but we may consider making this changeable if there is interest. You'll probably want to use node-cron in your plugin to schedule a notification push to a future date.

I think you're right... in the case of an anonymous function, the function itself would be in memory too. Then in that case, it's probably just easier to set up cron in general

It's default sorted by latest reply.

You'll want to listen to the filter:categories.build hook. You can remove all of the code creating the route override.

@julian and If I want obtain the latest post's pid , for every "Lastest post" in every categories and sub categories, how can I do that? What is the hook that I have use?

How did you "install" the plugin? npm install will install dependencies, a simple git clone will not. You will need to run npm install inside the plugin folder.

You may also want to consider using cron.

You can use the filter:<templateName>.build hooks. For the category page it would be filter:category.build, for a topic page it would be filter:topic.build and so on.

I don't think there's anything in core. But you could probably use the filter:topics.get hook and remove topics with a timestamp greater than now.

@baris correct answer! thanks!

Could be emitting because of some queued requests from socket.io, and the server going down and reconnecting... socket.io behaves badly and sometimes floods the server with queued up calls, hence we added this detection to temporarily drop the connection.