• 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 3.5.2

Status
Not open for further replies.
Did you mean to copy the files from app/themes/Peafowl/views back into app/themes/Peafowl?

Both of them work, but /views will always override the thing. You only need to move it to /views.
 
OK. You just have the files in both places in the 3.5.2 zip, but only in views/ in 3.5.0.

Also, it looks like the ones in app/themes/Peafowl are the old 3.4.6 versions, and the ones in app/themes/Peafowl/views are 3.5.2.
 
Is for legacy terms, the used one should be at /views.
 
This morning I updated from 3.5.0 to 3.5.1 and now to 3.5.2. But now it seems the api calls do not work anymore.

It keeps returning:
{"status_code":400,"error":{"message":"Invalid API v1 key.","code":100,"context":"Exception"},"status_txt":"Bad Request"}
Even though the api key is right.
 
This morning I updated from 3.5.0 to 3.5.1 and now to 3.5.2. But now it seems the api calls do not work anymore.

It keeps returning:
{"status_code":400,"error":{"message":"Invalid API v1 key.","code":100,"context":"Exception"},"status_txt":"Bad Request"}
Even though the api key is right.

Somebody else had a similar problem. I wonder if this issue is related to the recent 3.5.0 update??
http://chevereto.com/community/threads/sharex-not-working.5367/#post-29641
 
Status
Not open for further replies.
Back
Top