Tech Support

In paid access in access packages we now added support for configuring countries where this particular access package should be visible. This will allow for the following paid access configurations: - Show EUR prices for the EU countries and USD prices for the rest of the world. - Support different discounts for visitors from different countries. Also added support for CCBill dynamic pricing as a separate payment processor.

Yes, we have it in our feature list but not for the upcoming release. This was already implemented in 4.0.0: https://www.kernel-video-sharing.com/forum/forum/general-discussion/announcements/273-kvs-4-0-implementation-previously-was-3-9-2?p=493#post493 But not for models. This was implemented for members and channels. Your models should be registered as members if you want to use this.

In PHP there is an option which defines which directories PHP is allowed to access: open_basedir http://php.net/manual/en/ini.core.php#ini.open-basedir In your case it is most probably it who locks KVS backup plugin from accessing this path. You should check it in php.ini and adjust to include this path as well. Also we do not officially support OS Windows, so hard to tell, PHP / Apache may have some other limitations or specifics there, which we are not aware.

Thanks, looks clear. We will see if we can do something like that in the existing GUI. Please pay attention to this thread and provide your feedback after we announce changes in this area.

Hello, thanks for your feedback. In Stats -> Transactions there is a total line, which summarizes the filtered list. I think you can get (1), (2), (3) and (4) by selecting date filter from month start day to month end day. It will them summarizes the whole stats for that month period into a single line. We will also add column selector to this table and also add (5) and (7) to the columns. This will let you see the averaged numbers in total line. We will see if we can add ability to group stats lines by months, so that you can switch to this and don't need to select filters to compare different months. What you mean by projected sales? Isn't it the same as just multiple current month sales to the desired amount of months? Or it should also consider growth % and rebills ratio from previous periods? I think this may require additional stats section and probably not in this release. To accurately calculate this we will need more complicated logic here.

Hello, we are working with finalizing migration for your project. Once this is done, we will look into your server settings. Your ticket is still in open status, this means that we are not finished yet. Please be patient.

Thanks for your feedback. The reason why we don't provide this is that we don't have much expertise in this part and thus the only thing we can provide is a compilation of googled info, which is not probably really useful. We keep our local dev environments on ubuntu and found it pretty straightforward to install everything based on manuals found by googling "how to build XXX on ubuntu". FFmpeg trac has a pretty full article on how to build ffmpeg with all dependencies: https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu

Sure we can add it, will also probably add VR flag as well. These are very minor enhancements, we announced only big areas we are planning to concentrate. Meanwhile we will also add a dozen of minor enhancements as we do usually.

We will use this topic to post updates on 4.1 implementation. In 4.0 we didn't implement everything that was initially planned, which probably left some customers frustrated. We are sorry for that, however we cannot guarantee any features prior to when we finally add and announce them. The reason is that everything is being constantly changing and the market is changing all the time, so we have to react to that and adopt our initial plans to the new reality. In 4.0 we were planning some email enhancements there were not even started. In contrast we completely refactored advertising module and did many enhancements in grabbers and player. This was not planned initially, but this became highly demanded during the year. In 4.1 we would also like to share our top level plans, but again we would like to highlight that these are plans, nothing is guaranteed unless finally implemented. Ours plans are actually fully driven by our clients, except some features we are constantly adding for better support (e.g. more logging and etc., features that help us reduce support effort that is constantly being increased with more and more new customers and projects are coming each month). So 90% of the features we are adding are being proposed by you - our valued customers. If you want to propose a new feature, just create a support ticket and try to explain in much details why this feature is useful for you and why you will benefit from it. If we agree that this feature will benefit most of KVS customers, we will definitely consider it even if was not planned. If this feature is very easy to add, we may add it into the next update even if this is a very limited feature and most likely won't affect other KVS users. But if the proposed feature is technically difficult and we are not convinced that it will provide much benefit, then most likely we will refuse to add it in the near future, not because we do not want to work on it, but because we think we have much more important things to add into the next update. High priority features for 4.1 1) Complete emailing refactoring. We know this is annoying issue for many people and would like to finally close it. Requirements that we plan here: Ability to easily set up public email service to send emails (gmail and etc.) Ability to configure email templates in admin panel, extend support for tokens that can be used in emails. Ability to translate email templates to multiple languages similarly to other content in KVS. Ability to enable / disable certain emails from one place. 2) Automated audit and admin notifications. This one becomes more and more annoying as well. Also we think it may help to reduce support by providing constant project monitoring and better understanding of what went wrong. Requirements that we plan here: Create log table to log any issues that arise from time to time. Extend audit plugin with some more checks. Run audit plugin on scheduled basis to make sure that any issues will be reported ASAP. Report summary email to admin on a daily basis (traffic stats, content stats, project status). Report critical issues to admin's email immediately when they are identified. 3) HLS format investigation. We already started this and have some promising results. This is highly demanded feature by many whale customers and projects that render full-length videos. We do not have any requirements defined for it yet, but if our initial investigation goes as planned, this one may be quite easy and we will include it. However if it turns out that we need much effort here, we will postpone this one. 4) For paysites - more alternative payment processors and support for shopping cart. Requirements that we plan here: Crypto billing. Shopping cart block so that members can purchase content without using tokens - just choose what they need and immediately pay the whole amount. Tentative: ability to purchase internal subscriptions as well. Low priority features for 4.1 1) We would like to extend videos and albums for more images you can upload for them. Requirements that we plan here: In videos we would like to add support for 2 images (posters) that can be uploaded separately from screenshots. For these we will create a new screenshot format group, similar to what we already have for overview and timeline screenshots. These new images can be used for enhancing your site theme, e.g. showing some vertical and horizontal images for each video in an advanced layout. In albums KVS already has ability to upload a poster. We will extend to allow uploading one more poster image, so that in total you can upload 2 poster images. Subtitles text file upload for videos. 2) Comments and rating enhancements. Requirements that we plan here: Ability to reply to other comments (hierarchy). Ability to disable comments / rating to specific content (from admin panel and user area). Ability to sort comments by votes (show top rated comments). These are our initial plans for 4.1. We hope that top priority tasks won't take much and we will be able to implement low priority features. If we decide to release 4.1 right after some top priority are done, all other features will become top priority for 4.2. With 4.x we would like to make updates available faster, ideally each 2 months, so that new features go live as soon as possible.

