• 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

Guest API with buggy characters

M

mrladeia

Chevereto Member
Hello

I was running the very old version of Chevereto (3.13) and as it is a very old version, I had to manually upgrade the database to version 3.20 and then I managed to upgrade to version 4.

Observation:
I don't know if I did it the best way either. (Can you tell me any problems that this can cause)

By the characters that appeared in the api key field, it looks like the system tried to do some decryption. However, as my upgrade was just the structural database, the update did not encrypt the api, (probably in previous versions this happened)

I would like to know how I can fix this and if this process I did can cause other problems.

So far I haven't identified any problems with this upgrade I've done, except for the one below:
The Guests API field had the field with a problem, see the screenshot below:

1689302957673.png


Bonus Comment:

I made a big update in the translation of pt-BR v4, there was a lot of things wrong and I'm still revising. Do you have any prediction of when you will make available a release with the updated translation?
 
mrladeia said:
By the characters that appeared in the api key field, it looks like the system tried to do some decryption. However, as my upgrade was just the structural database, the update did not encrypt the api, (probably in previous versions this happened)
Click to expand...
Yes, when you updated something went wrong and encryption wasn't configured properly. You need to re-create that public API.
 
... Have you tried clicking on the input field and type the key you want?
 
You must log in or register to reply here.
Back
Top