• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • 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

Procedure for reporting multiple errors or abnormalities?

DeCysos

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.
 
Sort by date Sort by votes
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.
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top