Update status 4.0.1 update status is FINAL. You can download update in KVS client zone for all your licenses: Update cost Starting with KVS 4th generation we would like to change the way we approach to versioning and update policy. Earlier KVS had branches (1.x, 2.x, 3.x) and all updates within a branch were free, but updating to a new branch costed 25% of a new license price for each individual license. Many successful years passed and KVS now has many customers with big number of licenses on their accounts, so updating them all to KVS 4 will mean huge money for them. As a result we have re-balanced our update policy: With regard to versioning we will not use 'branch' term anymore, all new versions will be of 2 types: major feature updates (e.g. 4.1, 4.2, etc.) and minor bugfixing updates (4.0.1, 4.0.2). Minor versions will be announced as usual, but we won't make them available publicly if no critical bugfixes, they will be available on request only. Changing this approach will let us introduce important bugfixes instantly without considering major version current state. Access to any updates will now cost $100 yearly per customer and it doesn't matter how many licenses you have. Any new Ultimate license purchase will give +1 year of free updates since the day of purchase. Any new other license purchase will give +0.5 year of free updates since the day of purchase. All clients who've purchased a new Ultimate license since 15.01.2017 or any other new license since 15.07.2017 will have free access to 4.0 update. For convenience customer zone was updated with this info. All unused licenses will be using the latest version at any time, they will not be connected to any dates. Please note that updating to 4.0 would never be free anyway, we are not adding a payment here that never existed before. The 25% policy was there since 2009. However the 3.x branch was being developed for the last 5 years and all updates within it were free, so this policy has never been applied. The new policy makes it much cheaper to apply 4.x update for customers who have many licenses on their accounts, whilst it doesn't affect much those customers who have only 1 license. Update procedure Any project starting from 3.0.0 can be updated to 4.0.1 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. After you update your project, audit plugin will show a list of KVS #10 issues, this is planned. Please create a support ticket and specify your domain name and make sure KVS support access is enabled on start page on admin panel. Due to category avatar changes we will need to update your templates to comply with new filesystem structure. What's new in 4.0.0 You can find explanations and screenshots for the most of new features in this topic: https://www.kernel-video-sharing.com...usly-was-3-9-2 This topic also contains guides on how to enable some new features that require template changes and thus are not covered by automatic update. You can see some new features in action on KVS demo website and admin panel: http://kvs-demo.com http://kvs-demo.com/admin/ 1) Global enhancements in advertising module: Ability to restrict individual ads to certain devices, browsers and member statuses. Ability to restrict individual ads to be displayed during specific time interval (for example starting on 22:00 and ending on 02:00 every day). Ability to configure advertising start / end datetime with 1 minute precision. Ability to exclude specific advertising from being displayed for certain categories. Advertising spots now allow configuring wrapped HTML code, so that no empty advertising block is displayed when there is nothing to display inside it. Player HTML advertising can now be connected to advertising spots and thus provides easy way to use all the advertising module functionality inside player. Adblock plugin should not prevent saving advertising in KVS admin panel anymore. 2) Many enhancements in conversion module: Video trailer creation optimized, now trailers are created much faster and with less quality loss. Also it is now possible to add crossfade effects to trailers. Moving watermarks are now supported with ability to set speed, direction and any number of positions in seconds and percents for repeat. Ability to switch new videos conversion into 2-phased process: the first phase will only create all required video formats, the second phase will create all high-res formats which are typically declared as conditionally-optional. Thus video will become available faster, no need to wait for all video formats to be created. Added ability to optionally enable screenshot crop settings for manually uploaded screenshots. Previously crop was never used for uploaded screenshots. Background tasks logging was enhanced. Now background task log can show info about all conversion phases and most importantly subtasks and their duration. It is now possible to code a custom PHP script to set up individual crop, rotation or mirroring of a source file for any uploaded video. These options are not exposed for public usage, as they are too specific for most users. KVS will now support uploading audio files directly into MP3 format. In order to use this functionality you should add mp3 extension into list of allowed video extensions in /admin/include/setup.php, and also upload screenshots for every such video. 3) Big set of KVS player enhancements and fixes: Ability to enable auto preload, which gives hint to all devices to start optimistic video buffering before user starts playing. Ability to show related videos on pause (if no pause advertising is configured). Ability to show global video duration in player instead of current format duration. This may be useful for paysites if non-premium users are only able to watch short trailers - then it is better to show full video duration instead of trailer duration. All player HTML advertising is now fully integrated into KVS advertising module. For pre-roll and post-roll advertising the updated skins will show timeline with advertising duration. For pre-roll and post-roll advertising it is now possible to enable VAST from several supported providers. For pre-roll advertising you can now configure so that it is not displayed for every single video, but can skip some videos before next display. In embed player settings you can now set caching interval for embed codes. Previously embed codes were automatically cached up to 24 hours. Fixed wrong behavior of buffer indicator when skipping or switching to another format. Fixed timeline screenshots display issue in some browsers. Fixed full-screen issue in desktop safari. 4) Several important enhancements in KVS storage system: Added support for syncing one storage server from another storage server if they are located in the same storage group. This task is basically required when you move content from one server to another or when you want to duplicate content between several storage servers for load balancing. Previously you could only do that manually, now KVS can do that for you. We extended CDN invalidation API to support additional parameter that describes operation type (add, update or delete). Thus invalidation API will be executed also when new content is added into CDN. You can now disable storage groups, so that they are not used in new content allocation. IP whitelist configured in video anti-hotlink protection settings will now disable all protection levels for the given IPs, including status-based protection. 5) Set of grabber plugin enhancements: Ability to configure command line path to youtube-dl library with all the supported command line options. For grabbers based on youtube-dl KVS will also download video files via youtube-dl, which will allow using aria2 library for multi-threaded downloads without speed limit. For grabbers based on youtube-dl it will be possible to configure proxy servers list if your server's IP gets blocked. All existing grabbers will be switched to youtube-dl soon. 6) Several changes in FTP content upload plugin: Ability to specify video / album description in a separate TXT file. Ability to randomize order in which content will be added. Added display info about duplicates, if detected. 7) Image size settings were enhanced with additional resize type option that will allow now having images with dynamic size (previously it was only possible to have fixed size images for categories, models and etc). Also for categories and members we added 2nd size, so now all images support 2 separate sizes with different resize types. Due to categories avatar migration to a new storage structure it will be needed to modify some code in templates. After update audit plugin will show KVS #10 issue. Please create a support ticket specifying all domains you've updated and make sure that support access is enabled there. 8) KVS now supports internal paid subscriptions for members and channels using tokens. When purchasing a subscription, members will get premium access to all content from the member or channel they are subscribing to, including any content added in the future by this member or into this channel. A subscription can be time-limited or unlimited (configurable by admin). Limited paid subscriptions will be automatically renewed if a member has enough tokens on balance. Otherwise the subscription will expire and member will need to purchase it again to get access. Same as with individual content purchasing, KVS will allow you to set that part of spent tokens are earned by content authors, so that you can have members earning tokens from selling subscriptions to their profiles and channels. In member profile editing and channel editing blocks it is now possible to specify tokens price in tokens_required field. 9) For premium access packages you can now choose whether they are available on signup, upgrade or both. This option can be used for instance to provide some discounts for returning members, while having the full price for new members. 10) Premium access packages can now be purchased with tokens. We added a specific payment processor for handling this named Internal Tokens. So if your site offers free and premium zones, your free members can earn tokens for their activity and then use tokens to purchase access to premium zone. 11) In order to allow accepting payments using different methods, signup and upgrade blocks will now allow displaying access packages from all active payment processors. Thus you can use multiple payment processors at the same time and let users decide which one to use. 12) Members can now be awarded with tokens for logging into memberzone every specific time interval. This can be used to stimulate their activity on your site. 13) In video format settings you will now be able to specify download order for each format you enable download option. Previously the order of download files was not defined. 14) In video format settings you can now limit speed separately for embed code mode. This may reduce your traffic usage and at the same time no need to block embed codes usage. 15) Category and tag auto-selection plugins will now support lenient match for compound tags and categories. This new option will provide better way for languages where word endings vary in different cases. Also will give flexibility in auto-selection handling. 16) Models and content sources now support ranking based on the defined criteria (sorting). You can now display recent rank for each model or content source, and previous rank if changed. Ranking criteria can be set in content settings. 17) In mass editing you can now submit re-creation of multiple video formats at the same time (previously it was only possible to do 1 at a time). Also mass editing now supports access level field. 18) A new interface for videos / albums mass operation added: mass selection. You can use it to select list of videos / albums based on their IDs or URLs and then either filter them, or mass edit them, or delete them. 19) If you use mark video / album as deleted functionality, you can now send notification email right from there. This functionality is typically used to handle DMCA complaints, so sending email with the list of deleted URLs may be useful. 20) When editing videos or albums you can now run category, tag or model auto-selection plugins for them individually. Previously this was only available from mass editing GUI. 21) Exporting feeds can now filter by HD flag. Also you can now choose to simply export 'best' or 'worst' quality for each video instead of specifying direct format name. 22) Admin panel can now search by localized titles / descriptions / directories in all objects that support localization. 23) Website UI section now features version control system, which monitors all changes in theme templates, styles and JS files. This will allow you to rollback any specific change at any time, or restore original version if you have done something wrong. It can also be used with online text compare sites to find what has been changed in a specific version. 24) In website settings it will now be possible to configure that content with 'in process' or 'error' statuses is displayed via direct links. Previously such content would never be displayed. This feature is extremely useful for websites that offer video hosting functionality, users can upload their videos and immediately get embed codes that are not returning 404 error. Please note that you will need to update templates so that such cases display reasonable message, otherwise in most of the themes they will display no access error message. 25) In stats settings for search stats you can now configure max query length and blacklist symbols, which will prevent queries that do not match these filters to be added to your stats. This is needed to prevent some not nice queries to be later displayed on your site. 26) KVS website engine will now be able to produce minified HTML, however this option will not be available in public settings and can only be enabled via /admin/include/setup.php configuration. HTML minification produces single line HTML code without line breaks, however it will result in textareas not functioning correctly (all multi-lined content displayed in a textarea will be wrapped, e.g. video description editing will wrap multi-lined description); and also if you have some inline JS / CSS code without ending semicolon, this will break its syntax. Use at your own risk if needed. 27) In website settings for dynamic HTTP parameters you can now configure their cookie lifetime. Before that their lifetime was forced to 365 days. These are typically used to pass affiliate refs to your site. 28) In content settings it is now possible to configure access to file upload functions. Previously file upload function was available publicly (some sites may need anonymous upload), but now you can only allow it for registered members or admins only. For remote URL uploads you can also set a max filesize limit. 29) In this update we changed the way how tags are added in admin panel. Previously you could only mass add tags in plain list, but now you can mass add tags together with their synonyms; also you can use the same approach to add new synonyms to existing tags. 30) Video player in admin panel editing video page will now allow switching between all video formats, if there are multiple. Previously it would show the biggest size format, which is not always convenient. 31) A very important logical change for webmasters access level. Webmasters will no more have the same access level as premium members, they will have standard access level instead. 32) When overload protection gets triggered for a page, KVS will return 503 status with rendering overload.html contents instead of doing redirect as before. 33) Changed the way how text search behavior works when finding only 1 result (only 1 video, 1 album and etc). Earlier KVS would automatically redirect to this result page by default. After the update, redirect will not happen by default and KVS will simply display search results page with 1 video or 1 album. If you want to have redirect as before, you should use search_redirect_enabled parameter in the corresponding list_xxx block in your theme. 34) Tags list (list_tags) and tags cloud (tags_cloud) blocks now support displaying tags from any objects and not only from videos or albums. KVS also supports tags in models, content sources, posts, channels and playlists. 35) Added a new parameter show_stats to video view (video_view) and album view (album_view) blocks. You can use this parameter to force a block make an additional query and select video or album views stats for the last N days. These stats can be used to show video / album popularity graph for the given time period (the number of days KVS keeps these stats is defined in stats settings). 36) Categories list block (list_categories) can now show list of related categories, e.g. categories from the same group. In order to enable this the new parameters var_category_id / var_category_dir were added, which expect category ID or directory to be passed in URL. 37) Search queries list block (search_results) can now display search queries similar to the given category or tag (e.g. search queries that are using this category or tag). In order to enable this the new parameters var_category_id / var_category_dir / var_tag_id / var_tag_dir were added, which expect category / tag ID or directory to be passed in URL. 38) Posts lists block (list_posts) now supports filtering by custom fields. 39) It will now be possible to display future or upcoming videos / albums. In order to do that you use the new mode_futures block parameter in list_videos / list_albums block. This option is extremely useful for paysites to show the upcoming updates. 40) Bugs that have been fixed: Many player logic and skin fixes (described above). In some cases Epoch processor would close access before the end of period. Domains, that were blacklisted for signup emails would not blacklist subdomains as well. Backup plugin was optimized for satellites. Critical vulnerability that we've sent patch on November 20th. Random video / album redirect was cached for 1 minute and redirected to the same video / album during the whole minute. When using external search plugin KVS would not return 404 error for non-existing pages in search pagination. A dozen of other small usability / stability improvements. What's new in 4.0.1 4.0.1 is a bugfixing update for 4.0.1, though we put some small new features there. Those who already updated to 4.0.0 during first beta phase or had initially 4.0.0 installed, it is recommended to update to 4.0.1 only if you feel the new features or fixes are affecting you. Since 4.0.0 is still in beta, we expect more issues to be found as more projects will be updated, and thus 4.0.2 will be available within the next 30 days. If not, we will make 4.0.1 publicly available in March. 1) Several player enhancements: It will now be possible to use 3rd-party VAST providers for a subscription. At the moment subscription will be free for beta testing period. Advertising would not disappear anymore after being clicked. Enhanced adblock player feature. Now you can configure the amount of time in seconds that adblock user will be allowed to watch. After that player will emulate crash with showing your predefined HTML code instead. Added support for inline playback on Iphones, which will also allow showing pre-roll advertising on Iphone devices. Fixed mute button behavior on mobile devices. Previously it was not displayed for mobile devices. 2) In videos export and exporting feeds it will now be possible to format duration in HH:MM:SS format. 3) Comments list block (list_comments) will support additional mode to display comments to the whole user's content. 4) Channels list block (list_dvds) will support a new mode that allows listing channels available for upload to the given user based on their privacy settings. 5) Several new modes were added for mixed videos and albums list block (list_content). They will allow to display uploaded content, purchased content and content from subscriptions of a given user. 6) Bugs that have been fixed: In some cases moving watermark was not applied to videos.

