[Rosusmegus]

So.... Here we are newly installed now.....

Still get that code inserted in some places....
rss feed for ie8 is down the drain for an example.....

So.... Now another question.... If i go for Premium service here.... will that help? Or is it time to go somewhere else?

And... I'm not interested with circumventing stuff...
I dont want any code / scripts added to my site except what i put in there... Need complete control...

Possible here? Or not?

Exprience kinds of light up warnings in my head that if i stay here with that code still being "shot-in".... it will "bite-me-in-da-bu..." later

Like i said... I love this place It's just that this time it's for a project that i need to be able to really evaluate professionally...

[sizzlefire]

Originally Posted by Rosusmegus

So.... Here we are newly installed now.....

Still get that code inserted in some places....
rss feed for ie8 is down the drain for an example.....

So.... Now another question.... If i go for Premium service here.... will that help? Or is it time to go somewhere else?

And... I'm not interested with circumventing stuff...
I dont want any code / scripts added to my site except what i put in there... Need complete control...

Possible here? Or not?

Exprience kinds of light up warnings in my head that if i stay here with that code still being "shot-in".... it will "bite-me-in-da-bu..." later

Like i said... I love this place It's just that this time it's for a project that i need to be able to really evaluate professionally...

If you upgrade, then there is no such code.

[bonzairob]

I've just run into the same error. It wouldn't bother me too much, other than it's happening because I want to use a .php file to load some JavaScript.
I've done some testing, and the script doesn't turn up in .js files, which is good. However, even after changing the header of the PHP file to text/javascript, it's still included.
Keep the code by all means, but please: make it check the header type, not the file extension!

[luctranquoc]

Just fix it with 000webhost analytics code management.
Original resolution: http://www.sometip.tk/2012/07/remove...on-000webhost/

[jadtech]

I thought I read some wher in another post maybe this forum maybe another that there is something that can be added to the htacess file that could get rid of this type stuborn code..

[ShocK]

There is, about half way down this post - FAQ - Frequent Ask Questions Guide!

[WorldOfBullcraft]

There are a few ways to remove the analytics code and in a few degrees.
You can completely shut it down, you can shut it down for certain filetypes, you can shut it down for certain files (where you don't want the injection to take place).

Shutting it down completely can be achieved trough the control panel: http://members.000webhost.com/analytics.php

Shutting it down trough the .htaccess file can be achieved by adding this line to your .htaccess file:

php_value auto_append_file none

Save and reupload to your server and the analytics code is not injected anymore.

Allowing the injection to take place on certain file extensions only can be achieved trough adding and altering this code to your needs:

First some examples to protect .extension groups like .htm(l) or .php etc.
The link to the Analytics counter I found trough looking at the source of a injected html file so this should be accurate.

If one is to add this to the .htaccess you inject only into html files in the directory where you place this .htaccess:

 
<FilesMatch "\.(html?)$">
php_value short_open_tag "Off"
php_value auto_append_file "http://analytics.hosting24.com/count.php"
</FilesMatch>

And if you want it to affect php files, change the first line to this:

 
<FilesMatch "\.(php)$">

This you can do for each .extension, or even add a few extensions in the same line like:

<FilesMatch "\.(php|html|htm)$">

If you only want to protect certain specific files from being injected you can use the following code (which I use myself for a security script that cannot be injected because it corrupts that script):

<Files the_file_you_want_protected.php>
php_value auto_append_file none
</Files>

Ofcourse you will have to rename "the_file_you_want_protected.php" to whichever file it really is that you want protected including it's extension.
It would effectively protect that file from being injected while leave the rest of the site alone and have Analytics have it's way on the site.

This is from my own trial and errors. You can find my original post here: [Wordpress] Website Defender Plugin Problems

Good luck, Mike.

Edit, My 100th post yay :P

[kuroneko]

I don't really understand.

It's simple to get rid of the code, if you have a php file then just do the following:

</html><?php die(); ?>

Your website will die before it can show the analytics code.

But is this even legit?

[leeway]

You can go to http://members.000webhost.com/analytics.php to disable analytics code