vb.org Archive
Page 2 of 9 1 2 34 Last »
Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Upgraded to 4.2.2 problem with stylevar (https://vborg.vbsupport.ru/showthread.php?t=303173)

ozzy47 09-01-2014 05:28 PM
Those are not errors, but warnings. They have always been suppressed it was just recently with PHP newer versions, they started showing again.

Paul M 09-03-2014 12:06 AM
Quote:
Originally Posted by Brandon Sheley (Post 2513374)
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 :mad:
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.

Disco_Stu 09-04-2014 09:27 AM
I have to throw my two cents in here:

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?

doctorsexy 09-04-2014 10:26 AM
Quote:
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
The answer to that is, no.....

ozzy47 09-04-2014 10:29 AM
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. :)

Disco_Stu 09-04-2014 04:44 PM
Quote:
Originally Posted by ozzy47 (Post 2513732)
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.

ozzy47 09-04-2014 05:24 PM
Leave my spaghetti code out of this. :p :)

tbworld 09-04-2014 05:53 PM
Quote:
Originally Posted by Disco_Stu (Post 2513729)
I have to throw my two cents in here:

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. :)

Mark.B 09-04-2014 06:26 PM
Quote:
Originally Posted by Disco_Stu (Post 2513729)
I have to throw my two cents in here:

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.

ForceHSS 09-04-2014 06:42 PM
Quote:
Originally Posted by Disco_Stu (Post 2513729)
I have to throw my two cents in here:

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


All times are GMT. The time now is 05:58 PM.
Page 2 of 9 1 2 34 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01065 seconds
  • Memory Usage 1,751KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (6)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (3)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 
Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 
Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete