Jump to content

Tech Support

Administrators
  • Posts

    1,786
  • Joined

  • Days Won

    333

Everything posted by Tech Support

  1. 1) Content sources are categorization objects in Categorization -> Content sources section. Some sites refer to sites where the video comes from. So some grabbers can pick this info if you need it. 2) It depends on your grabber settings when you choose how to treat video files from grabber. 3) Cutting few seconds actually means "conversion".
  2. You should understand regex syntax to do this, there cannot be any automation.
  3. It doesn't matter. Historically KVS demo website had 360p format as the smallest one, because it was set up 10 years ago. Now 360p format is way too small, so by default new KVS installations do not have it. The filenames of video files doesn't affect indexing.
  4. The discussion above contains all the info.
  5. The feature is not for the nearest version for sure, then we will see. I'm not sure how you think it will be faster to edit this in other way, because you still have to manually specify data for each object. Even with import or bulk edit you have to manually prepare each thumb for example.
  6. Sorry, there is no way to do that at the moment via KVS admin panel. We are close to adding these features with our nextgen development, it will be possible to import / export / mass edit all the categorization.
  7. Title is not part of URL, directory is. You just need to change directory of the video and this will result in URL changing.
  8. No, you don't need to change view_video.php part, you only need to change the first part right after RewriteRule.
  9. You also need to change RewriteRule in .htaccess file. You need to find the rewrite rules that are used for /video pages, e.g. these: RewriteRule ^video/([0-9]+)/([^/]+)/$ view_video.php?id=$1&dir=$2 [L,QSA] RewriteRule ^video/([^/]+)/$ view_video.php?dir=$1 [L,QSA] The first rule is for the case when you pass video ID AND video directory. The 2nd rule is for the case when you pass video directory only. So you need to change video part in them to your xxx part.
  10. No, KVS player can only play MP4 files. TS files are not playable in browser as they typically use MPEG2 video encoder, which is not supported by browsers.
  11. This looks like misconfiguration in Website UI -> Theme settings. You need to make sure you have some existing video files exposed in sitemap:
  12. We are doing finalization for the fixes and some new features, should probably release 6.2.1 soon. It is not possible to run migration in a separate process.
  13. No, due to technical restrictions in KVS code it is still using JPG file extension for WebP images, but this doesn't matter in any way.
  14. It looks like you web server is using some predefined HTML file for showing 404 errors, like the one you attached in screenshot. You need to edit this file, it is displayed for all 404 pages.
  15. The best way to do this is to find where this error page can be edited in litespeed and added the following code under its head: <script> window.location = '/'; </script> This will continue to serve 404 error to bots, while browser users will be redirected to index page.
  16. No, unfortunately we don't have resources and time for that. We are only working with KVS improvements.
  17. Nginx is not required, and can be replaced with Litespeed. The only question is content protection IF you store content locally. If you store content on CDN, protection is done by CDN, so Nginx is not needed. As for Memcached, it doesn't make significant difference for KVS. KVS uses 2 level caching system, and Memcached really matters for huge traffic sites. Also it is never a problem to install Memcached if needed. Redis is not supported by KVS.
  18. Try to remove GA. When Google is testing on mobile, it uses slow 4G emulation and GA matters a lot.
  19. This looks to be normal, we also have this and video is indexed with this:
  20. This is most likely due to using Google Analytics and advertising from 3rd-parties. kvs-demo.com video pages have 85 on mobile:
  21. We don't have any dates, we are still testing PHP8 in new installations, this brought many issues and still coming.
×
×
  • Create New...