The only time I have seen that in the past is when people choose not to merge the changes. It still presents changed files, but those files obviously don't have the changes included, so a recheck will report the changes are still needed.millipede wrote:went back to the install and it shows those files still need to be merged... even though, I uploaded the correct ones.
Well, I definitely tried merging them via the ftp upload and by downloading them and uploading them via filezilla. It still gives me that message about those files.The only time I have seen that in the past is when people choose not to merge the changes.
following those directions using the 3.1.0 install folder, I got the same result.. just a blank screen. I even tried using IE instead of firefox to see if anything would be different.... nope. No "server not found" or any other weird messages... just a blank screen.Run the /install/database_update.php file
The database_update.php file is in the Install directory, and there was no htaccess file there... so, like it said, I created one and added that one line. Sure enough, I can now see a php error that may or may not help in this issue...Generally a blank white page when you expect content is a PHP error. As we offer production servers and not development servers we have "display_errors" off by default which is why you would get a blank white page instead of an error message.
You can turn on "display_errors" by adding the following line to a file called ".htaccess" in the same folder as the script having issues:
php_value display_errors on
If the file ".htaccess" does not exist, you are welcome to create one for this purpose.
Edit: I downloaded functions.php and opened it in notepad++ and here is line 162 in case that's helpful...Fatal error: Call to a member function set() on a non-object in /home/********/public_html/forums/includes/functions.php on line 162
Code: Select all
$config->set($config_name, $config_value, !$is_dynamic);
config.phpfile, and the
/filesdirectories from the package.
stkdirectory from Support Toolkit package to the root of your board installation.
config.phpfile, and the
/store/modsdirectory, if it exists (it contains the MOD packages installed using AutoMOD).
/install/from the root of your board installation.
hmmm, I suppose you're right about that. I do have the css modified just a little by myself, changed the colors a tiny bit, etc... and a few mods... not many... will be sad to see them all gone just like that though.I think you should just start over and not use the auto update method at all.
none of your MODs or styles will work in 3.1 anyway so there is no reason to try to keep any of them.
At this point, I have no access to my board so getting to the ACP is not possible. Prosilver is the only style so that's all default. Spambot countermeasures though...... I don't recall what I have that set at. I imagine it's one of those but I can't promise. I don't believe I have any "mods" for that though so it should be okay.In Administration Control Panel (ACP) > GENERAL > Board Configuration > Board settings:
Default style: prosilver
Overide user style: Yes
If spambot countermeasures are enabled:
Go to > Administration Control Panel (ACP) > GENERAL > Board Configuration > Spambot countermeasures:
If the installed plugin used is not GD image, GD 3D image, Simple image, Q&A, or reCaptcha, then change it to one of those.
That's a scary thought... you really delete EVERYTHING except those folders and that file?delete everything from your board installation on the server EXCEPT for the config.php file, and the /files, /images, and /store directories.
TIP:That's a scary thought... you really delete EVERYTHING except those folders and that file?
I'll be getting to it shortly. We'll see how it goes.
Yeah, I don't have one of those. I'm not too worried... those ARE the directions for installing 3.1.1 so it should work out just fine.TIP:
Try it first on your test /backup forum or whatever you call it.
First, that tool is for use with 3.0.12 or earlier. While my database has not been updated, all the files were updated during the automatic update so I'm not sure if that will make a difference.Removing the 3.0.x MODs from your database.
Just to give me something to do that wouldn't take TOOOOO long, I decided to try that... I didn't think it would fix my problem as my issue wasn't matching theirs... and, it didn't. I still get that php error on line 162.Oyabun1 wrote:Try the suggestion mentioned here.