5
Yo Yo CatCity...Great Tip!
Thanks, I have been wondering how static content is dealt with properly in the XOOPS environment.
Following your instructions, I cut & pasted "da code" into a custom block and positioned it within my front page. Now, all I have to do is tweak up my static content for this block. Are there any suggestions where to place static HTML for XOOPS sites? For my XOOPS site, The XOOPS Download module and an Apache
Alias directives share the same directory. (facilitates non-Xoops and XOOPS downloads in one swipe)
<apologies for the rustic graphics...not my forte>
Here is the relevant section from my
httpd.conf creating a download repository accessible via directly by browser or via Xoops...not rocket science, but Apache is fun, if you got "da privs".
#download repository
Alias /downloads/ "d:/web/downloads/"
<Directory "d:/web/downloads">
Options Indexes FollowSymLinks MultiViews IncludesNoExec
AllowOverride None
Order allow,deny
Allow from all
</Directory>
I am not too concerned about the "Allow from all" in my environment, but it a nice option to exploit if necessary