@megger What exactly is the issue?

Indeed it's not an error message. The thing is, that the result should be filtered by

"type": "preside-skeletons",

and suddenly the result is wrong (includes all preside extensions, not only the skeletons) and since nothing changed on the pixl8 stuff nor commandbox the assumption was, that maybe forgebox doesn't respect the filter anymore due to some changes. We already reported this to the Pixl8 team.

There was a ForgeBox release this week so it's entirely psosible there was a regression

This is what's called:

var forgeboxEntries = forgebox.getEntries( searchTerm = "preside-skeleton-" );

(https://github.com/pixl8/Preside-CMS-CommandBox-Commands/blob/stable/commands/preside/new/site.cfc)

@Javier Quintero @jclausen Assuming the recent ForgeBox release started using our Elasticserach implementation can you please look into this

the goal was to get a specific type. So Pixl8 needs to update the command

@madmike_de This CommandBox one-liner shows the proper search in action

repl "$wirebox.getInstance('forgebox').getEntries(typeSlug='preside-skeletons')" | jq results | printTable title,slug,typeSlug,latestVersion

I was taking a look at this particular case and yes the thing is that now that Elastic Search is our default search engine the search returns more records. with the previous implementation if you passed

preside-skeleton-

as the search term would bring back just the records that the slug contained the string

preside-skeleton-

so actually, the search has never looked for the package type but the title, slug, summary, or author. @bdw429s @madmike_de @megger

We improved the ForgeBox search to use Elastic search so it's going to do a MUCH better job at doing fuzzy keyword matching than it did before 😉

you can use the typeSlug param to look for the type as @bdw429s mentioned

Thank you guys!