[Typo3] Using TYPO3's FE_Users to control httpd access on subdomains

[Thorsten Kahler]

Hi Kevin,

your first question indeed can be answered easier than the second ;-)

The extension realUrl [1] exactly does, what you desire in your first  
question: it generates very literal URLs like e.g.  
http://typo3.org/documentation/document-library/realurl/ - This points to  
the documentation of the extension :-)

I don't know if there's already a solution for your second issue. In  
theory you can use TYPO3s authentication services to authenticate against  
your apache server respectively a .htaccess file. But I must admit that I  
can't find a ready extension for this in the extension repository [2] at  
first glance.

Good luck,
Thorsten

[1] http://typo3.org/extensions/repository/search/realUrl
[2] http://typo3.org/extensions/repository/search

On Thu, 2 Jun 2005 14:31:43 -0500, Kevin Segraves <kevin at pmt.net> wrote:

> Hello,
>
> Two questions if you don't mind..One simple, and one that I am not even  
> sure
> where to start.
>
> 1.	I can't seem to figure out how to have some pages appear as
> subdirectories in the url address.  For example instead of having all  
> pages
> displaying from the root (http://typo.org/index.php?id=15" , I'd like  
> have
> some labeled as http://typo.org/news/
>
> 2.  I have a main site where I've installed TYPO3 (ie.  
> www.mydomain.com).  I
> also have several sub-domains (ie. stats.mydomain.com, help.mydomain.com)
> that contain documents, files, and static HTML pages.  I would like to  
> use
> TYPO3's FE_User groups to control my httpd access privileges but don't  
> even
> know where to start for documentation - or what apache/mysql/php module  
> to
> use.
>
> I'm running a Redhat 9.0 distribution on an in-house server.
>
> I don't expect someone to give me a step-by-step tutorial, but if you  
> could
> point me in the right direction, I'd be much obliged.
>
>



-- 
No Subject - No Realname - No Service!
Respect the List/Newsgroup Rules!
  >> http://typo3.org/1438.0.html <<

It's not a bug - it's an undesired feature.