Last modified: 2013-07-30 00:10:50 UTC
It appears that some hosts append user tracking code to the end of load.php output. The specific code appended (to both js and css files): <!-- www.000webhost.com Analytics Code --> <script type="text/javascript" src="http://analytics.hosting24.com/count.php"></script> <noscript><a href="http://www.hosting24.com/"><img src="http://analytics.hosting24.com/count.php" alt="web hosting" /></a></noscript> <!-- End Of Analytics Code --> This obviously breaks stuff. (Additionally on people who have this issue also seem to somehow get load.php output a can't contact db server error somehow. not sure what the deal with that is). We should during the install process somehow check for this, and complain if load.php can't output stuff correctly.
It seems to me that you'd really have to use some sort of external site to check this since an internal check probably wouldn't show this. Does it show up if you do "curl http://LOCALDOMAIN/load.php" from the command line on the host?
(In reply to comment #1) > It seems to me that you'd really have to use some sort of external site to > check this since an internal check probably wouldn't show this. > Furthermore, load.php isn't going to work until after MW's installed.
>Furthermore, load.php isn't going to work until after MW's installed. That doesn't stop us from having a dummy php script that outputs js that we can use to check if its mangled. Without any information to back this up - I imagine doing Http::get( <url to self> ); would catch most cases - this doesn't have to bullet proof. Ideally it would just check if the result is totally mangled. If it can't connect to itself it could simply ignore checking for this. (In reply to comment #1) > It seems to me that you'd really have to use some sort of external site to > check this since an internal check probably wouldn't show this. Worst case scenario one could use ajax - but really I think that's overkill. > Does it show up if you do "curl http://LOCALDOMAIN/load.php" from the command > line on the host? I have no idea - its not my server. My intuition is its something that hooks into processing php files - in which case it would probably show up still, but that's just an unfounded guess.
