Some quirkiness: Forum Display issues in certain areas

[cliff p.]

I've been working on this issue for some time now, and I'm completely confused at this point...

1. Global hooks disabled in config.php.
2. Uninstalled/disabled all 3.8.x mods on test site before upgrade to 4.2
3. Followed all upgrade guidelines to the letter.
4. Debug mode is now enabled in config.php
5. Default style created with no changes to display.

Problem: See attached. Issue is that "post new thread" text does not display in certain forums (those with restricted access to staff/admin). Attempted to determine if permissions is an issue by resetting those forums to default permissions, and no change. Noticed that they also don't show in the forum classifieds sections either.

Also, the footer section of the forumdisplay is all borked up.

Any advice is appreciated. I'd really like to get this sorted out.

[kh99]

Hmm...maybe it's a language problem? Do you have another language or any translations for any of that text?

Also, you might check for javascript errors on those pages (seems like a long shot though).

[cliff p.]

Originally Posted by kh99

Hmm...maybe it's a language problem? Do you have another language or any translations for any of that text?

Also, you might check for javascript errors on those pages (seems like a long shot though).

I rebuilt the languages just in case (never had any language other than the default English language installed), with no change.

I looked using Chrome and FF both for JS errors, and nothing was flagged.

I'm wondering if I should re-download the 4.2 PL3 suite again...

[kh99]

That couldn't hurt (if you haven't modified any vb files).

Have you looked at the html source of a page to see if you see anything unusual?

[cliff p.]

Update: I looked at the debug output again at the footer, and I have 26 queries just on that page, and some are reported as errors (red bold text I assume?).

Funny thing, since all of those particular templates or files are not modified...

FORUMDISPLAY (1)
ad_footer_end (1)
ad_footer_start (1)
ad_forum_below_threadlist (1)
ad_global_above_footer (1)
ad_global_below_navbar (1)
ad_global_header1 (1)
ad_global_header2 (1)
ad_navbar_below (1)
footer (1)
forumdisplay_sortarrow (1)
forumrules (1)
gobutton (1)
header (1)
headinclude (1)
headinclude_bottom (24)
memberaction_dropdown (1)
navbar (3)
navbar_link (1)
navbar_tabs (3)
option (1)
pagenav (1)
pagenav_curpage (4)
pagenav_pagelink (1)
pagenav_pagelinkrel (1)
spacer_close (1)
spacer_open (1)
threadadmin_imod_menu_thread (24)
threadbit (2)

--------------- Added [DATE]1354577619[/DATE] at [TIME]1354577619[/TIME] ---------------

The only thing unusual that actually gets flagged, has to do with the cronimage function. Just says the following:

[IMG]Resource interpreted as Image but transferred with MIME type text/html: "http://sitename.com/etc.etc."[/IMG]

[kh99]

I think red on that display means the template wasn't cached, so that it has to do an extra database query to get it. But that in itself is strange because by default I don't think there should be any uncached templates.

[cliff p.]

Thanks for your replies. What I ended up doing probably wasn't the best solution:

1. Deleted all files from server.
2. Re-uploaded VB4 PL2
3. Confirmed config.php configured correctly; re-uploaded PL3


Once I did the above steps, I logged in to the admin cp to confirm the software could still talk with the database, and then browsed the forum in the locations that were not working before. Everything now seems to be working fine. Still not sure what exactly caused it. I'm betting there were some files that may have had some edits from the 3.8.x software that got transferred during the migration for update, and they didn't actually get touched by the upgrade.

Regardless, it's working again so I can start implementing the software modifications

--------------- Added [DATE]1354582552[/DATE] at [TIME]1354582552[/TIME] ---------------

I've found the culprit. VBSEO 3.6 causes the issue. Not sure why but that's the problem.

--------------- Added [DATE]1354584683[/DATE] at [TIME]1354584683[/TIME] ---------------

More specifically:

.htaccess file caused the error.