vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.5 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=113)
-   -   Custom HTTP Error Pages (https://vborg.vbsupport.ru/showthread.php?t=98243)

JJR512 10-13-2005 01:53 PM

Quote:

Originally Posted by KirbyDE
You are right, this edit is not necessary at all ;)

Hook template_groups
PHP Code:

$only['http_error'] = 'HTTP Errors'

Another suggestion:
Use phrases for the Text, so users can easily use it with other Languages too.

Just create a new plugin with that code as the code to that hook?

Also, regarding the templates vs. phrases issue: I originally thought to use phrases. But then I discovered you can't use variables, such as $vboptions[hometitle] in phrases. Is there a way to use variables like that in phrases? If so, I can re-write the hack. But when I put in that variable in a phrase I was testing, it just came out on the page literally, dollar sign and everything.

Andreas 10-13-2005 02:09 PM

Phrase with Variable:
Code:

Hello {1}, how are you?
Template using this Phrase:
Code:

<phrase 1="$bbuserinfo[username]">$vbphrase[hello_x_how_are_you]</phrase>
Yes, just make a plugin with this Code and the Templates will be grouped.

JJR512 10-13-2005 03:24 PM

I have updated the hack to include the new plugin provided by KirbyDE. The instructions have been updated. No vBulletin file modifications are necessary. (I copied that file mod from some other hacks that group templates the same way. Now I know it's not necessary to do it like that, and I'll probably create plugins like this for other hacks I've installed and return that file to its stock form.)

Due to the small change in method, the hack is now 2.0.1. This version does not include any phrases as KirbyDE has suggested. It will take me a short while to get all that done and tested, at which point we will probably have 2.1.0.

If you have already installed 2.0.0, and are going to upgrade to 2.0.1, simply do this: Removed the modification to your adminfunctions_template.php file, and add the product again, making sure to overwrite the existing version.

JJR512 10-13-2005 03:26 PM

Quote:

Originally Posted by KirbyDE
Phrase with Variable:
Code:

Hello {1}, how are you?
Template using this Phrase:
Code:

<phrase 1="$bbuserinfo[username]">$vbphrase[hello_x_how_are_you]</phrase>
Yes, just make a plugin with this Code and the Templates will be grouped.

Can you use {1} more than once in a phrase; for example, have the phrase be:
Code:

Hello, {1}! How are you today, {1}?
And the template would still be exactly the same as in your current example?

JJR512 10-13-2005 03:31 PM

Quote:

Originally Posted by Dark Visor
'e' should be a TYPE_UINT.

I think this is probably going just slightly beyond what I know about. How would I make this change, and why is it important? For my education and future reference.

I have another hack I may release soon that's also going to be using a variable through the URL in the same way that $e is used here. However, in this other hack, the value of the variable, $p, will be some text, like file.php?p=something. What should I define that as and how?

JJR512 10-13-2005 03:33 PM

Wait, I think I answered my own question...

In the httperror.php file, the line
Code:

        'e'        => TYPE_STR
should be
Code:

        'e'        => TYPE_UINT
Is that correct?

(But in the other hack I mentioned, where $p is some text, leave it set to TYPE_STR, right?)

Snake 10-13-2005 06:11 PM

Great, thanks for the hack.

akanevsky 10-13-2005 06:21 PM

Yes, that is correct.
You might want to read my tutorial, it describes what are the clean variable types in vBulletin. :)

Basically, since you are passing an integer through the "e" variable, you should force the integer type on it, but it's just for security's sake :)

JJR512 10-13-2005 07:27 PM

Updated to 2.0.2 based on code change suggested by Dark Visor.

If you have 2.0.1, make the change as described in post# 16 above and upload the modified httperror.php file.

If you have 2.0.0, basically do what is in post# 13 above (undo the modification to adminfunctions_template.php, then re-add the product, overwriting the existing version), PLUS upload the new httperror.php file.

Avalon111 10-14-2005 05:09 AM

i have noticed that members who are not viewing a error page are listed as viewing error page in Who is online.
i have been talking with one member who has told me that.

could that be caused by this modification?


All times are GMT. The time now is 09:17 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.01281 seconds
  • Memory Usage 1,745KB
  • 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
  • (7)bbcode_code_printable
  • (1)bbcode_php_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