-
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
Work in progress Chevereto v5.0.0 announcement
Improved user profile design now with taller background
User profile gets improved with a taller user background on the profile homepage, for all the other user-land pages the background will be a bit shorter, making better usage of the screen viewport and achieving a better distinction for the user homepage.
User profile gets improved with a taller user background on the profile homepage, for all the other user-land pages the background will be a bit shorter, making better usage of the screen viewport and achieving a better distinction for the user homepage.
Added /api/5/tags/{id} route
This new route will provide the means to manage a tag identified by
This new route will provide the means to manage a tag identified by
id, with a GET endpoint to retrieve tag details like user_id, number of files, count of views and more. The PATCH endpoint allowing to change both name and description and the DELETE endpoint to delete the resource.
Added input report validation on modal forms
Modal forms will now native display the input errors using reportValidity, this means that each input element will inline display the error using your web browser API. It looks like this:
^ In this example, the yellow box error contains the generic error (422 Unprocessable Entity) plus the "Stop words found" which is the inline error now added.
Modal forms will now native display the input errors using reportValidity, this means that each input element will inline display the error using your web browser API. It looks like this:
^ In this example, the yellow box error contains the generic error (422 Unprocessable Entity) plus the "Stop words found" which is the inline error now added.
Removed storage minimum capacity constrain
Before Chevereto V5.0, editing a storage required its capacity to be large enough to accommodate the storage's current usage. This made increasing or adjusting storage capacity unnecessarily difficult, as you had to delete files before making the change.
Storage capacity can now be adjusted without being restricted by the current amount of stored data.
Before Chevereto V5.0, editing a storage required its capacity to be large enough to accommodate the storage's current usage. This made increasing or adjusting storage capacity unnecessarily difficult, as you had to delete files before making the change.
Storage capacity can now be adjusted without being restricted by the current amount of stored data.
Fixed TLS verification for cURL requests in the upgrade process
The
The
upgrading.php file was missing TLS certificate validation. We fixed the TLS bypass, blocking MITM attacks where fake certs let attackers push malicious or downgraded updates undetected.
Added MediaMetadata support to video playback
Chevereto V5 now sets the Media Session API's MediaMetadata during video playback, so browsers and operating systems can show the title, artwork, and other details in their native media controls, such as lock screens, notification shades, and media hubs.
Chevereto V5 now sets the Media Session API's MediaMetadata during video playback, so browsers and operating systems can show the title, artwork, and other details in their native media controls, such as lock screens, notification shades, and media hubs.
Chevereto Cloud
