Tech Support

The only possible way without code changes would be to use max_duration and max_duration_webmasters combined. You can change status for whitelisted users to Webmaster. Then in video_edit block settings set max_duration = 1 (so that it is not possible to upload videos with bigger duration than 1 second) and at the same time set max_duration_webmasters = 9999999 (so webmasters can upload longer videos). It will also be possible to adjust error message in Website UI -> Texts. Find this text: validation.video_edit.content_duration_maximum = Video must be no more than %1% seconds You can change it some other message indicating that only whitelisted users can upload. Unfortunately not possible at the moment.

Yes, you can filter videos list by Other -> Vertical filter, then choose Mass edit filtered videos at the bottom and in mass edit GUI run this option for them: This will replace screenshots for these videos with the merged 3-in-1 according to your new screenshot options.

Yes, we think that PHP 8.1 was tested quite enough and all major issues were fixed in 6.2.1.

Please go to Website UI -> Pages and search for video_edit. It should show you link to Video Edit block on [Memberzone] My Profile page. Then open it for editing and set format_video_group_id parameter to the ID of Original group (admin panel doesn't show this ID, you need to click to Original group and see the ID in the page URL). Then all videos uploaded from users will be automatically assigned to this format group.

Please create support ticket. It may need to be required to enable debug logging to see details from the issue.

Update status 6.2.1 update status is FINAL. We are currently uploading updates for public, this may take several days. We didn't run beta testing for this update, and it might be possible that it will have some bugs. In case of severe bugs we will re-upload the update, so if you updated earlier you may need to re-do the same update procedure once again to get the bugs fixed. Update requirements KVS 5.0.0+ (earlier versions should be updated to KVS 5.0.1 first). PHP 7.1 - 7.4, PHP 8.1. If you haven't yet updated KVS to 5.0.1, then please do, you can find KVS 5.0.1 update information here: KVS 5.0.1 update Important notes for 6.2.1 Please check important notes for 6.2.0 if you didn't yet update to this version. Please check important notes for 6.0.1 if you didn't yet update to this version. Please check KVS 5.5.0 and vertical screenshots issue in old projects issue if you didn't yet update to this version. Please check important notes for 5.4.0 if you didn't yet update to this version. Please check important notes for 5.2.0 if you didn't yet update to this version. 6.2.1 update procedure (please check for known issues section) Any project starting from 5.0.0 can be updated to 6.2.1 with one only procedure. Depending on your current KVS version, update procedure may contain additional steps for older versions. Known issues: For some reason on some ZIP archives you may see Windows antivirus alert for admin panel JS file inside the archive (/admin/js/admin.js). This looks to be a false positive alert due to randomly encrypted JS file. KVS update ZIP archive cannot make harm for your PC, because you are not intended to "run" anything on your local PC, and it even doesn't contain any executable files at all. You must use KVS update plugin in order to update your project. For update you will need: KVS update ZIP archive for your project and its hash code for update plugin (contact support in beta phase to get these). FTP connection to your project so that you can upload files. Update procedure has the following steps: Create backup using Project backup plugin. You may skip manual backup if you have automated daily backups enabled and you see the backup archive from today or yesterday in the list of available backups. Upload update ZIP into KVS update plugin and specify hash code. KVS update plugin will notify you if there are any custom changes in KVS system files, which will be overridden by update (player skins are not checked here, so they will be silently updated if have custom changes). KVS update plugin will update database automatically. KVS update plugin will ask you to copy files from the archive on top of your project using FTP or filesystem copy. Please make sure you are NOT USING sync functionality in your FTP client, which will delete many files on your server, because obviously update archive contains only part of all files. What you need is just to drag and drop files from update archive on top of your project root folder and confirm their re-writing (excluding _INSTALL folder, it doesn't need to be copied). KVS update plugin will verify the updated files and finalize update procedure. Use System audit plugin to verify that everything looks good. Whats new in KVS 6.2.1 Bugfixing for PHP8 support, support for Cloudflare Turnstile captcha, better support for S3 server connection, ability to cut videos via import / grabbers and some more enhancements and bugfixes. 1) In video import and in grabbers plugin it is now possible to manually specify offset from beginning and end of the downloaded video files when importing them with processing. This is normally needed to cut intro of the source site. 2) S3 storage connection was enhanced with ability to configure timeout and use path-like access points. 3) Advertising will be able to filter out display for known SEO bots if needed. 4) Content stats plugin now will count stats for video preview files, posters and categorization files. 5) S3 backup option was added into Project backup plugin. 6) Google reCAPTCHA plugin was renamed to "Captcha" and now also supports Cloudflare Turnstile captcha. Please note that activating Turnstile will require theme changes. 7) In importing feeds it is now possible to stop running feed at any time. 8) Added video and album stats grouping by user. 9) Added support for displaying satellite stats in admin panel start page. In order to have this, satellites should be also updated. 10) An option was added into storage server to skip SSL certificate validation, which may be useful in certain cases to avoid false-positive error reporting. Also false-positive errors should not appear anymore if site is protected with Basic authentication. 11) It will now be possible to edit search queries that were submitted to your site. 12) list_videos block can now filter videos of the specific format group, and sort videos by quality factor. 13) Nextgen list_xxx blocks now support ability to dynamically exclude data from specific categorization by passing excluded categorization in URL parameters (for example exclude models with the given categories). 14) Bugs that have been fixed: - [SEVERE] Dozens of bugs related to PHP 8 support. - [MEDIUM] An extremely old bug was fixed, which could result in missing object data in HTML titles in some rare cases. - [MEDIUM] Backup plugin settings could be reset without user consent. - [LOW] Lots of small bugfixes in different areas.

In 6.2.0 we did a change that resulted in backward incompatibility with templates related to model gender. Previously KVS used model gender values as: 0 = female 1 = male 2 = other The new model gender values are these: 0 = unspecified / empty 1 = female 2 = male 3 = other Due to that change, there are 2 issues that may arise after updating to KVS 6.2.0+: 1) In model list there is a filtering possible in default KVS theme by model gender. This article provides info on how to fix the broken sorting. If template is not updated, this filter stops working correctly. 2) If your theme is customized to display model gender anywhere in other places, such as model list item, or model view block - the displayed value will be wrong due to value index shift. If you have this in place, please check your code and change model gender indexes as needed by shifting gender_id value by 1. Fixing model list filter A number of changes will be required: 1. Go to Website UI -> Language files and in every language files that you use you need to change this block: models.list_gender.0 = Female models.list_gender.1 = Male models.list_gender.2 = Other like this (basically incrementing the last number by 1): models.list_gender.1 = Female models.list_gender.2 = Male models.list_gender.3 = Other 2. Go to Website UI -> Pages -> [Categorization] Models Videos -> Models List block. In block template do changes: line: {{if $gender_id|strlen>0}} to: {{if $gender_id>0}} line: {{if $gender_id|strlen==0 || $gender_id!=0}} to: {{if $gender_id!=1}} line: {{if $gender_id|strlen==0 || $gender_id!=1}} to: {{if $gender_id!=2}} line: {{if $gender_id|strlen==0 || $gender_id!=2}} to: {{if $gender_id!=3}} Also these changes: {{$lang.models.list_gender.2}} to {{$lang.models.list_gender.3}} then {{$lang.models.list_gender.1}} to {{$lang.models.list_gender.2}} then {{$lang.models.list_gender.0}} to {{$lang.models.list_gender.1}} 3. Go to Website UI -> Pages -> [Categorization] Models Albums -> Models List block. In block template do the same changes as in #2 above. This step may be skipped if your project doesn't use albums.

