26
EXAMPLE above, I created a folder on my desktop, it was so crowded I made the folder so as to show that 'save as' would also create a folder that goes with the htm file.
You can then edit the htm page for the iformation you want to display with whatever changes you deem necessary, you can do this with your own html editor. I use frontpage.
Of course, you will use your own theme when you save as and copy and paste or create from scratch the appropiate text.
That is all there is to creating a new html page with the static information you want.
Link to that page. In this example it is on my server and my link would be...
http://xoops-end-user.com/xoopshelper/termsofuse.htmIt is then ready to link to from the footer as previously talked about. It's done... no content module needed. The links and theme will be uninform with the rest of your site.
NOTE: Another advantage of doing it this way is that you have an additional trouble shooting tool if the site goes down. If you can get to this page then the problem is xoops, if you can't the problem is your server. This method provides an independent login in the event you accidently turn off the login feature to yourself. Happens often accordig to the questions on this site. I even did it.
There are many practical reasons for doing it this way.
Including outright cost of service bytewise. Additional unneeded modules for static pages are not cost effective and could at some point in time become a target for mischieve. As the current WF-Channel.
Google even gives preference to those including some pure html pages as standing out from the norm.
Ok, I've stated my case... XOOPS is great, but you sleep better when you intergrate it with other programing formatsfor backup purposes.
Good luck... and welcome aboard!