vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 2.x Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=4)
-   -   Control Forumjump Depth Level (https://vborg.vbsupport.ru/showthread.php?t=33189)

Swayed 05-06-2002 10:33 PM

I decided to test this out on a cleanly installed test forum, and got the same thing. I'm pretty sure it's caused by version 2.2.5. The error was not brought about by a change in the global.php file, but rather one of the changes made by the functions.php file (which is also mentioned in the error).

Maybe at some point I'll try to figure out what is going on (I really want this script), but for now I would say not to install it on 2.2.5.

Q8vbhacks 06-01-2002 02:10 AM

also me help i get

Parse error: parse error in /..../....../....../admin/global.php(79) : eval()'d code on line 1

in admin Control Panel

also in forumhome

Parse error: parse error in /..../....../....../vb/global.php(103) : eval()'d code on line 1

Warning: Cannot add header information - headers already sent by (output started at /..../....../....../vb/global.php(103) : eval()'d code:1) in /..../....../....../vb/admin/functions.php on line 1459

mgoiriz 06-01-2002 09:54 PM

I think there's a problem when, in install_forumjump_depth.php, this line gets executed:

PHP Code:

$result mysql_query ("UPDATE template SET template = template + '\$forumjumpdepth = \"$forumhomedepth_value\";\n' WHERE title = 'options'"); 

The field 'options' in table 'template' ends up being a simple 0, so all the previous options get deleted, and that's why I used to get the eval()'d errors.

Hope I helped.

Q8vbhacks 06-02-2002 05:57 AM

very thank but what A query but in phpmyadmin to remove this change & back like before

Kianor 11-12-2002 02:57 PM

I got the same error with 2.2.7, how can I go back again to a working situation?

Anyone knows a query to do to restore everything?

ZiRu$ 11-13-2002 12:37 PM

a friend of mine installed this hack. He has the same problem....now he has to start from scratch. It's too bad because everyone else is having problems too.

Edgemyster 03-04-2003 07:28 PM

i've got the same problem and it's completely killed my forum... :<

we managed to restore our template.template(title='options') value from a stored version, but changes made to the setting table are irreversible since they are mathematically determined. Not so sure they should have anything to do with the problem though. The options template correction did NOT restore the site's functionality.

We are running 2.2.9, so the problem is not version-specific.

Sincerely,
- Screwed

Edgemyster 03-04-2003 10:32 PM

After 4 hours of pulling our hair out ... we fixed the problem.

This is the issue that some of you may get after installing the hack that basically turns your site to crap (parse errors at the top of every page - php files refusing to run, etc.).

We tracked the error to a database table that is modified by this hack. A query within this hack's installation file basically killed (removed) the 'options' data the "template" table all together. We had to restore this from an old backup.

After having done that, we still have the same problem. Firefly actually suggests in another thread to access the AdminCP, load the options, then save them - indicating that should fix the problem. It may for some of you, but we couldn't personally access our AdminCP any longer.

To make a long story a little bit longer, we did the following and got things working again:

1) Restore the 'options' data to the 'template' table from an old database backup. Try this first if you discover that your data has been erased here as well.

2) If you still have errors focusing on this line in the two global.php files (as we did) that points to the data modified in the database by the hack:

eval($optionstemp[template]);

Then comment out that line in ADMIN/global.php. And then load the AdminCP.

3) Click on your VB options, then save the options in AdminCP, as Firefly had suggested, and wah-lah - everything of ours was back up and functioning again.

A rather easy fix for something we beat our heads over for the last 5 hours.

My suggestion? DO NOT load this hack if you're operating on or around version 2.2.9 until it's problems are addressed (if ever).


All times are GMT. The time now is 01:45 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.01119 seconds
  • Memory Usage 1,732KB
  • 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
  • (1)bbcode_php_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (2)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (8)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