/.htaccess in /themes

[DGTALGOODIES]

The original file .htaccess is caussing errors.

<FilesMatch "\.(xml|mail|html)$">
deny from all
</FilesMatch

.htaccess is a
deny on all xml, mail and html files causing every call to that theme folder to fail/error.

[FSGDAG]

Thats exactly what I have in my .htaccess in the /themes folder and everything seems to be working fine for me.

I think ( but dont quote me on this ) the purpose of it is so that you cant call one of those files directly. That is has to go through the script or be called from the script.

What error are you getting??? Can you post a URL or post a screenshot?

[DGTALGOODIES]

The error i get is in the error log of my website.

[error] [client 64.202.161.177] client denied by server configuration: /var/www/vhosts/example.com/httpdocs/themes/WGD/index.html, referer: http://example.com/

It will do that to every page u visit.

If u change, this <FilesMatch "\.(xml|mail|html)$">deny from all
</FilesMatch>

to this <FilesMatch "\.(xml|mail|html)$">allow from all
</FilesMatch>

All of those errors will stop.Now i dunno if that is the correct way to fix this.

[DGTALGOODIES]

Not the correct way to fix this it causes syntax error with explorer.

[DGTALGOODIES]

What do u think! Bruceper.
I need your help on this one.

[Bruceper]

First I'll answer something you didn't ask, WHY is the htaccess file there?

The htaccess with deny from all is there to prevent users from loading up any pages in the admin panel AND the template directory. It's a security measure designed to prevent pages from being loaded directly.

If you remove the .htaccess file and then try viewing some pages you will see that they can actually be displayed.

This file has been included with IndexU for years, and should never cause an issue to valid, legitimate users.

So now I have to ask a question, are you thinking/seeing that this issue is preventing the site from loading up files?

If so please give me the URL. From the path it looks like it's running Plesk (yuk!).

one thing you can try is to add allow from 127.0.0.1 BELOW the deny line.

[DGTALGOODIES]

I tried add allow from 127.0.0.1 BELOW the deny line. Still the same thing.
I don't know what to do i don't have all the expertise.

I do know that this error happens on localhost/ and online.

I asked for help and they told me...

Thank you for contacting Assisted Services.

It appears that for both the smarty error and the client denied by server configuration errors are both caused by scripting errors. The smarty error is caused by the class file calling several files that are just not there (example: example.com/httpdocs/themes//$base_path/admin_tpl/menu.html). In the case of the client denied error, you have an htaccess file in place at
/var/www/vhosts/example.com/httpdocs/themes/.htaccess that is a
deny on all xml, mail and html files causing every call to that theme folder to fail/error. You will need to correct these issues in your script in order to resolve them.

As for your question i don't know i don't understand.
I would like to pay u to help me but that seems impossible unfortunately

[Bruceper]

Lets put it plainly, your host is retarded. The smarty issue is known, but is a warning and not an error. The deny from all works on thousands of installations, if it's not working on yours it's because of the environment and how your host has it set up.

Send me the URL, admin login and FTP login to support at nicecoder.com

[DGTALGOODIES]

OK i just send the information to support at nicecoder.com

Thank You.

[Bruceper]

Now I'm seriously confused, because your site is working just fine with the .htaccess file there.

What files/pages are not working? Do you have a screenshot? What browser and version are you using?

[DGTALGOODIES]

All the pages work, the problem is every page that is loaded will cause an error in the error log. ERROR [error] [client 64.202.161.177] client denied by server configuration:

[Bruceper]

To fix the issue add AllowOverride All to your .htaccess file. But you can't do that because it generates a 500 error on your site. Your host doesn't allow it.

BOTH of these issues are caused by the apache environment, and has nothing to do with IndexU. If you continue to have issues then speak with your host. If your host is still clueless then change hosts and demand a refund for every penny you've given to them plus an extra $20 for being retarded and blaming IndexU.

As you can tell, I'm sick of hosts that suck and can't configure apache/php properly.

[DGTALGOODIES]

They don't know how to fix it. They asking me if u have any other suggestion or if there anything else that needs to be done for allow over ride all.
I would love to forward u my conversation with them and have u tell me what u think.
If u can tell me what needs to be done they will fix it for me.

[DGTALGOODIES]

Thank you for contacting the Assisted Services Team.

Thank you for providing the log on to example.com site. We have attempted changes to the example.com/httpdocs/themes/.htaccess file such as:

order from allow, deny
allow from 127.0.0.1
deny from all

or:

deny from all
allow from 127.0.0.1

We also tried adding and removing the "AllowOverride to All" setting. We did not leave "AllowOverride to All" setting active since you have indicated that it may have caused other issues. We still receive the same "client denied by server configuration:" error in the error log when browsing the site. Further research did not determine the specific cause of this error.

As you have suggested, the issue is that the application is not 100% compatible with our Apache environment and settings. Our administrators have reviewed the issue and determined this is the root of the problem. We are happy to make the needed changes on your server, however, we need specific settings that the vendor requires for the application. We appreciate your patience in this matter.

Please Somme one HELP.

I need specific settings that the vendor requires for the application.

[FSGDAG]

It might help if you posted what the PHP Configurations are... Do you know how to create a phpinfo file?