FRESH install fails on apache windows XP Gallery 2.3.1
|
whiteknight0571
Joined: 2005-05-16
Posts: 8 |
Posted: Sun, 2010-12-05 17:34
|
|
Gallery version (not just "2"): G2 FRESH INSTALL DOWNLOADED TODAY For whatever reason, using the installer faults at step one, meaning, I downloaded the files, shipped them to my local testing server, unpacked them and hit the install folder. I get errors at the top of the screen at start as follows: Strict Standards: Non-static method GallerySetupUtilities::startSession() should not be called statically in C:\server\htdocs\gallery2-3\install\index.php on line 85 Strict Standards: Non-static method GalleryUtilities::getRequestVariablesNoPrefix() should not be called statically in C:\server\htdocs\gallery2-3\lib\support\GallerySetupUtilities.class on line 320 Strict Standards: Non-static method GalleryUtilities::_getRequestVariable() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 289 Strict Standards: Non-static method GalleryUtilities::_internalGetRequestVariable() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 875 Strict Standards: Non-static method GalleryUtilities::_internalGetRequestVariable() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 879 Strict Standards: Non-static method GalleryUtilities::sanitizeInputValues() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 293 Strict Standards: Non-static method GalleryUtilities::sanitizeInputValues() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 708 Strict Standards: Non-static method GalleryUtilities::sanitizeInputValues() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 714 Strict Standards: Non-static method GallerySetupUtilities::areCookiesSupported() should not be called statically in C:\server\htdocs\gallery2-3\lib\support\GallerySetupUtilities.class on line 326 Strict Standards: Non-static method GallerySession::getRemoteIdentifier() should not be called statically in C:\server\htdocs\gallery2-3\lib\support\GallerySetupUtilities.class on line 365 Strict Standards: Non-static method GalleryUtilities::getServerVar() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GallerySession.class on line 1266 Strict Standards: Non-static method GalleryUtilities::sanitizeInputValues() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 1408 Strict Standards: Non-static method GalleryUtilities::getRemoteHostAddress() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GallerySession.class on line 1267 Strict Standards: Non-static method GalleryUtilities::isTrustedProxy() should not be called statically in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryUtilities.class on line 1008 Strict Standards: Non-static method GallerySetupUtilities::getConfigDir() should not be called statically in C:\server\htdocs\gallery2-3\lib\support\GallerySetupUtilities.class on line 367 Strict Standards: Non-static method GallerySession::compareIdentifiers() should not be called statically in C:\server\htdocs\gallery2-3\lib\support\GallerySetupUtilities.class on line 370 Strict Standards: Non-static method GalleryUtilities::strToUpper() should not be called statically, assuming $this from incompatible context in C:\server\htdocs\gallery2-3\modules\core\classes\GalleryTranslator.class on line 418 From there, I go to hit the Begin Installing button and am taken to a forbidden page. No real error ouput, and I think I now know why, but do not know why the problem is happening. If I copy link from the intall button, I get the following link: http://localhost/gallery2-3/install/%3Cbr%20/%3E%3Cb%3EStrict%20Standards%3C/b%3E:%20%20Non-static%20method%20GallerySetupUtilities::areCookiesSupported()%20should%20not%20be%20called%20statically%20in%20%3Cb%3EC:/server/htdocs/gallery2-3/install/index.php%3C/b%3E%20on%20line%20%3Cb%3E318%3C/b%3E%3Cbr%20/%3Eindex.php?step=1 It faults there, forbidden page with unformatted html code showing in the browser window in IE. Anyone have a clue what's going on with this or how to fix it? It almost appears that the installer in not getting the correct parameters or link for step 1 of the install. Any help would be greatly appreciated. ***EDIT*** |
|
Posts: 8
Oh, and no, STRICT reporting is NOT enabled, but still getting the output it seems.
Posts: 8
You've got to be kidding me. OK, NO error reporting able to be on in php.ini for 2.3.1 to install. I really hope you devs are planning on doing something to keep that from being an issue in the code. For now, I'm at step 2, we'll see how it goes. For the rest of you with similar errors, ALL ERROR REPORTING MUST BE TURNED OFF for gallery to get past step 1. Sure would be nice if that was in BIG LETTERS on the install pages, which it presently is not, and MOST hosts will have SOMETHING turned on.
Posts: 8
A quite simple fix to this would be to include turning errors off within the code with the following:
// Turn off all error reporting
error_reporting(0);
Simply place it at the top of the file just after the <? line
Would be easier than haveing people search hours to figure out why their install isn't working. As long as that is included in the install header php file, no reporting what so ever would happen, thus preventing the errors I listed above.
However, with some further reading, as relayed by http://us3.php.net/manual/en/function.error-reporting.php
Hence another way to make sure your installer is pre coded with error reporting OFF to prevent such future issues with gallery2.
Posts: 1642
Why rant about an application's reporting levels when it is simply respecting the reporting levels YOU have set on your server?
If you don't want applications to use strict error reporting, don't set up YOUR server telling them to do so.
--
dakanji.com
Posts: 8
@Dayo How about all the others that DON'T have their own server? The rant wasn't about those that have their own, it's about those that DON'T have their own and can't turn off reporting. Guess you missed that. Why do you rant about a valid comment for others with the same situation and no abilities to turn off reporting? Also, clarifitcation point, it's not just STRICT that tosses off the install, it's ANY reporting on a windows server with apache running it seems, again, something that people without their own servers can't control. Again, something that could be easily controlled through a couple more lines of code which would prevent the issue. Not to mention that NOTHING within the install notes says anything about reporting needing to be off or the install will fail, which again would help keep people from searching for hours or days trying to get their install to work for said reasons, but flame on.
Posts: 8339
No production server should have strict reporting on.
And in your searches for your problems how many others did you come across complaining about strict error reporting being an issue? Maybe one or two?
This is not an issue devs need to address.
Direct quote from gallery2/config.php after a successful install:
-s
FlashYourWeb and Your Gallery with The E2 XML Media Player for Gallery2
Posts: 8
Once again, I turned STRICT off, left reporting on, and STILL with ANY error reporting enabled, install failed. So, once again, what you are missing is the simple fact that ANY error reporting enabled on a server, at least windows and apache, can and WILL kill the install. But, that's not a dev issue I guess, so be it, moving along. ALSO, you miss the fact that I couldn't even get the install to go from initial steps before I turned off ALL reporting. Hence, I NEVER got the information YOU quoted. So that helps people in my situation, or anyone on a host with ANY reporting enabled how? Have a nice day.
***EDIT***
As for the number of posts on the subject, ever think that maybe people just don't bother because they can't get it to install and just move on? If that's what the devs want, then so be it. If not, I'd highly suggest updateing install and site information to let people know about reporting and the problems it will cause because of the installer.
***EDIT2***
Don't want people to just move on after reading about error reporting on and there's nothing they can do about it? Don't want people to move on because the installer doesn't work? Then code the installer to turn it off so the install goes through. Simple information added in this post to try to improve an already excellent open source software, that's never been in debate.
Posts: 1642
It is not Gallery reporting the errors, it is PHP and PHP will report errors according to how the server admin has set it up. So if a server admin wants to see strict errors and warnings, it is their choice and applications should not be overriding this conscious decision.
In any case, I participated in testing G2.3.1 before release and it works perfectly ok under strict reporting conditions. It was tested under these conditions to make sure all PHP 5.3 errors were accounted for. This was under under Linux however and not Windows but then, anyone running a Windows webserver deserves whatever comes their way
As for your suggestion to add the switch to cancel errors for Windows installations, please consider updating the documentation accordingly for Windows users.
By the way, "G2 FRESH INSTALL DOWNLOADED TODAY" is meaningless. Give the version number you are running.
--
dakanji.com
Posts: 8
Seriously, doesn't work? You can't see the date and time on the post to know what today is, so you wouldn't know what version it was? Dayo, I can see there is no point in trying to say anything to help solve this issue where you are concerned. Regardless of what "anyone running a Windows webserver deserves whatever comes their way", there are still potential users of gallery that do not have an option, that wind up hosting on windows servers, and are not maybe as technically savvy as others in this forum. If you wish to preclude them from using the software, then once again, keep your stance as it has been. As for updateing the documentation, I can do that how? If I can, I'll be glad to do so for windows users.
Not everyone is as technically savvy and versed as many who use this forum. Not everyone is totally knowledgeable about the differences nor the limitations/bugs of certain server OS combinations. I'll not even get into server builds that may also toss plenty of potential issues into the equation. As I said, the point is still valid, depending on the wishes of the gallery developers. Either you want to ensure that people can use the software, or you don't. If you want to ensure, you take the steps needed to ensure it. My posts have endeavored to help make sure that intentions were met as developers intended them to be met. If it is not the developers wishes to address this issue, then that is there choice. In the end, I did my part, I brought the issue to them for their consideration.
***EDIT***
Found the page, not part of the user group, so therefore, cannot edit the information. Page is located at http://codex.gallery2.org/Gallery2:Installation_on_a_Windows_Server_with_Apache so have already tried to add the note to the page to no avail.
***EDIT2***
Changed topic for later users attempting to find information on this issue. Better now Dayo?
Posts: 1642
Try registering on the doc page and then you can edit it to add stuff. Use the "create account" link on the top right. You can put your suggestion under trouble shooting.
--
dakanji.com
Posts: 16504
If you installed Apache, MySQL, PHP, etc on XP using XAMPP, this doesn't happen. At least it didn't the last time I installed and ran XAMPP.
EDIT: So what I'm saying is that they are using sane values for a production site. Why you'd have PHP set to display errors on a production site is beyond me.
____________________________________________
Like Gallery? Like the support? Donate now!
Posts: 8
It's not a production site, it's a local test bed, which I didn't use XAMMP or any other "boxed" solutions. I'm not a server admin, so, things were kinda set at default. There are others, I'm sure who fall into the same category as I do, self server to test things before putting them online, development in a local environment etc. I could also still see where this could be an issue for someone hosting with a fly by night company. Many exist. Many lure people in because of the cheap hosting prices, etc. I didn't think the present gallery devs would wish to shut such people out because of an installer issue, hence the reason why I posted this to begin with.
It wasn't about my issues, it was about those that might come after me, those that may have come before me, those that wished to be able to use gallery because of the quality it represents but are limited because of their hosts, or their server knowledge as relates to a local one and it's setup. I didn't use boxed solutions as I'd much rather be able to set up and build the test bed with what is needed, not be locked into something that doesn't update often enough for functionality I may need at any given time. As time goes on, I am learning, but I don't know it all yet.
***EDIT***
And the "doc page" is burried where? I went to the page linked above, there is no create account link anywhere on that page that I can see.
***EDIT2***
NVM, found a place to create an account for the document pages. I will endeavor, within the next days, to write something up relateing to this issue and include some other information for those who may be useing the mod_security build to harden their servers. That is another thing I found when trying to install gallery 2.3.1, with the way that the installer sends information during installation, and with the way it sends information after an install to update administration settings, it doesn't play well with mod_security. I found I had to disable the module in httpd.conf before I could get anywhere with gallery configuration even after the install.
Posts: 1642
***DELETED***
--
dakanji.com