![]() |
You won't be able to upgrade your forum in future, unless you remember to rename the config.php file back to config.php and overwrite the modified class_core.php file BEFORE proceeding with the upgrade.
Edits to class_core.php should only then be re-applied AFTER the upgrade is complete. Here's the code in upgradecore.php that would stop you from upgrading until the file exists as "config.php": Note: You could also change the config.php reference in this file, but you'd have to remember to make that change every time the file is overwritten with the newer version when updating. Code:
// config file check |
Also, I recommend changing "config.php" to something as obscure as possible, as it's easy to read the contents of a folder in a php file.
Calling it "configuration.php" or "mynewconfig.php", even in another directory, doesn't make it particularly difficult for a hacker to figure out where your config.php has gone, if he wants to hack your site and already has the means to put a malicious file onto your server. :) |
I wonder if you can remove the current working directory and move it above root?
Like outside of public_html/ ? include('/home/inc/XXXXX'); or include('../../XXXXX'); |
No,it has to stay in vBulletin root.
|
It didn't work. What I did was made a folder in the root like this: blahblah/blahblah/newconfigfilename.
I came up with an error. Any ideas? TIA. |
Is the folder in vbulletin root?
|
Quote:
|
Is the set URL relative?
|
Quote:
Quote:
Quote:
|
is it works with vbulletin 3.7.x
|
All times are GMT. The time now is 02:16 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|