When exporting videos, it is now possible to select duration format to be HH:MM:SS, previously KVS would only export duration as a number of seconds. Exporting feeds are also affected.

We continue to put fixes towards to 4.0.1 as a result of beta testing by some volunteer projects. There is an additional set of player fixes and enhancements. 1) Mobile players will render mute button, previously mute button was hidden on mobile devices. The mute button seems to be required by some advertising publishers. If you are using custom player skin, you may need to adjust it so that volume button is displayed in controlbar. 2) Advertising will not be closed anymore when it is clicked (this affects start ads, pause ads and pre-roll / post-roll ads). In case of preroll ad users will have to wait for the advertising to complete / or skip button available in order to continue to a video. 3) Enhanced anti-adblock feature. Previously it replaced player immediately disabling ability to watch a video. This might be considered as a red flag for SEO, since some users would simply close the page. Now it will work in another way: it will allow user to play video for some time (configurable) and then it will emulate video player crash with ability to show your custom content instead of player. You can use this to notify your adblock users that they may want to disable adblock plugin for your site to continue watching. We believe this will be a better trade-off between maximizing revenue and SEO. This functionality was tested in Chrome, Firefox and Edge with popular adblock plus plugin. With regard to adblock, some reports suggest that currently 30% of desktop users are using adblock plugins. Taking in consideration that desktop users are approx. 50% of tube traffic, you may be losing up to 15% of revenue. Some well-known advertising providers are getting completely blocked with stock version of adblock plugins. Recently we updated a tube network to 4.0 and all advertising displayed there was not visible at all. Per our experience very few webmasters are using adblock plugins and thus they are not even aware of this issue. The recommendation is to always check your advertising with adblock plugin enabled to make sure that it is not truncated, otherwise you may need to re-think your advertising strategy. Also here are some tips that you should follow: - Never use CSS styles having "ad" or "ads" or "adv" or "banner" or anything like that for advertising sections. Such sections will be automatically truncated by the most of adblock plugins. Use random character sequences for these style names. - Never use a folder named "advertising" or "ads" to server any files from it, these files will not be loaded for adblock users. - Never use advertising files having popular advertising sizes in their filenames, e.g. "banner-800x60.jpg" and similar. Rename your advertising files to neutral filenames.