It is only possible via tokens. First of all you should have an active billing that supports tokens, and have some access packages that provide ability to purchase tokens. Users can then purchase tokens via billings and spend them on purchasing access to individual videos. This is supported by default theme and can be enabled in Website UI -> Theme settings as enable tokens option. Then in Settings -> Memberzone settings you also need to allow purchasing videos for tokens and configure their default price. In order to video being allowed to be purchased, its access level should be set to premium members (either using Access level option, or using Access type option that is configured to be accessible for premium members only). When a non-premium user opens a video which access is limited to premium members, AND tokens are enabled in theme, AND this video has price in tokens, the user will see a form to purchase access to this video with tokens. If there are not enough tokens on user's balance, they should see an option to buy tokens via billing packages. If there are enough tokens, they should see an option to confirm purchase, and once confirmed they will unlock access to this video. Also users can access the list of their purchased videos in their profile page (when tokens are enabled in theme).

Please check Adding / removing menu items section in this article:

It is many places around theme template, everywhere where avatar is displayed.

Please check with host support where the high LA comes from. Could be: Apache, MySQL, FFmpeg, filesystem - based on that info solution varies.

No, this will not affect admin panel.

Did you reach out their support? We don't know anything about their products, so we can't provide any support about this.

Yes, KVS supports watermarks:

Then you can go to Website UI -> Pages and search for video_edit block there. In video_edit block settings set min_duration = 100000, then nobody will be able to upload videos.

This is a matter of design. There is not issue with CLS on KVS default theme:

Website UI -> Theme settings -> enable videos upload by members.

You don't need to uninstall Nginx, Nginx should be normally used as a proxy on top of Apache for static files (JPG, JS, CSS and video files). Also you can use subdomains for localized versions instead of subfolders. This doesn't require any .htaccess specific rules.

Yes, this grabber is not working right now because yt-dlp is not updated with new URL pattern yet. Yt-dlp is trying to fallback to their generic grabber, which doesn't support multiple quality factors and only provides some single video file. You can delete xvideos grabber and install Default Videos, which should work with grabbing only basic info using yt-dlp generic grabber.

The grabber was recently updated with that issue. Do you mean it is still not working?

KVS doesn't have feature to remove watermarks.

It is not technically possible to use popunder advertising in player. A popup will just open a new browser tab with focus, is that what you need? Then you can just use standard javascript onclick handler to open a new browser tab, but we don't see any sense to add such feature into player settings.

Yes, some grabbers may not work with some videos, because they don't provide full quality video files.

No, it is not possible to change video upload types between each other due to complexity of the logic involved.

To add to this question, these are the .htaccess mod_rewrite rules that do the magic for allowing subfolders being used: RewriteCond %{ENV:REDIRECT_REWRITTEN} !=1 RewriteCond %{ENV:REDIRECT_REDIRECT_REWRITTEN} !=1 RewriteRule ^([a-z]{2})/(.*) /$2 [L,QSA,E=REWRITTEN:1,E=LOCALE:$1] They translate https://domain.com/de/someurl/ into https://domain.com/someurl/ and add ENV variable REDIRECT_LOCALE = de