Recent posts
#81
pe dark mode inca se vede "albul" de la pagina normala gen cand dai sa intri intr-un video sa zicem ca se incarca pagina mai greu apare cu alb (se vede urat daca pagina e dark)
https://i.ibb.co/bFcM2MD/Untitled.png
la fel si la prima pagina
https://i.ibb.co/bFcM2MD/Untitled.png
la fel si la prima pagina
#82
You can post here on the forums, everything is solved here.
#83
Hey Marius,i have problems with latest version,how i can contact you please?
#84
Introducing a first try at a Dark Mode for PHPVibe.
You cannot view this attachment.
Please contribute any issues and inconveniences.
You cannot view this attachment.
Please contribute any issues and inconveniences.
#85
Change the database's default engine to InnoDB
Use Maria Db, Mysql is too old. I've never seen that error. I'll have a few trial installs see if I can reproduce it.
Use Maria Db, Mysql is too old. I've never seen that error. I'll have a few trial installs see if I can reproduce it.
#86
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
#87
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..
#88
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^^ #89
#90
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.