Finally, I made it simpler...

I made a link from /toto/myfiles to public/uploads/myfiles. Then, I wrote this app.get code in my plugin :

app.get('/uploads/myfiles/:file(*?)', function (req, res) {
		// Things TODO with req.params.file for permissions (after work on it)...
		var longfilename = path.resolve('public' + req.url);
		if (fs.existsSync(longfilename)) {
			res.status(200);
			res.sendFile(longfilename);
		} else {
			console.log('Fichier non trouvé');
			res.status(404);
			res.render('404', {path: req.path});
		}
	});

Now, there is no problem with the ajaxify thing... Ouf !

I'm going to open another topic for another question about the 404 error rendering...

@PitaJ Ok ! I do it now.

Thanks ! I had tried this before but something else was wrong.

Now, everything is ok !!! Thanks again !

Hello @yariplus,

Is your plugin compatible with nodebb 1.10.1 ? I can't get widgets working on my site. Thanks in advance for your answer.

Hello !

On this forum (and also mine...), there is no pagination-block visible when we are on /recent or /popular for example.

Is there a simple way to make it working on my forum ?

Thanks in advance.

@PitaJ Thanks ! Success !!!

composer.tpl needed to be in /node_modules/nodebb-theme-oxide-YA/templates/ and not in /node_modules/nodebb-theme-oxide-YA/templates/modules...

Sorry

Must I write a request for nodebb-plugin-composer-default for this :
On small screens, it would be great to be able to replace the write-container with the preview-container on clicking "show preview" and revert to write-container on clicking "show editor" ?

Hello !

I need to change some bootstrap classes in custom-page.tpl (to change sidebar dynamical width for example as I have already done it in my own theme templates files). I can do it directly in nodebb-plugin-custom-pages/templates/custom-page.tpl but it will be replaced on each package upgrade... Not great !

Is there another way to do it without this problem ?

Thanks in advance !

Finally, I made my own plugin with hook filter:email.modify. I activate it when on Dev and it redirects all emails to a special email address (to control things).

Sorry for the "noise"...

Hello !

I succeeded in adding LaTeX on my nodebb forum but my solution is bad for maintenance (all plugin I found to do that had defaults so I made my own work)... I think there is a greater/more elegant way ; here is the reason for this message .

Here is my method for now :

• I forked nodebb-plugin-markdown (named it nodebb-plugin-markdown-YA).
• I added into package.json these dependencies : katex and markdown-it-texmath.
• I copied katex.min.css from katex to nodebb-plugin-markdown-YA/public/less/katex.min.less.
• I copied "fonts" dir from katex to "nodebb/public".
• I changed nodebb-plugin-markdown/index.js (bof, bof... ). Here is the diff between nodebb-plugin-markdown/index.js and nodebb-plugin-markdown-YA/index.js :

2a3,6
> // YA add-on for LaTeX (markdown-it-texmath + katex)
> var katex = require('katex');
> var MarkdownItTexmath = require('markdown-it-texmath').use(katex);
> 
52c56,57
<                       href: nconf.get('relative_path') + '/plugins/nodebb-plugin-markdown/styles/' + (Markdown.config.highlightTheme || 'railscasts.css'),
---
> //  YA change for LaTeX (markdown-it-texmath + katex) - plugin renamed !
>                       href: nconf.get('relative_path') + '/plugins/nodebb-plugin-markdown-YA/styles/' + (Markdown.config.highlightTheme || 'railscasts.css'),
115c120,123
<                       parser = new MarkdownIt(_self.config);
---
> //  YA change for LaTeX (markdown-it-texmath + katex)
> //                    parser = new MarkdownIt(_self.config);
>                         parser = new MarkdownIt(_self.config).use(MarkdownItTexmath, {"delimiters" : 'dollars'});
> 
236a245,246
> //  YA change for LaTeX (markdown-it-texmath + katex)
> //  checkboxes make some bad things with LaTeX so desactivate it
238,241c248,251
<               parser.use(require('markdown-it-checkbox'), {
<                       divWrap: true,
<                       divClass: 'plugin-markdown',
<               });
---
> //            parser.use(require('markdown-it-checkbox'), {
> //                    divWrap: true,
> //                    divClass: 'plugin-markdown',
> //            });

