vb.org Archive - Search not working after upgrade to vBulletin 4.2.2 Patch Level 4

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)

- - Search not working after upgrade to vBulletin 4.2.2 Patch Level 4 (https://vborg.vbsupport.ru/showthread.php?t=317108)

Quote:

Originally Posted by MrEyes (Post 2536780)

3) Search on my site is working, no idea why. It started to work after a server reboot which I was doing for entirely different issues.

Awesome! That is odd though, but very good!

Quote:

Originally Posted by edgeless (Post 2536876)

The description by a number of your colleagues for the function of the SKIP_DS_ERRORS code string, including that from certain vB developers, has been that it "turns off the extra error reporting in php 5.3 & 5.4 (for strict & deprecated warnings)". The frequent use of this description -or others like it- demonstrates a common interchangeability of the two terms during discussion of said code string's function and purpose. Since even developers refer to the purpose of said code string as it "turns off the extra error reporting", I'm inclined to consider my reference to "hiding errors" as a completely appropriate statement. But even in view of this, I initially intended to type the word "warnings" instead of "errors"... I really did! And that's precisely why I used the term "warnings" instead of "errors" in my following reply. I think the mere fact that those two terms are interchanged on a frequent basis, even by software developers, tends to inspire some inadvertent interchangeability from many of us on occasion. And by the way, I've noticed that some developers even refer to said warnings as "less important errors". So in my opinion your focus on my semantical tendencies in order to try and belittle my qualification to comment has been uncalled for (at best).

As for the blanket file replacement troubleshooting measure, you've made your point. It makes sense and I agree with the reasons involved. Hence, I apologize for voicing my impulsive thought concerning the many times this step is suggested by vBulletin support folks. After all, as I've said, and as you've elaborated upon, it's not practical or time/cost efficient to identify corrupt files or code sections within a system when a direct blanket replacement of files is often able to solve the problems.

To clarify: nobody's belittling anyone.

However, whenever people say "vBulletin is rubbish because it hides errors rather than fixes them" - which is what started to get implied in this thread, as it does in many others -that inaccuracy needs to be corrected, or at the very least, the true facts explained. many do not have the required knowledge to understand what is actually happening, they simply read "vBulletin hides errors rather than fixes them" and assume that to be factual. That perception needs to be corrected.

Some people make the statement because they genuinely think that's what happens - it is right that they should be corrected.
Others make the statement because they have a certain agenda - again it is right that they should be corrected.

I too get frustrated at the apparent interchangeability of the term "errors". When developers do it it's even more annoying. And as I already mentioned, vBulletin themselves compounded the issue by using "SKIP_DS_ERRORS" so I can fully understand why some people jump to the conclusion that we are "hiding errors rather than fixing them".

I also understand that, to an ordinary person using the software, an ugly line of text appearing on the page with the word "WARNING" at the front is, as far they are concerned, an error....you would say "I'm getting an error message on screen" not "I am getting a warning message on screen" if describing the problem.

What does frustrate me is when people such as Paul, who are actual php programmers, state what is really happening (and we as the support team often do also), and people argue and complain still (I'm not suggesting you do this by the way).

Quote:

Originally Posted by Mark.B (Post 2536961)

To clarify: nobody's belittling anyone.

Ah, but you were. It was your first line of response to me.

Quote:

Originally Posted by Mark.B (Post 2536961)

However, whenever people say "vBulletin is rubbish because it hides errors rather than fixes them" - which is what started to get implied in this thread, as it does in many others -that inaccuracy needs to be corrected, or at the very least, the true facts explained. many do not have the required knowledge to understand what is actually happening, they simply read "vBulletin hides errors rather than fixes them" and assume that to be factual. That perception needs to be corrected.

But the way you go about correcting that perception indeed matters! Your persistent response to my initial use of the terms "errors" and "hiding them" was to assert that I simply don't understand what the SKIP_DS_ERRORS code directive actually does. And then in my subsequent reply when I termed what's being disabled by said code directive as "warnings", you condescendingly went on to imply that my interchanging of the terms confirms my failure to understand what the directive is in fact doing. I think that's quite a leap of an assumption on your part.

So the impression I've taken from your replies in this thread is why I've pointed out that certain vB developers themselves are inclined to characterize the role of the SKIP_DS_ERRORS code line as that of turning off the extra "error reporting". And by the way, fyi, I do understand that non-fatal run-time warnings don't halt the execution of associated functions, and that fatal run-time errors are unrecoverable (i.e., they result in termination of associated functions). It's not a very difficult concept to grasp in my opinion.

Lastly, I think you should be mindful that if I thought vB was "rubbish" I wouldn't likely be using it as a community platform. I hope that's at least some food for thought.

Quote:

Originally Posted by Lynne (Post 2536886)

Awesome! That is odd though, but very good!

Indeed, very odd - thanks for noticing ;)

As for Mark and Edge, thanks but read point #2 in the post above ;)

Did anyone ever figure out how to get the 'new posts' search to work? Topic got a bit derailed.......
My 'new posts' isn't working and I urgently need a FIX
no response at vB.com forums either.

This is what I have and it works

Code:

search.php?{session.sessionurl}do=getnew&contenttype=vBForum_Post

Thanks, where do I put that?

Well, you could just try typing in that url (with your forum root at the beginning) without the session stuff, like:

Code:

www.mydomain.com/forum/search.php?do=getnew&contenttype=vBForum_Post

and see if that works. It should be the same as clicking the "new posts" link though.

Quote:

Originally Posted by Eq4bits (Post 2549015)

Thanks, where do I put that?

Sorry I thought you knew go to admincp/settings/Navigation Manager edit new posts tab and put it into Target URL do make sure you put it into the correct one as there are more than one if you click forum in the Navigation Manager you will see more so make sure you pick the right one

n/m i found it in Navigation... it's what was already in there...
any other ideas?
Bueller? Bueller?

X vBulletin 3.8.12 by vBS Debug Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (2)bbcode_code_printable (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
Messages:

Phrase Groups Available:

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01383 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 (2)bbcode_code_printable (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
Messages: