Recent posts
#81
Specified key was too long; max key length is 1000 bytes
and
Incorrect table definition; there can be only one auto column and it must be defined as a key
i dont know how to fix it ^^
Im use MySQL
and
Incorrect table definition; there can be only one auto column and it must be defined as a key
i dont know how to fix it ^^
Im use MySQL
#82
It shows me these errors when installing the script then runs but do I have to adjust all the stuff then in the admin area ? or what is the easiest way to solve the problem. Maybe you have a tip would be very grateful for that.
ezSQL (v2.18) Debug..
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [39] -- [ALTER TABLE `vibe_crons` ADD PRIMARY KEY (`cron_id`), ADD KEY `cron_type_idx` (`cron_type`(333));]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [40] -- [ALTER TABLE `vibe_description` ADD PRIMARY KEY (`did`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [41] -- [ALTER TABLE `vibe_em_comments` ADD PRIMARY KEY (`id`), ADD KEY `object_id` (`object_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [42] -- [ALTER TABLE `vibe_em_likes` ADD PRIMARY KEY (`id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `sender_ip` (`sender_ip`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [43] -- [ALTER TABLE `vibe_hearts` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `uid_uni` (`uid`,`vid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [44] -- [ALTER TABLE `vibe_homepage` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [45] -- [ALTER TABLE `vibe_images` ADD PRIMARY KEY (`id`), ADD KEY `iTitleSearch` (`title`), ADD KEY `iviews_idx` (`views`), ADD KEY `idates_idx` (`date`(50)), ADD KEY `ipub_idx` (`pub`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [46] -- [ALTER TABLE `vibe_images` ADD FULLTEXT KEY `iSearchText` (`title`,`description`,`tags`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [47] -- [ALTER TABLE `vibe_images` ADD FULLTEXT KEY `iSearchTitleText` (`title`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [48] -- [ALTER TABLE `vibe_jads` ADD PRIMARY KEY (`jad_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [49] -- [ALTER TABLE `vibe_langs` ADD PRIMARY KEY (`lang_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [50] -- [ALTER TABLE `vibe_languages` ADD PRIMARY KEY (`term_id`), ADD UNIQUE KEY `lang_code` (`lang_code`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [51] -- [ALTER TABLE `vibe_likes` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `uid_uni` (`uid`,`vid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [52] -- [ALTER TABLE `vibe_noty` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [53] -- [ALTER TABLE `vibe_options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`), ADD UNIQUE KEY `option_name_uni` (`option_name`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [54] -- [ALTER TABLE `vibe_pages` ADD PRIMARY KEY (`pid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [55] -- [ALTER TABLE `vibe_playlists` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [56] -- [ALTER TABLE `vibe_playlist_data` ADD PRIMARY KEY (`id`), ADD KEY `playlist_idx` (`playlist`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [57] -- [ALTER TABLE `vibe_postcats` ADD PRIMARY KEY (`cat_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [58] -- [ALTER TABLE `vibe_posts` ADD PRIMARY KEY (`pid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [59] -- [ALTER TABLE `vibe_reports` ADD PRIMARY KEY (`r_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [60] -- [ALTER TABLE `vibe_tags` ADD PRIMARY KEY (`tagid`), ADD KEY `tag` (`tag`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [61] -- [ALTER TABLE `vibe_tag_names` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [62] -- [ALTER TABLE `vibe_tag_rel` ADD PRIMARY KEY (`tid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [63] -- [ALTER TABLE `vibe_users` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [64] -- [ALTER TABLE `vibe_users_friends` ADD PRIMARY KEY (`id`), ADD KEY `uid_idx` (`uid`), ADD KEY `fid_idx` (`fid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [65] -- [ALTER TABLE `vibe_users_groups` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [66] -- [ALTER TABLE `vibe_user_subscriptions` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [67] -- [ALTER TABLE `vibe_videos` ADD PRIMARY KEY (`id`), ADD KEY `TitleSearch` (`title`), ADD KEY `views_idx` (`views`), ADD KEY `dates_idx` (`date`(50)), ADD KEY `pub_idx` (`pub`), ADD KEY `source_idx` (`source`(300)), ADD KEY `tmp_source_idx` (`tmp_source`(300));]
Query Result..
ezSQL (v2.18) Debug..
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [39] -- [ALTER TABLE `vibe_crons` ADD PRIMARY KEY (`cron_id`), ADD KEY `cron_type_idx` (`cron_type`(333));]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [40] -- [ALTER TABLE `vibe_description` ADD PRIMARY KEY (`did`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [41] -- [ALTER TABLE `vibe_em_comments` ADD PRIMARY KEY (`id`), ADD KEY `object_id` (`object_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [42] -- [ALTER TABLE `vibe_em_likes` ADD PRIMARY KEY (`id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `sender_ip` (`sender_ip`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [43] -- [ALTER TABLE `vibe_hearts` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `uid_uni` (`uid`,`vid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [44] -- [ALTER TABLE `vibe_homepage` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [45] -- [ALTER TABLE `vibe_images` ADD PRIMARY KEY (`id`), ADD KEY `iTitleSearch` (`title`), ADD KEY `iviews_idx` (`views`), ADD KEY `idates_idx` (`date`(50)), ADD KEY `ipub_idx` (`pub`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [46] -- [ALTER TABLE `vibe_images` ADD FULLTEXT KEY `iSearchText` (`title`,`description`,`tags`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [47] -- [ALTER TABLE `vibe_images` ADD FULLTEXT KEY `iSearchTitleText` (`title`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [48] -- [ALTER TABLE `vibe_jads` ADD PRIMARY KEY (`jad_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [49] -- [ALTER TABLE `vibe_langs` ADD PRIMARY KEY (`lang_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [50] -- [ALTER TABLE `vibe_languages` ADD PRIMARY KEY (`term_id`), ADD UNIQUE KEY `lang_code` (`lang_code`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [51] -- [ALTER TABLE `vibe_likes` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `uid_uni` (`uid`,`vid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [52] -- [ALTER TABLE `vibe_noty` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [53] -- [ALTER TABLE `vibe_options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`), ADD UNIQUE KEY `option_name_uni` (`option_name`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [54] -- [ALTER TABLE `vibe_pages` ADD PRIMARY KEY (`pid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [55] -- [ALTER TABLE `vibe_playlists` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [56] -- [ALTER TABLE `vibe_playlist_data` ADD PRIMARY KEY (`id`), ADD KEY `playlist_idx` (`playlist`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [57] -- [ALTER TABLE `vibe_postcats` ADD PRIMARY KEY (`cat_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [58] -- [ALTER TABLE `vibe_posts` ADD PRIMARY KEY (`pid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [59] -- [ALTER TABLE `vibe_reports` ADD PRIMARY KEY (`r_id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [60] -- [ALTER TABLE `vibe_tags` ADD PRIMARY KEY (`tagid`), ADD KEY `tag` (`tag`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [61] -- [ALTER TABLE `vibe_tag_names` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [62] -- [ALTER TABLE `vibe_tag_rel` ADD PRIMARY KEY (`tid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [63] -- [ALTER TABLE `vibe_users` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [64] -- [ALTER TABLE `vibe_users_friends` ADD PRIMARY KEY (`id`), ADD KEY `uid_idx` (`uid`), ADD KEY `fid_idx` (`fid`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [65] -- [ALTER TABLE `vibe_users_groups` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [66] -- [ALTER TABLE `vibe_user_subscriptions` ADD PRIMARY KEY (`id`);]
Query Result..
No Results
Last Error -- [Specified key was too long; max key length is 1000 bytes]
Query [67] -- [ALTER TABLE `vibe_videos` ADD PRIMARY KEY (`id`), ADD KEY `TitleSearch` (`title`), ADD KEY `views_idx` (`views`), ADD KEY `dates_idx` (`date`(50)), ADD KEY `pub_idx` (`pub`), ADD KEY `source_idx` (`source`(300)), ADD KEY `tmp_source_idx` (`tmp_source`(300));]
Query Result..
#83
Thank you very much for the quick reply, I'll check the settings. Is absolutely new territory for me in the field of 
and thank you very much that the recaptcha function was turned off, that makes the script perfect for my use. (what I also noticed: With videos he has an enormous distance to the other videos, otherwise respect, good work you have won a customer with it <3 I'm more of a design freak if you understand what I mean^^
and thank you very much that the recaptcha function was turned off, that makes the script perfect for my use. (what I also noticed: With videos he has an enormous distance to the other videos, otherwise respect, good work you have won a customer with it <3 I'm more of a design freak if you understand what I mean^^ #84
#85
Hi! I've checked it now, and it works. Make sure the server has the settings required https://forums.phpvibe.com/how-tos/server-settings-for-large-file-uploads/
I will remove the need for recaptcha today. I'm working on the login/register pages for the new update, and I will commit them today.
I will remove the need for recaptcha today. I'm working on the login/register pages for the new update, and I will commit them today.
#86
Hey nice Script but the Upload dont work can you help me with that ?
and i dont understand how can i make the user Registration without Captcha ?
and i dont understand how can i make the user Registration without Captcha ?
#87
I've wrapped recent patches to a release with number 11.0.45 https://github.com/PHPVibe/PHPVibe-CMS/releases/tag/11.0.45
You can see a changelog here https://github.com/PHPVibe/PHPVibe-CMS/commits/master/
You can see a changelog here https://github.com/PHPVibe/PHPVibe-CMS/commits/master/
#88
Restrict video qualities for guests and non-premium users in PHPVibe
For those of you constructing an adult tube using PHPVibe, this small modification can be beneficial if you're contemplating restricting certain video qualities for specific users, akin to the practices of sites like Redtube or Pornhub.
To implement this modification in the PHPVibe CMS, open the file app/classes/class.providers.php and locate the following section:
Just before the last line (krsort($qualities)
, insert the following code:
Adjust the $garr and $usrr arrays with the values you want to exclude. $garr pertains to guests, while $usrr relates to non-premium users or regular users. The $qualities variable is global, allowing you to access it from video.php in the theme folder. This enables you to create a message that informs users about the restricted qualities, such as "Sign in to watch this in stunning 1080p," a common feature on adult tube sites.
I hope this proves helpful! Cheers.
For those of you constructing an adult tube using PHPVibe, this small modification can be beneficial if you're contemplating restricting certain video qualities for specific users, akin to the practices of sites like Redtube or Pornhub.
To implement this modification in the PHPVibe CMS, open the file app/classes/class.providers.php and locate the following section:
Code Select
/* We have multiple qualities */
$real_link = (isset($qualities["hd"])) ? $qualities["hd"] : $qualities["sd"];
$extra = $qualities;
}
krsort($qualities);
Just before the last line (krsort($qualities)
, insert the following code:Code Select
/* Restrict some */
$garr = array('1080', '720', 'hd'); /* Guest restrictions */
if (!is_user()) {
foreach ($garr as $rg) {
if (isset($qualities[$rg])) {
unset($qualities[$rg]);
}
}
}
$usrr = array('1080');/* Non-premium user restrictions */
if (!has_premium()) {
$qualities = array_diff(array_map('json_encode', $qualities), array_map('json_encode', $usrr));
$qualities = array_map('json_decode', $qualities);
}
Adjust the $garr and $usrr arrays with the values you want to exclude. $garr pertains to guests, while $usrr relates to non-premium users or regular users. The $qualities variable is global, allowing you to access it from video.php in the theme folder. This enables you to create a message that informs users about the restricted qualities, such as "Sign in to watch this in stunning 1080p," a common feature on adult tube sites.
I hope this proves helpful! Cheers.
#89
PHPVibe diverges from a custom PHP framework or an MVC model, opting instead for an easily navigable file system. The central controller, index.php, serves as the core orchestrator, encompassing subsequent files.
index.php initiates a route, a view, a PHP file situated in the /views folder, named views/{name}.route.php. This view, in turn, invokes a template file located at /themes/{current theme}/{name}.php as its display (template).
Why this approach?
It simplifies the system for easy editing, avoiding the use of a custom PHP framework or MVC model. Notably, no files are overwritten even if mixed within the same folder during coding. This avoids potential conflicts, such as having two files named video.php in different folders—one for components and another for theme output.
Here's a flow example for a single video page:
index.php
Utilizes load.php, which consolidates all libraries.
Invokes:
views/video.route.php
Calls:
themes/main/video.php
Serving as the final destination for theme output.
index.php initiates a route, a view, a PHP file situated in the /views folder, named views/{name}.route.php. This view, in turn, invokes a template file located at /themes/{current theme}/{name}.php as its display (template).
Why this approach?
It simplifies the system for easy editing, avoiding the use of a custom PHP framework or MVC model. Notably, no files are overwritten even if mixed within the same folder during coding. This avoids potential conflicts, such as having two files named video.php in different folders—one for components and another for theme output.
Here's a flow example for a single video page:
index.php
Utilizes load.php, which consolidates all libraries.
Invokes:
views/video.route.php
Calls:
themes/main/video.php
Serving as the final destination for theme output.
#90
The YouTube logo on the player
One of the most commonly searched queries by our users/webmasters interested in video sharing is "How to remove/get rid of the YouTube logo on YouTube embedded videos." However, achieving this task is challenging, often temporary, and comes with high risks. Not only do you risk limitations imposed by YouTube or being banned from the API, but you may also draw the ire of Google, potentially resulting in removal from its listings.
The typical approach involves creating a proxy file that captures and decodes the link to the YouTube video. However, this method requires constant updates and code changes whenever YouTube modifies its platform. This can be frustrating, and it's advisable to reconsider pursuing this idea.
YouTube advertising on the player
Whenever you embed a YouTube video using their iframe or a supported player, YouTube advertising will still appear on your website. While it may be annoying, content creators are positioned to earn substantial revenue through the Google network.
In such cases, the best choice is to accept and adapt to it.
PHPVibe exclusively employs safe players compliant with YouTube's policies to the fullest extent. Both video ads and the YouTube logo will persist and will not be removed from our CMS.
If you observe our clients attempting to remove these elements, kindly refrain from seeking assistance from us.
The CMS is open source, allowing each owner to customize it according to their needs.
One of the most commonly searched queries by our users/webmasters interested in video sharing is "How to remove/get rid of the YouTube logo on YouTube embedded videos." However, achieving this task is challenging, often temporary, and comes with high risks. Not only do you risk limitations imposed by YouTube or being banned from the API, but you may also draw the ire of Google, potentially resulting in removal from its listings.
The typical approach involves creating a proxy file that captures and decodes the link to the YouTube video. However, this method requires constant updates and code changes whenever YouTube modifies its platform. This can be frustrating, and it's advisable to reconsider pursuing this idea.
YouTube advertising on the player
Whenever you embed a YouTube video using their iframe or a supported player, YouTube advertising will still appear on your website. While it may be annoying, content creators are positioned to earn substantial revenue through the Google network.
In such cases, the best choice is to accept and adapt to it.
PHPVibe exclusively employs safe players compliant with YouTube's policies to the fullest extent. Both video ads and the YouTube logo will persist and will not be removed from our CMS.
If you observe our clients attempting to remove these elements, kindly refrain from seeking assistance from us.
The CMS is open source, allowing each owner to customize it according to their needs.