In modern tube site designs you sometimes need to show separate content for phones in comparison to other devices with bigger screen. There are 2 ways you can achieve that: by configuring mobile subdomain (m.domain.com) and showing a separate mobile version of your site; and by using the same domain with adaptive design and by displaying separate template code for different types of devices. This article will describe both approaches. Configuring mobile subdomain This was a popular approach in the past, but now Google doesn't recommend using it: We don't see any reason why someone would like to use this approach. We can imagine that there is a necessity to show different content for mobile devices (e.g. show only 1 video list with 12 items for mobile, and show several video lists with 24-36 items for desktop), however this can be perfectly implemented with the 2nd approach, when you customize template to show different blocks for different devices. And this is the recommended and easier way of handling such task. However some customers still want to use mobile subdomain for whatever reason, so we briefly describe this configuration. In order to configure mobile subdomain you should configure it to the same directory on filesystem, where KVS is installed and configure it to use separate .htaccess file, if you want to show different KVS pages for the same URLs on mobile and desktop. Here is example Apache configuration that highlights these aspects: DocumentRoot /var/www/domain.com/public_html ServerName m.domain.com ServerAlias m.domain.com AccessFileName .htaccess_mobile So mobile subdomain would be using .htaccess_mobile file, while desktop subdomain would be using standard .htaccess file for URL rewrites. This gives you ability to rewrite the same URLs to separate pages in KVS, for example you can have Index and Mobile Index pages and in .htaccess_mobile you can add this rewrite to route all index traffic to Mobile Index page: RewriteRule ^$ mobile_index.php [L,QSA] Same for other pages if needed. In order to annotate desktop and mobile URLs for Google, you should find this line in header template (Website UI -> Page Components -> include_header_general.tpl): <link href="{{$page_canonical}}" rel="canonical"/> and replace it like this: <link href="{{$page_canonical|replace:"m.":""}}" rel="canonical"/> <link rel="alternate" media="only screen and (max-width: 640px)" href="{{$page_canonical|replace:"m.":""|replace:"//www.":"//"|replace:"//`$config.project_licence_name`":"//m.`$config.project_licence_name`"}}"> If you want to add a redirect of phone devices to mobile, you can add the following code into /admin/include/pre_initialize_page_code.php: // mobile subdomain redirect include_once("$config[project_path]/admin/include/mobiledetect/Mobile_Detect.php"); if (class_exists('Mobile_Detect')) { $mobiledetect = new Mobile_Detect(); if ($mobiledetect->isMobile()) { if ($_SERVER['HTTP_HOST'] == $config['project_licence_domain']) { header("Location: //m.{$config['project_licence_domain']}{$_SERVER['REQUEST_URI']}"); die; } } else { if ($_SERVER['HTTP_HOST'] == "m.{$config['project_licence_domain']}") { header("Location: //{$config['project_licence_domain']}{$_SERVER['REQUEST_URI']}"); die; } } } Showing separate template code for different devices under the same domain Another way is to show some parts of page separated for phones and other devices. This is not about advertising: you don't need any template customization described here for advertising, as advertising supports mobile VS desktop options directly in their settings. This approach is typically used in the following cases: Including different CSS styles for mobile VS desktop. Showing different blocks for mobile VS desktop, mobile block is typically configured to render less items than desktop. Hiding certain blocks for mobile devices, e.g. sidebar, additional content blocks that only make sense for desktop. Step1. In /admin/include/pre_initialize_page_code.php add the following block: include_once("$config[project_path]/admin/include/mobiledetect/Mobile_Detect.php"); if (class_exists('Mobile_Detect')) { $mobiledetect = new Mobile_Detect(); if ($mobiledetect->isMobile() && !$mobiledetect->isTablet()) { $config['device'] = 'phone'; } } If you need to have separation between all mobiles (phones + tablets) and PCs, then you use this: include_once("$config[project_path]/admin/include/mobiledetect/Mobile_Detect.php"); if (class_exists('Mobile_Detect')) { $mobiledetect = new Mobile_Detect(); if ($mobiledetect->isMobile()) { $config['device'] = 'mobile'; } } Step 2. Then in templates anywhere you need you can use this approach: {{if $config.device=='phone'}} mobile phone {{else}} pc / tablet {{/if}} For the 2nd variant of PHP code you should use this template code: {{if $config.device=='mobile'}} mobile phone + tablet {{else}} pc {{/if}} Example to show different list_videos blocks with different settings for phones: {{if $config.device=='phone'}} {{insert name="getBlock" block_id="list_videos" block_name="Mobile Videos Watched Right Now"}} {{else}} {{insert name="getBlock" block_id="list_videos" block_name="Videos Watched Right Now"}} {{/if}} Example to hide sidebar for phones: {{if $config.device!='phone'}} <div class="sidebar"> ... sidebar contents that is hidden for phones </div> {{/if}} Performance implications Separating content for mobile and desktop devices will affect your server's performance because caching % will be reduced up to x2 times. This will mean higher load on your database.

