Jump to content

KVS 5.0 implementation (was 4.1)


Tech Support
 Share

Recommended Posts

  • Replies 106
  • Created
  • Last Reply

Top Posters In This Topic

  • 3 weeks later...

We refactored the way how video / album time-based limitations work (e.g. watch max N videos for M hours). Previously they were based on cookies for performance reasons and so they were not working accurate due to that. Users could clean cookies and reset their limits.

 

Since we got a lot of complaints for this functionality, it was finally switched to IP uniqueness and it will now work more accurately, but will also affect database performance that may be quite noticeable for high traffic sites. However this will only affect sites that enabled this functionality in video_view / album_view blocks:

 

content_access_time_limit.thumb.png.9cac1f1b5334ad6f0c04ec7aeb3a0620.png

 

Also we added partial support for IPv6 and now such IPs will be rendered correctly in KVS. A 'partial' support means that we won't store full 128bit IPs, instead we will store only the last 64bit part, which is expected to indicate user's device. Using this approach will not affect KVS storage system and will not introduce any performance impact.

Link to comment
Share on other sites

  • 2 weeks later...

 

You better integrate some solutions that allows CC and paypal payments, there is should be something new i mean without bureaucracy with business verification and crazy censorship. Unfortunately CryptoCurrencies still not popular a lot

 

Paypal and Credit Card payments are already integrated long ago into KVS.

Link to comment
Share on other sites

  • 1 month later...

Since we did not post much on this topic, here is a short summary of what we are doing. We continue our global refactoring effort to enable PHP7 support. This is a huge implementation and testing task and thus it is moving slowly and we don't have any GUI enhancements for the showroom. As we need to re-test almost every KVS functionality, we are also putting some enhancements in areas that were never touched before:

 

- We changed the way how passwords are stored in KVS for the enhanced security of passwords.

- We continue working with blocks: grouping their parameters, updating their docs and default templates. 50% of the blocks are finished already.

- We are changing various lists in admin panel and adding column selectors for them. This was partly done in previous updates, but still many lists miss this functionality.

- We are planning to enhance stats display, add more columns with additional data and some basic analysis.

- We are also planning to completely change payment processors to new code architecture, which is quite dangerous in terms of regression bugs, but will be a great step forward for future payment enhancements and new features.

- We will probably look into related videos performance and add support for additional cache level for them, which will be useful for projects with huge content databases.

 

Nevertheless, our primary and top priority at the moment is PHP7 compliance.

Link to comment
Share on other sites

  • 4 weeks later...
Since we did not post much on this topic, here is a short summary of what we are doing. We continue our global refactoring effort to enable PHP7 support. This is a huge implementation and testing task and thus it is moving slowly and we don't have any GUI enhancements for the showroom. As we need to re-test almost every KVS functionality, we are also putting some enhancements in areas that were never touched before:

 

- We changed the way how passwords are stored in KVS for the enhanced security of passwords.

- We continue working with blocks: grouping their parameters, updating their docs and default templates. 50% of the blocks are finished already.

- We are changing various lists in admin panel and adding column selectors for them. This was partly done in previous updates, but still many lists miss this functionality.

- We are planning to enhance stats display, add more columns with additional data and some basic analysis.

- We are also planning to completely change payment processors to new code architecture, which is quite dangerous in terms of regression bugs, but will be a great step forward for future payment enhancements and new features.

- We will probably look into related videos performance and add support for additional cache level for them, which will be useful for projects with huge content databases.

 

Nevertheless, our primary and top priority at the moment is PHP7 compliance.

 

Hi,

 

You think able to release PHP 7 compatible on the next update?

 

Thanks

Link to comment
Share on other sites

  • 4 weeks later...

One of the new features we added into 4.1.0 is ability to fully control which tags are being created by KVS. Tags are dynamic objects that could be created without any limitations. Now this can be configured and you can define some rules that will affect which tags are allowed and which are not. It will even be possible to completely disallow creating new tags by site users, import, grabbers and other content creation methods that can automatically create tags.

 

You can see all details on this settings image:

 

tag_settings.thumb.png.37fa26c4b6567c282c941a3e88e11db4.png

 

Also we extended synonyms validation, so that it is not possible to create synonyms that duplicate existing tags or synonyms of other tags.

 

And finally tag synonyms will now be considered when adding new tags, so that instead adding a new tag KVS will select an existing tag with such synonym. Previously tag synonyms were only used by tags auto-selection plugin.

Link to comment
Share on other sites

There is an issue with KVS player and one of the recent iOS updates. In some cases (not 100% reproducible) it may result in wrong fullscreen behavior that will not allow to return from fullscreen back to normal. This was detected on iPad devices.

 

We presumably fixed this issue in 4.1.0, but since this version is not yet finalized, you may want to get a hotfix.

In order to hotfix your player you must be on 4.0.3 or 4.0.4 version and you should update this file from kvs-demo.com website:

