• 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.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

Procedure for reporting multiple errors or abnormalities?

DeCysos

Phoenix Foto Service
Is it more appropriate for any mistake or conspicuousness to create your own thread or is it more pleasant to compile per bug / eye catching collected in a thread?

Example:
  1. I notice that one language variable is missing in file xyz ....
  2. I notice that one function does not work
  3. I notice a file that generates a 404 error because it does not exist, for example.

Well these are now three errors / abnormalities.
 
I don't mind that much long as easy to understand which is a whole universe on its own. Sadly, I don't think that there's any rule that can help to get a more easy to digest report, at the end it all depends on the experience of the user.

Long as the user know what is going on the more likely it will be easier to tell us the problem and how to deal with it.
 
Back
Top