I just upgraded a clients site to vb 4 and we're upgrading the vb3 style with vbulletin's built in upgrade tool. I went to go change out the logo and I get the Declaration errors mentioned a year ago in the OP... The advice is to hide PHP errors?
It seems it would be better for the company to fix the problem, not hide it.. :down:
actually it seems when I edit any stylevar.. well this will be an annoying job.. I'm sure the client will be asking me what the hell is wrong with vb4 when they see them too.. Thanks vBulletin
Regardless of your predictable rant, if you want to fix it, use the advice given.
You should however use SKIP_DS_ERRORS rather than SKIP_ALL_ERRORS, that restores the warning reporting to the same as used by vb2, vb3 and vb4 versions other than 4.2.2.
I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.
Suppressing errors (hiding, covering up problems) is about the worst thing you can do as a developer. If customers find out you're doing that then they will never trust you again. This type of approach shows a complete lack of desire or ability to fix the underlying problems.
Would you want your plumber or auto mechanic to hide problems from you? Of courses not.
Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
Reply With Quote
Well then there is not much web based software you would purchase then, as it has been a common practice for ever. If it was so bad, then the blame should fall on the people who created PHP, as they made it so the warnings could be suppressed.
Well then there is not much web based software you would purchase then, as it has been a common practice for ever. If it was so bad, then the blame should fall on the people who created PHP, as they made it so the warnings could be suppressed.
Most software development environments have the ability to suppress error messages. They also provide the ability to write completely illogical spaghetti code too but that doesn't mean it's good practice to use either option.
I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.
Suppressing errors (hiding, covering up problems) is about the worst thing you can do as a developer. If customers find out you're doing that then they will never trust you again. This type of approach shows a complete lack of desire or ability to fix the underlying problems.
Would you want your plumber or auto mechanic to hide problems from you? Of courses not.
Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
I do not believe that anyone was promoting masking constructional errors. The discussion (as I interpreted) was about interpretive/compiler warnings. Maybe I just misread.
I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.
Suppressing errors (hiding, covering up problems) is about the worst thing you can do as a developer. If customers find out you're doing that then they will never trust you again. This type of approach shows a complete lack of desire or ability to fix the underlying problems.
Would you want your plumber or auto mechanic to hide problems from you? Of courses not.
Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
Well it was common knowledge when vBulletin 3 was released. Nobody seemed to mind then.
I run my own software business and have over 30 years experience developing software. I develop systems for telecoms, railroads and manufacturers and I can tell you that if I started suppressing errors instead of addressing and correcting them I would be out of business tomorrow.
Suppressing errors (hiding, covering up problems) is about the worst thing you can do as a developer. If customers find out you're doing that then they will never trust you again. This type of approach shows a complete lack of desire or ability to fix the underlying problems.
Would you want your plumber or auto mechanic to hide problems from you? Of courses not.
Ask yourself this: When you were first thinking about purchasing vBulletin and you found out that error messages were being suppressed would you still be willing to purchase it?
I totally agree with what you have said this is why I put a link in my sig so any can find the fixes for the problems in 4.2.2
09-03-2014, 12:06 AM
Linear Mode
