Tech Support Posted May 18, 2018 Share Posted May 18, 2018 Update status 4.0.2 update status is FINAL. You can download update in KVS client zone for all your licenses: Update procedure Any project starting from 3.0.0 can be updated to 4.0.2 with one only procedure. Depending on your current KVS version, update procedure may contain additional steps for older versions. 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. If your project's version is 3.9.0+, the update procedure is standard and nothing special is expected: Create backup using Backup plugin. 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. You will need 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 doen't need to be copied). KVS update plugin will verify the updated files and finalize update procedure. You can use System audit plugin to verify everything looks good. If your project's version is before 3.9.0, the update procedure will be difficult and will include cache reset for the whole site (if you have much traffic it can make your project to be unavailable for some time). Also 3.9.0 update can have issues with displaying the new player if conflicting with your design styles, please check this post listing all issues: https://www.kernel-video-sharing.com.../28-kvs-v3-9-0 Specific to 4.0.2 4.0.2 update contains set of player VAST bugfixes. If your project is already 4.0.1 and you want to simply get player bugfixes from 4.0.2, you can replace this file on your installation with the new version from kvs-demo.com: https://kvs-demo.com/player/kt_player.js If you are not interested in other fixes in this update, you won't need to update your project, taking player JS file is enough to get all player bugfixes. If your project accepts payments and uses KVS payment processors, it is recommended that you update it to 4.0.2 to get the new way of logging. What's new in 4.0.2 1) Added Google ReCAPTCHA integration, which allows replacing all KVS captcha. In order for it to work correctly, massive theme template changes are required. They will be described on forum. 2) KVS will now support dynamic pricing from CCBill added as a separate payment processor (CCBill Dynamic Pricing). 3) In paid access package settings you can now enable filtering by countries, so that certain access packages are only available for certain countries. This will let you configure access packages in different currencies; also you can use this feature to make special offers for different market segments. 4) It will now be allowed to change conversion server libraries configuration directly from admin panel. Previously if you needed to change this, you could do only via conversion server filesystem. 5) In models death date field was added. 6) In grabbers we changed the way how the time part of post date is populated. Previously you could configure to take post date from the source site, but its time part was always randomized between 00:00 and 23:59. Now we added additional option to enable time randomization, and if the option is not enabled, grabber will set time to the current server time as the new default behavior. 7) Video quick preview in admin panel will not open a separate window anymore, it will show a modal layer on top of existing window. 8) When displaying list of site pages and if your page components have a lot of global blocks used in them (e.g. header, footer), these global blocks will be listed for all site pages and make page list display too cluttered. We fixed that by grouping such global blocks under the single row with ability to expand it. 9) We started a long-running task to refactor block parameters and documentation. Block parameters will be logically grouped and displayed in similar grouped way, so that they are easier to understand and navigate. Block documentation will be updated with the latest scenarios and practices. Block default templates will also be updated to render all possible data fields (all possible input field for form blocks). This will let you easily render the needed data by simply copy-pasting the needed code from default template of a block. This is a multiple-version task: since we have almost 60 blocks it will take some time for us to silently update them all. 10) In response to GDPR enforcement we reviewed data sets stored by KVS for registered members and made some fixes to reduce data storage in certain cases. Starting from 4.0.2 KVS will not keep login and transaction logs anymore when a member is deleted from KVS. We will also provide a statement on our forum to describe information that is being used and stored by KVS for registered members. 11) Models (list_models) and categories (list_categories) list blocks were extended with ability to display list of related models (categories) by videos and albums they are used together with the current model (category). 12) In signup block you can now configure that access code field is required; so that only users who have access code can register. 13) In logon block it is now possible to restrict only users with webmaster status to log in. This option may be useful if you want to separate memberzone into members and webmasters, which all have different functionality. 14) In logon block it will also be possible to set up 3rd-party callback for logging all login events. If you are using NATS, it provides such callback script to record all logins for additional analysis. 15) In internal messages list block (list_messages) it is now possible to batch approve or reject all pending friendship invitations. 16) Added several display modes in mixed content list block (list_content) to align this block with standalone video / album lists. 17) Bugs that have been fixed: Exoclick should now correctly consider all VAST stats from KVS player. When start screen advertising was enabled together with VAST, start screen advertising was not clickable. The option to skip N videos before showing the next pre-roll ad was distorting VAST advertiser stats, as player requested VAST tag even if advertising was not displayed. Now it was fixed to only load VAST tag when pre-roll is going to be displayed. Vertical videos were handled incorrectly with the new ffmpeg versions. Fixed memory leak in mass editing and content stats plugin when processing huge amount of videos. When videos half-processing was enabled, secondary tasks had default priority; should have had the same priory as primary task's priority was. In some rare cases uploading new photos to existing albums would result in background task error without no reason. In category groups list block (list_categories_groups) there was incorrect avatar URL rendered. Tag directory was not always re-generated correctly. Model auto-selection plugin didn't consider models with numbers in their titles. No error message was shown when uploading ZIP archives that are password protected. Grabbers will not be using GoogleBot user agent anymore. This allowed some sites to block such requests. Category avatar generation plugin and videos sub-selection for each category in category list block did not consider category CTR stats correctly when using CTR sorting. They were using global CTR stats instead of category-specific CTR stats. When upload was configured via subdomain, it would stop working if enable uploader access restriction that we've added in 4.0.1. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.