TYPO3 Core

Also .htaccess in typo3/

The .htaccess file is not enabled by default (_.htaccess) , isn't it?

So I don't see a need to do something here.

Greets,
Thomas

Hi Dmitry, I think especially you should have a close look at this... ;-)

See http://lists.netfielders.de/pipermail/typo3-team-core/2006-September/005608.html and replies.

I will look what we can do...

By the way, I cannot find .htaccess in typo3 folder.

In the current svn there is an .htacc in th sysext folder, but non in the typo3 folder

Current files require "AllowOverride Indexes" for caching to work. This gives huge performance improvments and lowers traffic a lot. The question is what we do:
- release typo3 as before, in unoptimal configuration (with renamed .htaccess)
or
- release with optimal configuration (with .htaccess) and make a note about renaming or configuring Apache

So far I did not see complains in mailing lists about .htaccess.

I understand that some virtual hosts may disallow mod_expires but typo3 is not Mambo, it is generally used in more serious environments and enabling Indexes is not a problem. Personally I see no reasons to release unoptimal configuration...

Both solutions would be finde for me.

Michael, your choice?

Dmitry, would it be possible to put this into a condition?

<IfModule expires.c>
...
</IfModule>

Unchecked, though!

As long as the default configuration can block an installation, I see this as a no-go. However, if you can tweak .htaccess so that Ingos default-setup doesn't trigger an error, then go ahead.

- michael

The condition won't work, as, for example in our case, it only checks if the module is existing, not if it's allowed to change the directory setting.

<IfModule> is there, it does not help. And there is no check for AllowOverride in Apache. So, if it is "no-go", we have to ship typo3 in non-optimal configuration. This is bad... :(

Just add an smal text to the installation guide, this would be perfect !

Michael, may be we just go with a note? I really think it is bad to go without this performance increase. Most people, who install typo3, will have control over their servers. Others can do manual rename.

It is not difficult to me to rename those ".htaccess"es in svn, I simply think that it is impractical. Imagine that Ferrari/Formula-1 engineers care about people, who want to drive Ferraries over country roads. Not bad but totally impractical...

Hi guys,

I actually think we should rename the files to _.htaccess, because a TYPO3 installations that works at all, is IMHO a very important point for people not to give up using TYPO3 in the very beginning.

We can easily put a note about this in the installation guides.

Dmitry, what do you think? Would be great if you could rename them in SVN.

cheers
Ingmar

Ok. I will remove those performance enhancements if you wish... Let it be so.

Renamed .htaccess files, corrected NEWS.txt

Thanks Dmitry.