Discussion in 'vBulletin' started by Paul M, Jun 30, 2017.
and PHP 7.2 ? PHP 7.2 beta1 is coming next week
vB3 and VB4 dont like PHP 7.2 much.
That said, I dont think any of the errors are fatal, so if you completely suppressed error reporting, you might get away with it.
Complete suppression is the IB Way.
Ok ..... What is that even supposed to mean ?
Error supression was built into vB3 by Jelsoft, and replicated into vB4 (its probably in vB2 as well).
Suppression of dissent on the forums.
Suppression of former employees with the XenForo lolsuit.
C'mon you're not that thick.
The discussion was about php 7.2 and errors.
If you have something useful to add, please do, but pointless digs about IB are not welcome.
I meant IB has a habit of suppressing their own errors in terms of the decisions they have made with the vBulletin product.
No one has ever publicly admitted to making poor decisions and no one has been made to pay for said poor decisions.
The vB.org decision is just another poor one in a long line of poor ones.
In any reputable company Robert Briscoe would have been out the door after the vB4 "Gold" fiasco.
But not only did he receive a free pass on vB4, a product salvaged largely by the likes of yourself and others, he has also received a free pass on vB5.
If vBulletin.org is the end of an era then vBulletin.com will be defined as the end of an error.
Considering I've been exclusively a vBulletin customer since 2000 and have openly defended the vB5 product this is not pointless bashing.
It is a customer wishing someone higher up than customer support and the developers cared about the future of the product.
Some people get it.
I see the IB Censors have now stepped in ;
Spotted that - I saw a lot of the posts that were eventually deleted. Some interesting comments.
I'm surprised they left mine. I did try to word it very carefully.
It appears your subsequent post highlighting some out-of-date information has been logged in JIRA, marked as resolved and petitioned to be reopened. All this to amend the site 'About Us' page.
I try, I honestly try not to bitch and moan about vBulletin but but they present such an easy target it's almost impossible to resist.
Which still lists Marco as the Site Coordinator BTW, so it's not like it's only a little bit out of date. Marco's been gone what, almost 7 years? And I'm not even getting into the assertion "vBulletin.org is primarily run by volunteers who, like our member base, are vBulletin customers" - it's clear who's running vBorg now.
About a year after Internet Brands took over vBulletin, I posted this image. I was ridiculed for my sky-is-falling opinion. After all, vBulletin was the industry leader and had a spotless reputation at that point.
Since I cannot access vborg Jira anymore, I dont know what they did, but the process of using Jira for all VBO changes is standard (and one I insisted be used).
Everything is stored in svn (code & styles) and the site reloaded from svn on any updates.
So even a custom template change would be wiped out by a subsequent change and reload if its not correctly saved.
I used to use a similar system when I had forums running on vB4 to ensure continuity after an upgrade so I can see the point of it but changes to content even on custom pages was a trivial process despite being logged. This seems unnecessarily protracted.
The basic process is pretty simple ;
1. Log Jira
2. Update in SVN.
3. Deploy to Stage
4. Verify its correct.
5. Deploy to Live
6. Verify its correct
7. Close Jira.
VBC, VBO & VBG all sucessfully used that basic process (which I built) for 5 years, and no one had any complaints.
You can argue thats over complicated if you want, but when you are maintaining multiple sites and systems, its far easier to just have a standard process.
The only part that puzzles me as why the Jira was closed before the work had been done.
I blame Marco!
They only want happy-go-lucky thank you posts now. I resisted the urge to say "thank you for the fatal blow to VB's third party support site"
We use a similar process.