1.1.1 - 1.1.2 upgrade works fine but many, many errors in log

[catfished]

Version 1.1.2, a few simple mods, using the default (core) theme:

I upgraded from 1.1.1 to 1.1.2 using the link in the admin panel on 4 different forums. All went well on all 4 except that the upgrades created anywhere from 100 to 300 or more errors in their respective error logs. Everything seems to be working fine with all 4 and they're all showing version 1.1.2. All errors were logged at the same time within a few seconds in their respective forums and there have been no other errors since. They were evidently all created during the upgrade.

Here's a couple of examples of errors from different forums:

Apply Filter: Only show the error messages of this member  catfished       February 12, 2007, 03:11:43 PM
http://www.mizjossie.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fclose(): supplied argument is not a valid stream resource
File: /home/jossette/public_html/forum/Sources/Subs-Package.php
Line: 1909

Ed       February 12, 2007, 08:23:08 PM
http://norcalcarpclub.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fopen(/home/norcal/public_html/forum/Themes/default/languages/Login.german.php) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied
File: /home/norcal/public_html/forum/Sources/Subs-Package.php
Line: 1902

[bcswebco.com]

Yes ... after reading this, check my log and found 167 pages of the same errors described.

[catfished]

Yes ... after reading this, check my log and found 167 pages of the same errors described.

Thanks bcswebco.com, I had a hunch I was not the only one. I wonder if we should worry about them or just delete them and pretend they never existed?

[bcswebco.com]

I'll make a W.A.G. on this and say probably all is well ... hopefully one of the support folks here will chime in and confirm. 

Looking at the errors I would say that some of the files (i.e. Subs-Package.php) could not be accessed because of a permission issue.  You might want to check the detailed listing of files just to be sure they were updated.

In my case I had other upgrade issues, so I used the "webinstall.php" tool to upgrade from 1.1.1 to 1.1.2, which wrote over to update all files.

[catfished]

I'll make a W.A.G. on this and say probably all is well ... hopefully one of the support folks here will chime in and confirm.

Thanks,

Yeah, I really wish one or more of the support folks would chime in and confirm or deny. I imagine lots of people have experienced the same thing but aren't aware of it due to not yet checking their forum error logs.

You might want to check the detailed listing of files just to be sure they were updated.

I guess they were all updated, a lot of forum files are dated 2-12-07 when viewing them in my FTP program. 

[青山 素子]

We are all volunteers, so please be patient with us.

Notice the one file listed in the error message: "/Themes/default/languages/Login.german.php". Do you have a language pack you were using that doesn't exist anymore?

[catfished]

We are all volunteers, so please be patient with us.

Notice the one file listed in the error message: "/Themes/default/languages/Login.german.php". Do you have a language pack you were using that doesn't exist anymore?

Thanks for the reply. I only use English and have never installed any language packs. Keep in mind that this is occurring in every forum that I've updated, four so far. There are errors for every language and many other files in the forum but the forums all seem to work perfectly.

Like I said in my previous reply:

I imagine lots of people have experienced the same thing but aren't aware of it due to not yet checking their forum error logs.

[SleePy]

catfished,

This error shouldn't occur. And from the looks of it SMF is finding a index.german.php so it is trying to load the other language files but errors are occurring of it not finding it.
Are you sure english is the only language on that board

[catfished]

catfished,

This error shouldn't occur. And from the looks of it SMF is finding a index.german.php so it is trying to load the other language files but errors are occurring of it not finding it.
Are you sure english is the only language on that board

I guess I just don't know how to communicate this. First of all, I don't know what languages may be available but I never installed or added anything to do with languages in any of the 4 forums that I have but they all gave similar errors right at the time I upgraded them from 1.1.1 to 1.1.2 with the link in the admin box.  There were many other errors for several different languages such as German, Dutch and Spanish plus many, many other types of errors such as Themes/default/Register.template.php and Themes/default/Poll.template.php.  I just listed a couple of examples. Here's a couple more:
http://norcalcarpclub.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fclose(): supplied argument is not a valid stream resource
File: /home/norcal/public_html/forum/Sources/Subs-Package.php
Line: 1909

2: fopen(/home/norcal/public_html/forum/Themes/default/languages/Login.english.php) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied
File: /home/norcal/public_html/forum/Sources/Subs-Package.php
Line: 1902

Here's a couple from a different forum:
http://catfished.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fopen(/home/catfish/public_html/forum/Themes/default/languages/index.english.php) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied
File: /home/catfish/public_html/forum/Sources/Subs-Package.php
Line: 1902

http://catfished.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fopen(/home/catfish/public_html/forum/Themes/default/Register.template.php) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied
File: /home/catfish/public_html/forum/Sources/Subs-Package.php
Line: 1902

And from another forum:

http://www.mizjossie.com/forum/index.php?action=packages;sa=install;package=smf_1-1-2_patch.tar.gz
2: fopen(/home/jossette/public_html/forum/Sources/ManageSearch.php) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied
File: /home/jossette/public_html/forum/Sources/Subs-Package.php
Line: 1902

I really don't understand how I can have all those installation errors in these forums and they seem to run perfectly.

[bcswebco.com]

Ed -

If:

1. copyright tag is showing 1.1.2
2. all appears to be running fine
3. A detailed listing of the files (the display box on the right
   of the main admin page) shows current versions

... I would not sweat it.  This is just my humble opinion.  I've
noticed that the error log will throw in a bunch of entries in previous
upgrades/mods just while determining that the script needed my
FTP log info to change permissions.

Note to support: For the record, my errors were not just language file specific and I only
use English on my board.

- Bill

(btw: that is a whopper of a cat!!)

[catfished]

Ok folks,

I had to figure it out myself as usual. It seems that it was a permission problem. Even though it came up with the password box to change permissions before it would install, it was evidently not CHMODing them correctly. It was logging an error for each file that it wrote to plus a Subs.php error for each file. Evidently, it was still writing to the files since the upgrades worked flawlessly but all those errors in the logs really made me nervous.

Now the fix:

I uninstalled the upgrade packages and deleted them. I then went into the Package Manager options and  set them to "all files are writable". Then I clicked on the link in the Administration Center to upgrade back to 1.1.2. Everything went fine and there were no errors. I of course then went back into Packages options and changed the permissions back to "Only the standard files are writable"

I still think there are at least a few other folks that are getting these errors but are not aware of it. I suggest people check their error logs right after upgrading just in case.