Tweet
Anyway, so when will vb5 work with PhP 7? By not working with the current PhP 7 this means effectively it is not PhP 7 compatible.
-
-
We started working on these issues when they were reported. We'll resolve them as soon as possible. If you have a specific issue with a version of PHP, the best way to get them resolved is to post the issue in JIRA and we will fix them as quickly as possible. Posts like this are not helpful in any way.Translations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 APIComment
-
I voted for this:
I believe that is the issue. It shows as MAJOR but unassigned as of yet....Comment
-
It is being looked at. I do not know how long it will take to fix, nor which version the fix will go into.I voted for this:
I believe that is the issue. It shows as MAJOR but unassigned as of yet....
Constantly pushing us on it will make no difference. The support team are not involved in development. As I mentioned earlier though, it can't just be "instantly fixed". There isn't a button to press that says "fix this issue". The developers need to investigate the cause of the issue, work out possible fixes, and establish what impact those fixes might have on other areas of the code. These then need to be extensively tested, on multiple platforms, to ensure they don't break anything else. It's not a fast process.
If you watch the bug report the latest information will always be there.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
This issue should be resolved in the final release of 5.2.3, which is imminent, barring any last minute disasters.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
great news
i just had this same issue the last few days without noticing this topic until now...
in my case it is a cpanel server which a famous slow adopter for upgrades...with this approach it is generally a good balance for security and function, so i was pretty upset to have my site break and fighting with host for days....5.2.3 tho...aces nice work thanks you
Comment
-
I got told it would be in 5.2.3, but it looks like something prevented that from happening at the last minute. It will now be in 5.2.4.
The workaround for now is to run php 7.0.7.MARK.B
vBulletin Support
------------
My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
My Unofficial vBulletin Cloud Demo: https://www.adminammo.comComment
-
ok, its good to see the effort was made anyway...seems problematic reverting to 7.0.7 tho...i fought with my host about it for a couple days, then i saw some others tried that route and failed....sigh, idk...probly gonna be easiest to just wait 2 months unless there is a method to ensure a safe downgrade? even after 2 days with host i dont understand what the big difficulty is in matching the configurations or whatever the big issue on that idk..
-
-
Please try the attached patch file.Translations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 APIComment
-
Comment
-
What does this patch do? Does it make any alterations in the php.ini file because I had a code in there to max_input_vars=10000 and now that code has disappeared and even when I put it back in, the max_input_vars remains at 1000. I would like to revert absolutely whatever this patch has done. -
The patch makes changes to the following files:
core/vb/request.php
core/vb/ip.php
core/vb/session/webapi.php
core/vb/session/api.php
core/vb/session/web.php
You can open up the patch file in a text editor to see what it changes. It doesn't touch the php.ini file. -
I followed all instructions seemed to do the job on my test forum, so I repeated on my actual site as follows:
(upload the patch to forums directory)
1. login via terminal SSH to server
2. cd public_html/forums
3. patch -p0 -i VBV-16318.patch
4. Got this:
(Stripping trailing CRs from patch.)
patching file core/vb/request.php
(Stripping trailing CRs from patch.)
patching file core/vb/ip.php
(Stripping trailing CRs from patch.)
patching file core/vb/session/webapi.php
(Stripping trailing CRs from patch.)
patching file core/vb/session/api.php
(Stripping trailing CRs from patch.)
patching file core/vb/session/web.php
5. I forced to PhP 7.0.9
No more error upon regular logins to forums now. All seems well! EXCEPT - note my post below - that Facebook login / integration appears to be no longer working after running this patch.
Thanks for help and guidance.
P.S. The max_input_vars reverting to 1000 instead of 10000 was a different issue which is resolved now.Last edited by Maltair; Fri 5 Aug '16, 12:30pm.
-
-
just to confirm another, i just now got to doing this and the patch worked great on my server as well...its a nice relief seriously thank you..Comment
-
After running the VBV-16318.patch, there is one possible issue though - can't seem to login with Facebook. This may be a recurrence of this bug:
http://www.vbulletin.com/forum/forum...working-lately
or it may have something to do with this patch.
The Facebook LIKE has disappeared from the forum pages.
Because I also just tested and even trying to Register via Facebook is no longer working - try to register and click f Connect with Facebook and nothing happens, you just land on the site home page.
Anyone else - after running this patch is Facebook login and integration still working for you?
I suspect that this patch somehow eliminates Facebook integration / login.
Comment
-
This should be posted in the JIRA so it can be reviewed and tested. The patch is an untested workaround for PHP 7.0.9 and higher only at this time.
Translations provided by Google.
Wayne Luke
The Rabid Badger - a vBulletin Cloud demonstration site.
vBulletin 5 APIComment
-
I posted in the JIRA.
I REVERTED THE PATCH, WENT BACK TO PHP 5.6.24 AND FACEBOOK INTEGRATION/LOGIN WAS RESTORED. So this VBV-16318.patch does not seem to be a complete solution.Comment
-
What is this error?
Invalid SQL:
SELECT `varname`,`languageid`,`text` FROM phrase
WHERE `varname` IN ('Description cannot be empty. Please set this field.','go_back','my_profile','my_recent_posts','user_settings','log_out','logo','search' ,'filter_search','navbar_home','navbar_blogs','navbar_articles','navbar_social_groups','na vbar_158516011593_15751604158916081585','navbar_15751604157816081575160216101593','navbar_ 15781586161016101606_15751604160516081575159016101593','navbar_newtopics','navbar_todays_p osts','navbar_whos_online','navbar_mark_channels_read','navbar_member_list','search_in_tit les_only','advanced_search','notice_23_html','navbar_help','navbar_contact_us','go_to_top' ,'powered_by_vbulletin','footer_current_time','working_ellipsis','yes','no','ok','cancel')... -
[20-Oct-2017 00:42:08 Europe/Minsk] PHP Warning: Illegal string offset 'starter' in public_html/includes/vb5/template.php(318) : eval()'d code on line 167
[20-Oct-2017 00:42:08 Europe/Minsk] PHP... -
hi,
when viewing some members blog, get this error
[16-Apr-2017 10:10:15 Asia/Riyadh] Warning: Illegal string offset 'moderatorperms' in /home/usre/public_html/vb/includes/vb5/template.php(318)... -
Forum version: vBulletin 5.3.0 Connect
PHP version: 5.6- The forum was working absolutely fine till last night (IST). Now after 8 hours I visited the forum and got a couple of warnings right up
-
Randomly getting the following SQL error. Different users. I'm having difficulty determining "what" is wrong. I believe it is indicating a thumbnail image is the cause, but if so, I can't determine...
Comment