Is there a greater way to do these things keeping nodebb-plugin-markdown unchanged and installed ? I can write another plugin to apply my changes (add LaTeX with markdown-it-texmath and katex and remove markdown-it-checkbox use) but is it really possible and, if yes, with which hooks ?

It would be really simpler for maintenance (and also more beautiful... )...

Thanks in advance for help !

Success ! I have been able to implement spectrum as a button in composer without using addButtonDispatch. Ouf !

Hello !

I gave up with bootstrap-colorpicker.js not being able to integrate it in the composer.

I tried another thing... but also without success . I wanted to add a button into the composer to choose text color with spectrum.js. This library loads fine (after little changes in spectrum.js for define and jQuery) but how is it possible to add this color <input> as a toggle button in default composer ?

It's not the same thing as using addButtonDispatch no ?

Finally, I made my own plugin with hook filter:email.modify. I activate it when on Dev and it redirects all emails to a special email address (to control things).

Sorry for the "noise"...

Hello !

I have a Prod nodebb site (which works ; cool ) and I make all my tests/changes on a Dev one on my local machine.

I copy Prod to Dev site without problem (adjusting config.json etc...). But what adjustments do you recommend for emails ? How to do them from command line ? I don't want users to receive emails from my Dev system...

On drupal, I have a module which catches emails on Dev to prevent their sending (it is activated in a settings file ; I can see what would have been sent). On nodebb, can we do the same thing ? Can we activate this from command line or from a file ? (It would be great to have a setting about email sending in config.json to simply change the behavior depending on the Prod or Dev system, like on drupal...). Or can we redirect all mails to one address for tests ?

