@julian I will give it a try, Thanks so much.

@sebastián-cisneros Im not sure if this is the right way (probably not) but it seems to be working. Please correct me if im wrong.

$(document).ready(function() {

	$(window).on('action:ajaxify.end', function(ev, data) {
		if ($('html').hasClass('composing')) {
			var $cancelComposer = $('#taskbar .taskbar-composer a');
			$cancelComposer.trigger( "click" );
		}
	  });

});

basically on action:ajaxify.end , this is after you loaded the new page (search or topic detail page), you trigger the taskbar-composer button that hiddes the composer.

In the composer, while writting the title of the topic, you get like a dropdown quick search of topics with the same title

if you have a lot of resulst, in that dropdown you can see a link to "see more resulsts". This link loads the Search page with the string of the title, that's perfect; but the composer popup/modal is still open at the top of the search page, so you actually don't see that the page has changed. Is this a bug or a feature?

I can see this problem in this same https://community.nodebb.org/ install. Anyway I can close the modal/popup after you get redirected to the search page so the user can see the search page?

Same thing happens if you click on any of the resulsts of that dropdown quick search of topics.

I already created a custom field in the composer, and is working perfect. Now I want to add some validation, just like the one nodebb core has when you try to publish a topic without a title and you get this alert.

How can trigger this same alert with a different message and avoid the composer to submit (until this field validates)?

@baris following up on this, I think i got this fixed the way I needed, but just in case, I would like to hear your opinion.

So, I took src/topics/sorted.js in the nodebb source code, copied to my theme, and requiere my customSorted.js instead of nodebb's sorted.js

That way I can make my custom updates to the nodebb core, without actually changing nodebb src code.

Becuase of some requierement of the project im working, we are NOT using categories, so I just have setup 1 category, and all topics go to that category. So, when I do all queries I need to do to topics, I ALWAYS set 'cids' to the default category i've already setup.

For this reason, when I do 'topics.getSortedTopics...' with cids = 2 , in the sordted.js file this function gets call 'async function getCidTids(params)'

in that function, 'if (params.tags.length)' , in my case true when I call it with multiple tags, this get's fired 'return _.intersection(...await Promise.all(....'

Changing that 'return _.intersection(...await Promise.all(....' to 'return _.union(...await Promise.all(....' fixes my problem. I've done some testings and all seems to be working just fine.

Another function I got my eyes on in that same sorted.js file is

const method = params.sort === 'old' ?
			'getSortedSetIntersect' :
			'getSortedSetRevIntersect';

maybe to ?

const method = params.sort === 'old' ?
			'getSortedSetUnion' :
			'getSortedSetRevUnion';

any comments on these two things? Am I maybe breaking something I didn't noticed yet?

Again, thanks for the help.

I'm using this function

topics.getSortedTopics()

and there is a param "sort" that can sort reulsts by 'recent', 'old', 'posts', and 'votes'. But I was wondering , is there a way to get the resulsts sorted by view count?

@baris I just noticed that all these functions

await getTids(params);
await sortTids(data.tids, params);
await filterTids(data.tids.slice(0,meta.config.recentMaxTopics), params);
await getTopics(data.tids, params);

are not exported on the Topics module, I there is no way for me to use them without updating nodebb source code.

@baris what about doing something like this ?

get all Tids that have each tag

await getTids(params);

then merge those results in a big Tids array

then sort that array of Tids

await sortTids(data.tids, params);

then filter that sorted array

await filterTids(data.tids.slice(0,meta.config.recentMaxTopics), params);

then get all the topics from the filtered sorted array

await getTopics(data.tids, params);

what do you think?

@baris this can work, but I need to paginate the results.

So to get ALL the Topics from each one of the tags, and then merge those results, then sort this merged array (by recent/views/votes) and then just return the section of the array that meets the page I want to show.

this can get slow, right?

is there another way I can get this done? may be directly quering the DB? or a better way?

So, I'm aware that you can call this nodebb core function

topics.getSortedTopics()

and send as a parameter tag or tags (array of tags), this function returns topics that have all the tags in the array, right?

Is there a way to get topics that have at least 1 of the tags in the array?

@baris you are a rock star!