@julian - Installed a web browser on my Moto 360 just to try this out. The result:
And a Youtube video, just for good measure (processing as of 10:30 Eastern):
@julian - Installed a web browser on my Moto 360 just to try this out. The result:
And a Youtube video, just for good measure (processing as of 10:30 Eastern):
You can use normal HTML comments like <!-- comment here -->
. If you really don't want the comment to be output in the html you can do something like
{{{ if @false }}}
Comment goes here
{{{ end }}}
@aStonedPenguin You can use grunt to automatically watch assets and recompile + restart whenever changes are made
It will even only recompile the assets that were changed.
Edit: also, if you want to avoid changing files in the first, you may want to learn how the devtools work so you can edit CSS live, and even add those changes to local files automatically.
https://developers.google.com/web/tools/chrome-devtools/inspect-styles/edit-styles
https://developers.google.com/web/tools/setup/setup-workflow
@teh_g you can use n
to install a later version of Node if you want. Look up "n install NodeJS" it's super easy.
https://github.com/suguru03/neo-async
Crazy. Absolutely crazy. How did he do it?
It appears he removed the event emitter and some of the limit functions which was able to speed it up. Interesting.
@xen It really depends on the size of your forum and what you're willing to pay for. Redis works by storing your data in RAM, so if you have a super huge forum, it can run out of RAM space. Mongo stores data directly to disk, so you get much cheaper storage. As far as performance cost with NodeBB, the difference is negligible as most of the request time is spent parsing templates, not requesting data.
@CCob yep pretty much.
@evoixmr I'd like to stay within the bounds of NodeBB as much as possible so I probably won't ever add direct email invites. I may add invites for users of the forum. Go ahead and open an issue with your requested features at http://GitHub.com/pitaj/nodebb-plugin-calendar/issues
Notifications will be sent via email if the user has that set up on your forum.
Grunt!? Why not any of the billions of other choices you could have made for this?! /s
@Michael-Pfaff you may also consider donating to some of the open source modules NodeBB relies upon, or to the creator of your favorite theme / plugin.
This was due to NodeBB/NodeBB#5727
It's fixed in latest master
As with any open system, some projects will be abandoned due to lack of interest of available free time from the developer in charge. If you see a plugin that doesn't appear to have recent activity and which doesn't work on newer versions of NodeBB, then most likely it is abandoned. The only way to find out if a plugin works is to test it yourself at this point, though I believe a thing is planned that will automatically check plugins for failures to run for each new release of NodeBB, and would notify the respective maintainer(s) of that incompatibility.
If I were you, I would do this in core. You will need to add functions to get topics filtered by tag, add the necessary elements in the core themes, add socket endpoints for the filtering, and add the necessary client side code to make all it work.
It will still be easier than writing it as a plugin.
Here's how I do it:
npm i npm@4
so it doesn't use npm@5
, cuz that breaks nodebbdev
directory in home foldergit clone https://github.com/nodebb/nodebb
, clones into ~/dev/nodebb
git clone https://github.com/nodebb/nodebb-plugin-emoji
, clones into ~/dev/nodebb-plugin-emoji
cd nodebb-plugin-emoji
, npm link
cd ../nodebb
, npm install
, ./nodebb setup
npm link nodebb-plugin-emoji
, this "links" the plugin into node_modules, which is better than having the git repo directly inside node_modules@tigger I have a plan to rewrite this plugin to do exactly that at a later time.
@agarcia17 I guess I'll have to do it, then -_-
You want to add your privilege by adding a hook handler for each of
filter:privileges.list
filter:privileges.groups.list
filter:privileges.list_human
filter:privileges.groups.list_human
In the .list
ones, you should have something like this:
exports.privilegesList = function (list, callback) {
list.push('your_privilege_id');
callback(null, list);
};
and in the .list_human
ones, you want to add a human-readable name or provide a translation token
exports.privilegesListHuman = function (list, callback) {
list.push('[[admin/your_plugin:your_privilege_id]]');
callback(null, list);
};
All this does is add these privileges to the ACP interface for configuration. You can use the methods provided by the privileges
core module to actually apply that permission, through methods like:
privileges.posts.can
privileges.topics.can
privileges.categories.filterUids
privileges.posts.filter
You'd have to listen to other filter hooks in order to filter topics from the category listing and prevent users from viewing those topics via direct link.
Here's an example of using a custom privileges from my plugin
New version. Please update to [email protected]
if you're willing to run the master branch.
npm install nodebb-plugin-calendar@latest
Changes:
invalid
events by hitting the button in the composerLast night, took a look at the composer and improved the performance substantially. I also changed the positioning to use top
instead of translate
for better compatibility.
NodeBB/nodebb-plugin-composer-default#12
Also, just want to remind you of my other PRs, NodeBB/nodebb-theme-persona#171 and NodeBB/NodeBB#3769
Have you tried looking at what Q&A does? The source is here