This grabber was fixed in youtube-dl library and now it works.

Hello, thanks for reporting this. The grabber was updated to v10 and the issue with embed code fixed.

There will be likely more VAST advertising providers in the future. For now we will have only these 2.

All KVS themes use the same approach of configuring texts and SEO. In admin panel you can change any text in Website UI -> Texts section. You can simply search by the text you want to change and KVS will show you all texts where this fragment is used: SEO In Website UI -> Texts section filter by SEO group. You will see a lot of texts, which can then further be filtered by Page, for example select Index page: For each page you will normally see 3-5 texts like this: html.index_title - for HTML title of this page html.index_description - for HTML description of this page html.index_keywords - for HTML keywords of this page html.index_seo_title - for SEO title displayed on this page html.index_seo_text - for SEO text displayed on this page SEO title and SEO text are not available for every page, normally they are available on Index and on main lists (videos by category, by tag, by model, by search and etc). The other 3 texts are available for all pages. Some pages that render different lists may have many different versions of these texts. For example Common Videos List / Common Albums List pages render videos by category, videos by tag, latest videos, top rated videos and etc. For each of these variants you will see a set of these texts: On Index page you would normally write some static text there, describing your site or whatever you think may be useful for your SEO. When a list page is displayed by category or tag or search, you should normally show different texts for different categories or tags or search requests to have better SEO coverage. You can do that with using tokens, that will be replaced by some data from category, tag and etc. For example search for texts by this external ID: html.videos_by_category. You will see the following 4 texts: These texts are used on page that renders videos list from a specific category. You can see that these texts use some tokens inside them, the tokens will be replaced with some data from category that is currently displayed. So "%title% Videos" will be replaced with "Music Videos" on Music category and "Funny Videos" on Funny category, "%description%" will be replaced with category description and "%synonyms%" will be replaced with category synonyms. You can play with these tokens to get some unique texts for your site. All supported tokens will be listed below. And there is also advanced opportunity to randomize texts for different objects, which is especially useful in tags and search results, where there can be a big variety of different texts. Consider the following example for tag page title: html.videos_by_tag_title = [rand]Free || Cool || Best || HQ || HD || High quality[/rand] %tag% videos There is a [rand]...[/rand] block inside this text. This block will force KVS to take one of the listed fragments randomly for every tag page. So here are different displays for different tags: Free music videos Best funny videos High quality mobile videos ... The key thing here is that random fragment will remain constant for the same tag, unless you update this text notation - updating it will result in another randomization seed. So there will always be "Free" selected for "music" tag and there will always be "Best" selected for "funny" tag. Again, this will remain constant for the time when you don't touch this text anymore. Once you change it (e.g. change the order of words, or anything else in this text), there may be another random fragments selection. You can use [rand]...[/rand] block everywhere in SEO texts (title, desc, keywords, SEO text and title). But title and SEO text / SEO title are the best places for this. Usually it makes sense to use this with tags and search queries due to their big volume. Here are tokens supported for different pages (token meaning should be clear from token name): - Videos / albums by category: %title%, %description%, %synonyms%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by tag: %tag%, %synonyms%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %first_object_title%, %first_object_description% - Videos / albums by model: %title%, %description%, %alias%, %country%, %city%, %height%, %weight%, %birth_date%, %age%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by content source: %title%, %description%, %total_videos%, %total_albums%, %total_photos%, %today_videos%, %today_albums%, %categories_as_string%, %group_as_string%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos by channel: %title%, %description%, %total_videos%, %today_videos%, %categories_as_string%, %custom1% - %custom10%, %first_object_title%, %first_object_description% - Videos / albums by search: %search_keyword%, %first_object_title%, %first_object_description% - Video view page: %title%, %description%, %duration%, %rating%, %rating_amount%, %video_viewed%, %username%, %release_year%, %custom1% - %custom3%, %tags_as_string%, %categories_as_string%, %models_as_string%, %content_source_as_string%, %dvd_as_string% - Album view page: %title%, %description%, %photos_amount%, %rating%, %rating_amount%, %album_viewed%, %username%, %custom1% - %custom3%, %tags_as_string%, %categories_as_string%, %models_as_string%, %content_source_as_string% URLs There are 2 places where you can configure URL patterns: In Settings -> Website Settings you can configure system patterns to the main object pages. These patterns are used in admin panel and other system functionality, so they are managed here in this special place: In Website UI -> Texts section you can configure all other URL patterns used by your theme. You can filter them by URL patterns group filter: Some URL patterns also include a token, where dynamic URLs are built (category page, tag page and etc - %DIR% on the above screenshot). If you change such patterns, you should also make sure to keep the same token there, otherwise URL patterns will be broken. Changing URL patterns is not recommended for basic users. In order for new URL patterns to work you will need to add changes to /.htaccess file and modify RewriteRules there. KVS uses mod_rewrite to manage URL mapping, which is difficult to use, but the most flexible way and provides unlimited customization capabilities. Here is small example. If you want for example to change this pattern: urls.albums = /albums/ To: urls.albums = /photos/ you also need to locate the corresponding rule(s) in /.htaccess file. Please be aware that each list page RewriteRule also has a sister rule for pagination, e.g. to make these pages work: /albums/2/ /albums/3/ /albums/4/ ... Usually these 2 sister rules are grouped together: RewriteRule ^albums/([0-9]+)/$ /albums_list.php?from=$1 [L,QSA] RewriteRule ^albums/$ /albums_list.php [L,QSA] You should change pattern in both of them to photos: RewriteRule ^photos/([0-9]+)/$ /albums_list.php?from=$1 [L,QSA] RewriteRule ^photos/$ /albums_list.php [L,QSA] Please note that end of the rule remains the same as before, you only change the first part of rewrite rule (e.g. this part /albums_list.php [L,QSA]). Again, we do not recommend to change this for basic users, URL patterns are not something that much affects anything.