https://kvs-demo.com/player/kt_player.js

 

Please make sure to create a local backup of this file for any unexpected issue.

 

WARNING! This fix was not yet tested on production sites and thus may result in other unexpected issues, please be sure to monitor your stats to see if anything goes wrong. This fix will only be available as part of the future 4.1.0 update.

Link to comment
Share on other sites

  • 2 weeks later...

There are several plugins in KVS that work in schedule, such as Template Cache Cleanup, Backup and Avatars Generation.

If there are many KVS projects installed on the same server, these plugins may be executed at the same time and may result in server overload.

 

Now it will be possible to configure time of day for every of such plugins to avoid them all being executed at the same time:

 

cron_plugin_scheduler.thumb.png.00c0f856384fe782159207f0bdb289f7.png

Link to comment
Share on other sites

A set of grid enhancements in admin panel was finalized last week. Here are key enhancements.

 

1) In videos and albums we finally migrated column chooser from personal settings into their grids to comply with other grids:

 

grid_videos.thumb.png.5e7d8b0384c4efa6560d249d15d8cf51.png

 

2) Also all column choosers will now allow reordering columns by drag and drop operation, so that you can configure the most convenient table view:

 

grid_dnd.thumb.png.494971323d212612aaff010c889619c9.png

 

3) In all grids it is now possible to enable thumb and file columns (where available). File columns will either show inline preview when clicked, or trigger file download for non images:

 

grid_thumb_and_files.thumb.png.95ac91b2edfdf02c9dc0407882d6cd92.png

 

4) Categorization editors will support Save & edit next button similar to videos and albums:

 

editor_buttons.png.05f84fae2a9a6c21d020a2e60075c853.png

5) Performance of all grids has been revised and now they will produce less SQL queries, as well as performance of queries themselves was adopted to work better for big databases. For example, KVS will now change query style based on which grid columns are enabled and thus will not query data that is not needed to be displayed and may affect query performance.

Link to comment
Share on other sites

Some enhancements and fixes were done in stop words functionality configured in Website Settings.

 

First of all, we fixed 3 bugs with it:

 

1) Case insensitive match was not working for non-latin symbols and not using star symbol.

2) When a stop word was specified without star symbol, it was replaced even if it was part of other words. The new behavior is that if you want partial match, you must use star symbol. So fuck will only replace words spelled as "fuck", but won't replace inside "fucking", "fucked" and etc. If you want those to be replaced as well, you must add star, e.g. fuck* in stop words list.

3) If 2 or more words are replaced in a row, there will not be multiple [censored] repeated.

 

Also we added support for custom regular expression rules. This will allow much more control on what users can post, for example you can cut URLs to prevent spam in comments.

 

autoreplace_rules.thumb.png.f16dfa86429d9d3bfe1b022bca10dd7d.png

Link to comment
Share on other sites

  • 2 weeks later...

All payment processors were changed to the new API. This will allow us to add more paysite features in the future, such as shopping cart and additional payments.

Also we enabled support for trials in all payment processors where possible:

 

payment_processors_features.png.ea5498c7793df0832c47af500c724d18.png

 

In addition to that, we added support to configure token awards for referred registrations, so that your members can refer other members to join your site and thus earn tokens, that can further be paid out or spent on premium content access. This can be configured in Settings -> Memberzone settings among other awards:

 

memberzone_awards_referral.png.e864e0b98b1518e4213a41798c8b7176.png

 

Similar referral commissions were also added into access codes. When creating new access codes, you will be able to specify token award that will be received by referring other users that will use access codes of this type. For example if you are using access codes to sell access to your site, you can also allow your users earn tokens from referring other users to your site. In comparison to free signup awards, this award will only be counted if the referred user uses one of these access codes:

 

access_code_referral.png.59a71f38feb1a9cf0e53a13ada278964.png

Link to comment
Share on other sites

  • 3 weeks later...

Can the Geo-Blocking area lock this feature be added? Posting video users can choose to play videos that are not in those areas. In addition, the background can add a setting scheme that sets the resolution above 2k for paying viewing, and the normal definition is free to watch.

Link to comment
Share on other sites

GEO blocking is not yet possible, it will break caching logic and thus not easy to implement.

 

Configuring which video qualities are allowed for which users (e.g. 2k quality is allowed for premium) is standard settings task.

 

Go to Settings -> Video formats and configure premium access level for 2k video format.

Go to Settings -> Player settings and configure Video formats display -> Redirect URL to point to your page where you explain that 2k quality is only available for Premium members. Then:

a) If video is accessed by premium member - selecting 2k format in player will play the file

b) If video is accessed by standard member or guest - selecting 2k format in player will redirect them to your Redirect URL.

 

Documentation: Setting Up Video Access

https://www.kernel-scripts.com/en/documentation/kvs_quick_start/#section_memberzone_video

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • Create New...