• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • This community is user driven. Be polite with other users.
    • We recommend purchasing a Chevereto license to participate in this community.
    • Purchase a Community Subscription to get even faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Search function for tags match all

mikaa

Chevereto Member
Thank you for your feature request.

Yes, the system already supports filtering tags with an AND condition. You can achieve this by using /?match=all in your URL.

For example:
Code:
/tag/tag1,tag2/?match=all

I chose not to use operators like + or - to keep the syntax simpler and to avoid restricting these characters within a tag. The - character is particularly problematic because it is commonly used to separate words, such as in pokemon-fire, and it wouldn't be possible to use it as a tag if it were an operator.

Thank you for your suggestion. If you have any more ideas or need further assistance, please let us know.
Hello, thank you!

Just tried (/tag/pokemon,layout/?match=all) but go an error :

HTML:
PDOException in /var/www/html/app/src/Legacy/G/DB.php:153

# Message [Code #42000]
SQLSTATE[42000]: Syntax error or access violation: 1140 In aggregated query without GROUP BY, expression #1 of SELECT list contains nonaggregated column 'chevereto.chv_tags_files.tag_file_tag_id'; this is incompatible with sql_mode=only_full_group_by

# URI
/tag/pokemon,layout/

# Method
GET

# Parameters
GET: array (size=1)
match => string all (length=3)

# Time
2024-11-14T13:58:25+00:00 [1731592705]

# Incident 673602015d368

# Backtrace
------------------------------------------------------------
0 /var/www/html/app/src/Legacy/G/DB.php:153
{main}()
------------------------------------------------------------
1 /var/www/html/app/src/Legacy/G/DB.php:153
PDOStatement->execute()
------------------------------------------------------------
2 /var/www/html/app/src/Legacy/G/DB.php:168
Chevereto\Legacy\G\DB->exec()
------------------------------------------------------------
3 /var/www/html/app/src/Legacy/Classes/Listing.php:686
Chevereto\Legacy\G\DB->fetchAll()
------------------------------------------------------------
4 /var/www/html/app/legacy/routes/tag.php:139
Chevereto\Legacy\Classes\Listing->exec()
------------------------------------------------------------
5 /var/www/html/app/src/Legacy/G/Handler.php:455
Chevereto\Legacy\G\Handler->{closure}()
------------------------------------------------------------
6 /var/www/html/app/src/Legacy/G/Handler.php:179
Chevereto\Legacy\G\Handler->processRequest()
------------------------------------------------------------
7 /var/www/html/app/legacy/load/web.php:662
Chevereto\Legacy\G\Handler->__construct()
------------------------------------------------------------
8 /var/www/html/app/legacy/entrypoints/index.php:44
require_once(string(length=37))
------------------------------------------------------------
9 /var/www/html/index.php:12
require_once(string(length=46))

Do I need to remove this SQL mode on my side?
 
You can either edit the mode or wait (?) until I announce it as an official functionality. This hasn't been announced yet but nice catch, I wasn't aware.
 
Back
Top