Oh, Nice! So you edited your post while I was typing a reply (that apparently wasn’t needed). Meh, I’m glad you got it accomplished.
I don’t use vbulletin, so I do not know where it gets the info to report that information, or if it is a configurable setting in vbulletin. Generally speaking, such things are set by an application at install time by querying the PHP installation, or set by the application dynamically at run-time. If you installed vbulletin before you made the change, it may need to be reset in vbulletin. Then again, as I said, I don’t use vbulletin, so that is only “an edumacted guess”
[quote]So now what? Did it go through or what?
I have no way to know that, but you can easily check it yourself by running a phpinfo() program, and seeing what is reported.
If it “went through”, the phpinfo() report will show the path to your copy of php.cgi and php.ini (the ones in your cgi-bin directory, not the DH common directories), and will show your new upload_max_filesize value. If those thing are correct in the phpinfo() report, then the remaining problem is somehow related to a vbulletin setting
If you don’t see those changes, then it “didn’t take” and you are still doing something incorrectly. You will then need to “get it right” and repeat the phpinfo() confirmation process I just described to see that it has worked. Only then should you worry about vbulletin.
Edit: Ha! you edited that last post again while I was typing another (again, apparently unneeded) answer… remind me next time to wait at least an hour before responding to your posts … and you’re welcome!