Features / Usability

Hello J,

the .htaccess in a directory that shall not be readable from the web can be set up as following:

<FilesMatch ".*">
	order deny,allow
	deny from all
</FilesMatch>

Anyway I'd strongly suggest to use a different setup and to store the files "outside the tiki root" in a directory where no domain points to.

Given, your public_html is equal the Tiki root, you could create a folder a level higher "besides" the public_html.

Example:

{CODE()
htdocs/useraccount/public_html
htdocs/useraccount/files
htdocs/useraccount/files/gallery
htdocs/useraccount/files/wiki (optional, I use gallery)
...
{CODE}

Then your path in the tiki-admin.php?page=fgal would be:

../files/gallery

The two dots before the slash mean "one directory level up".

Please mind to set appropriate permissions to the files directory recursively - if nothing else works, use:
chmod -R 777 files (or analog in a cpanel dialogue)

Do you work with cPanel?
A hint:

In standard cPanel setups on usual shared hosting, the primary domain always points directly to public_html.

This is very bad, if you want to install more than one website, as then you literally are forced to install websites "into each other".
You could ask your provider to change the document_root (of the primary domain) to a subdirectory of public_html.
This way you could install your Tiki into a directory alike /htdocs/useraccount/public_html/tikiroot and then have plenty of space for parallel additional installations - at least very handy, when you want to install and test an upgrade of your side without risking to brake the live site.

IHope that helps,
Torsten