This is already possible in the upcoming update. You can connect player HTML ads to advertising spots configured in Website UI section. In advertising spot you can configure multiple ads, one for desktop and another one for mobiles. You can render different HTML code here. In advertising HTML code you can use 2 element classes with specific meaning: class="kt-api-time-left" - will render the advertising time left class="kt-api-btn-skip" - will act as your "Continue to video" button I think we will come up with an educational article on advertising soon and try to demonstrate common scenarios. With the new advertising module its power is unlimited!

Due to high demand for paysites we also added support for displaying videos and albums from future updates. In list_videos / list_albums blocks we introduced mode_futures parameter, which will enable block to display only content from future period. The important thing to consider here is that such content will not be available via direct links, because the content still 'doesn't exist', but you can still show it as a list of the upcoming content. This functionality is fully compatible with relative post dates, when content is appeared differently for different members depending on their registration dates.

You can upload such videos, but KVS player doesn't support VR, so you should be using 3rd party player for playing them.

Please contact support, the version is ready but not yet announced.

We've added one more feature to the advertising module - ability to show different ads in different browsers. It looks like Google Chrome will start advertising crackdown soon, disabling popunders, floating ads and some other. It may be extremely important to use different advertising strategy for different browsers, so KVS will now allow this as well in addition to device type restriction:

Since this is a major new version it will be beta and only after some beta testing period (1-2 month usually) it will be available for public download. This is the way we always do for major updates. Any customer can request beta update by contacting support. We only make an update available after we are 100% sure it doesn't have any critical issues, since many our clients have multi-million traffic sites.

Yes, we have such plans. The engine already supports this, only need to do some GUI.

Next week.