I'm trying to load a default set of global tags so they can be used for the autocomplete function when creating new topics. However, adding new tags in the 'Manage Tags' section doesn't seem to enable this functionality. Is this not the intended purpose of adding new tags through 'Manage Tags'?
I know I can add a set of tags to the whitelist for each category, but that would be a lot of duplicated tags and would also prevent users from adding new custom tags.

Is there any built-in way to achieve this?

I'm trying to build a WYSIWIG composer plugin using summernote with the redactor plugin as a starting point/template. However, at some point between hitting the submit button and the rendering of the final HTML, some filtering seems to be occurring. Is there any documentation available that would help me understand the flow from submission to saving to rendering so I can identify where the filtering happens?

@baris said in Unable to chat:

account/new-chat

Thanks! that was it, I had some custom css that hid the 2nd item in the dropdown menu. That also explains why it worked with the new DB since the custom css was no longer there.

I'm trying to get bi-directional integration working for nodebb running in an iFrame. One of the last pieces left is ensuring that the post index is captured in the browser session stack. I can get the navigation events captured by listening for 'action:ajaxify.end' and using that to postMessage back to the parent so it can then be used for a pushState. I would also like to capture the post index changes as a user scrolls through the posts so it can be reflected in the parent url. Is there an event I can attach to, so these index changes can be captured?

@rod

You can create a plugin that waits on the hook "action:post.save" and fires a method that executes the custom action you define

    { "hook": "action:post.save", "method": "customAction"  },

Details on creating a plugin are available at Creating Plugins

I'm trying to load a default set of global tags so they can be used for the autocomplete function when creating new topics. However, adding new tags in the 'Manage Tags' section doesn't seem to enable this functionality. Is this not the intended purpose of adding new tags through 'Manage Tags'?
I know I can add a set of tags to the whitelist for each category, but that would be a lot of duplicated tags and would also prevent users from adding new custom tags.

Is there any built-in way to achieve this?

@rod

You can create a plugin that waits on the hook "action:post.save" and fires a method that executes the custom action you define

    { "hook": "action:post.save", "method": "customAction"  },

Details on creating a plugin are available at Creating Plugins

I'm trying to get bi-directional integration working for nodebb running in an iFrame. One of the last pieces left is ensuring that the post index is captured in the browser session stack. I can get the navigation events captured by listening for 'action:ajaxify.end' and using that to postMessage back to the parent so it can then be used for a pushState. I would also like to capture the post index changes as a user scrolls through the posts so it can be reflected in the parent url. Is there an event I can attach to, so these index changes can be captured?

@PitaJ For testing purposes, I just short-circuited the Posts.sanitize method in src/posts/parse.js

@PitaJ

I did find the built-in sanitization code and turned that off for testing, but that still doesn't seem to be the source of the disappearing divs. With the redactor composer, sanitization was also occurring within the plugin code. I still want to use the sanitization plugin because it allows for the rules to be customized in one place along with options for further data transformations.

@julian It's mostly working as intended. However, all div tags get stripped out and I'm unable to find any specific place in the code where it might be occurring. I can live without the div tags or just replace then with spans before submitting, but having them stripped out does break some existing html that someone might choose to paste from an existing post/article in another system. Plus, it would be nice to know the entire lifecycle from the 'submit' button to rendering. I've tried following the hooks in the src/posts/parse.js script and the html is still intact at that stage. Yet, by the time it gets rendered they're gone. I am using the sanitize plugin to go along with the new composer, but its been disabled while I chase down the disappearing divs.

@baris said in Unable to chat:

account/new-chat

Thanks! that was it, I had some custom css that hid the 2nd item in the dropdown menu. That also explains why it worked with the new DB since the custom css was no longer there.

I'm trying to build a WYSIWIG composer plugin using summernote with the redactor plugin as a starting point/template. However, at some point between hitting the submit button and the rendering of the final HTML, some filtering seems to be occurring. Is there any documentation available that would help me understand the flow from submission to saving to rendering so I can identify where the filtering happens?

@baris I tried the default theme and that didn't fix the issue. I was able to see the menu option when I installed on a new DB with the same theme and plugins installed. Is there an easy way to reset the settings? I tried nodebb reset -s but that didn't seem to reset the privileges to defaults.

@baris ajaxify.data.hasPrivateChat returns 0