I suppose nodebb developpers have a solution for this (they don't send emails to every users from their development machine and can test their mail system ).

(Precision, in case it would be necessary for the answer : I use mailgun stmp on my nodebb Prod).

Example of try :

• Copied nodebb-plugin-extended-markdown as a basis of my plugin (unchanged, it works with colorpicker "of nodebb" like I said above).
• Added to dependencies in package.json :

"bootstrap-colorpicker": "^2.x"

• Added to plugin.json :

"modules": {
        "bootstrap-colorpicker.js": "node_modules/bootstrap-colorpicker/dist/js/bootstrap-colorpicker.js"
    }

• I replaced the require call in client.js like this :

require([
            'composer/formatting',
            'composer/controls',
            'translator',
//	    'vendor/colorpicker/colorpicker',
	    'bootstrap-colorpicker'
	], function (formatting, controls, translator) {
            if (formatting && controls) {
                // params is (language, namespace, callback)
                translator.getTranslations(window.config.userLang || window.config.defaultLang, 'extendedmarkdown', function (strings) {
                    var composerTextarea;
		    $('li[data-format="color"]').colorpicker();
// Commented all the following from initial plugin
//                     $('li[data-format="color"]').ColorPicker({
//                         eventName: 'showPicker',
//                         color: '#a67f00',
// ......

• I commented also the last line in client.js here :

                    formatting.addButtonDispatch('color', function (textarea, selectionStart, selectionEnd) {
                        if (selectionStart === selectionEnd) {
                            controls.insertIntoTextarea(textarea, '%(#a67f00)[' + strings.color_text + ']');
                            controls.updateTextareaSelection(textarea, selectionStart + 3, selectionStart + 9);
                        } else {
                            var wrapDelta = controls.wrapSelectionInTextareaWith(textarea, '%(#a67f00)[', ']');
                            controls.updateTextareaSelection(textarea, selectionStart + 3, selectionStart + 9);
                        }
                        composerTextarea = textarea;
//                        $('li[data-format="color"]').trigger("showPicker");
                    });

(I must find with what I must replace this last line to call the colorpicker... but the problem is not here...)

Then, after build of course, when I open the editor in nodebb, I have this message in the console.log of the browser :

TypeError: e is undefined      bootstrap-colorpicker.js:1:21152

At 21152 corresponds "e.colorpicker=o;" in the following extract of bootstrap-colorpicker.js :

this.element.trigger({type:"changeColor",color:this.color,value:this.input.val()})}};e.colorpicker=o;e.fn.colorpicker=function(t){var i=Array.prototype.slice.call(arguments,1)

I think I make a big mistake in how to use the colorpicker or implement it in nodebb but I'm not a js expert (I learn about it each day ).

Hello !

I develop an extension for the markdown editor with a color button to change text color. I started from nodebb-plugin-extended-markdown where there is the same thing with a color picker... It uses the nodebb "integrated" color picker (vendor/colorpicker/colorpicker) but I need to change it for two reasons :

• Like in nodebb acp, there is a "bug" when clicking in the palette of this color picker : it's necessary to tap and move to select a color, which is counter-intuitive... (I don't know if it's necessary to write a bug report for this on nodebb github...).
• I need a greater color picker, like bootstrap-colorpicker (https://github.com/farbelous/bootstrap-colorpicker) which has good options (preselector colors...).

But... all my attemps to use bootstrap-colorpicker (v2 or v3) fail.
Do you have some guidelines to help me ? How can I have the bootstrap-colorpicker opening/working after click on my composer button added in the nodebb composer ?

Precision : step to disable markdown-it-checkbox in code is now not necessary since the following change made by @julianlam in nodebb-plugin-markdown...

https://github.com/julianlam/nodebb-plugin-markdown/issues/108

alfazaz created this issue in julianlam/nodebb-plugin-markdown

closed How to disable use of markdown-it-checkbox... #108

Hello !

I succeeded in adding LaTeX on my nodebb forum but my solution is bad for maintenance (all plugin I found to do that had defaults so I made my own work)... I think there is a greater/more elegant way ; here is the reason for this message .

Here is my method for now :

• I forked nodebb-plugin-markdown (named it nodebb-plugin-markdown-YA).
• I added into package.json these dependencies : katex and markdown-it-texmath.
• I copied katex.min.css from katex to nodebb-plugin-markdown-YA/public/less/katex.min.less.
• I copied "fonts" dir from katex to "nodebb/public".
• I changed nodebb-plugin-markdown/index.js (bof, bof... ). Here is the diff between nodebb-plugin-markdown/index.js and nodebb-plugin-markdown-YA/index.js :

2a3,6
> // YA add-on for LaTeX (markdown-it-texmath + katex)
> var katex = require('katex');
> var MarkdownItTexmath = require('markdown-it-texmath').use(katex);
> 
52c56,57
<                       href: nconf.get('relative_path') + '/plugins/nodebb-plugin-markdown/styles/' + (Markdown.config.highlightTheme || 'railscasts.css'),
---
> //  YA change for LaTeX (markdown-it-texmath + katex) - plugin renamed !
>                       href: nconf.get('relative_path') + '/plugins/nodebb-plugin-markdown-YA/styles/' + (Markdown.config.highlightTheme || 'railscasts.css'),
115c120,123
<                       parser = new MarkdownIt(_self.config);
---
> //  YA change for LaTeX (markdown-it-texmath + katex)
> //                    parser = new MarkdownIt(_self.config);
>                         parser = new MarkdownIt(_self.config).use(MarkdownItTexmath, {"delimiters" : 'dollars'});
> 
236a245,246
> //  YA change for LaTeX (markdown-it-texmath + katex)
> //  checkboxes make some bad things with LaTeX so desactivate it
238,241c248,251
<               parser.use(require('markdown-it-checkbox'), {
<                       divWrap: true,
<                       divClass: 'plugin-markdown',
<               });
---
> //            parser.use(require('markdown-it-checkbox'), {
> //                    divWrap: true,
> //                    divClass: 'plugin-markdown',
> //            });

Is there a greater way to do these things keeping nodebb-plugin-markdown unchanged and installed ? I can write another plugin to apply my changes (add LaTeX with markdown-it-texmath and katex and remove markdown-it-checkbox use) but is it really possible and, if yes, with which hooks ?

It would be really simpler for maintenance (and also more beautiful... )...

Thanks in advance for help !

Hello,

Is there a way to ajaxify widgets like the header ? For example, I have a online users widget (+ a shoutbox also) in a sidebar which doesn't need to be reloaded from scratch on each changing of page when navigating on my forum site.

I can make changes in code but does someone have some guidelines to be able to do it ? I never played with ajaxify...

Thanks !

@baris OK. I made an issue on nodebb github see(https://github.com/NodeBB/NodeBB/issues/7770).

Thanks for your answer !

alfazaz created this issue in NodeBB/NodeBB

closed Disable user to quit a group (permission) #7770