vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.6 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=194)
-   -   Administrative and Maintenance Tools - vB Error Pages 1.0 (https://vborg.vbsupport.ru/showthread.php?t=132337)

TheFrienzNet 01-25-2007 09:27 PM

Thanks a lot, i've been looking for something like this for a while!

*Edit*

I can't seem to find any place where I can edit the error pages in AdminCP.

blogtorank 01-25-2007 11:33 PM

Thanks this works perfect!

TheFrienzNet 01-27-2007 07:51 PM

Quote:

Originally Posted by TheFrienzNet (Post 1167301)
Thanks a lot, i've been looking for something like this for a while!

*Edit*

I can't seem to find any place where I can edit the error pages in AdminCP.


Err?

da420 01-27-2007 08:06 PM

Try your style manager.

TheFrienzNet 01-31-2007 07:42 PM

Quote:

Originally Posted by da420 (Post 1168533)
Try your style manager.

Hm?

da420 01-31-2007 07:49 PM

vberrorpages_400
vberrorpages_401
vberrorpages_403
vberrorpages_404
vberrorpages_500

Those are the templates that are added with this modification. To make them look different you will need to edit those templates.

Ericsson 03-01-2007 07:53 PM

The error pages arnt showing up for me: http://www.ps3blab.com/dsadsa

What should the .htaccess file look like?

tehPARADOX 03-08-2007 05:30 AM

Quote:

Originally Posted by jgommel (Post 1166996)
I'm not sure if this will help anyone or not, but I added the following code to each .php error page in order to get my skins images/paths etc to work correctly.

FIND:
Code:

require_once('./global.php');
ADD UNDER:
Code:

// #################### HARD CODE JAVASCRIPT PATHS ########################
$headinclude = str_replace('clientscript', $vbulletin->options['bburl'] . '/clientscript', $headinclude);


This has solved the issue with missing style images when error page is outside of forum directory.

thincom2000 03-08-2007 04:06 PM

I have just made it a rule to always use full paths in my templates since I first had an error like this, and so far no problems (except when a hack uses str_replace() on top of my pre-empt).

Also, with specific regards to this hack, I noticed that when using these error pages, the error is not sent to my server's error logs, while if using the default error pages, they are.

SaN-DeeP 03-10-2007 12:13 AM

does this modification calls error pages for deleted threads as well ??


All times are GMT. The time now is 02:56 AM.

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.02695 seconds
  • Memory Usage 1,735KB
  • 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
  • (3)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