|Due Date:||Dec 31|
What is Auth module?
There are already HTML file wrapping modules for Xoops, like
TinyContent or iContent.
The problem with these modules, is that it is quite troublesome
to put the content in the xoops menu and additionally it requires
quite a lot of editing of the original html files.
There is most likely a need to have a xoops module that can easily
put html contents under separate xoops menus, so this is why I have
developed the "Auth module"
Additionally the Auth module will allow .php and .CGI files to be included instantly into Xoops, without the need to do any modifications. There are probably people that have some knowledge about using .php or .cgi, but would not be able to create a complete module.
All you need to do is put the .html, .php, .cgi and even image files into the designated "Auth module" folder and they will be automatically wrapped with the xoops header and footer and display properly in xoops.
The comments are owned by the author. We aren't responsible for their content.
I carried out this procedure myself quite successfully on a 500 page website using wf-section.
How do you preserve the links between the different html pages when importing them into wf-section?
Published: 2004/12/23 0:41 • Updated: 2004/12/23 0:41
I looked at this project from every angle and could not find a quick easy fix!
creating a new document in a XOOPS site inevitably changes every part of the URL, so you have to be prepared to recode all your links manually. If you are interlinking other XOOPS pages, chances are they need to be pulled from the database, so that will require a query.
If yu want to go down the route of "wrapping" an existing site in an iframe, this becomes a little easier, BUT the trade off is severe. Nothing is integrated in the XOOPS website and what happens when a S/Eengine calls and serves one of your wrapped pages? Will it include your XOOPS website? no, just the html page! This is an old problem encountered when building a Frames website... linking the content page so that the frameset was included as well. Maybe this could be achieved in xoops, but there will be other connectivity and search problems.
The ther option as stated in this http://www.xoops.org/modules/smartfaq/faq.php?faqid=253 FAQ is to 'include' your pages. This becomes a more managable project. You could use a good search and replace program like http://www.orbit.org/replace/ and insert the header and footer snippets in each of your existing html pages. Thet will now all be included in your XOOPS site and their relative URLs will be the same. If not use search and replace again to correct this. The challenge now is reaching them. Probabbly use a menu system like multimenu. It's a lot of work!
It took me 4 months of evening work cutting and pasting a few pages into wfsections. In the end it was worth it.
Published: 2004/12/23 3:40 • Updated: 2004/12/23 3:52
Check out the auth module. It supports cross links between pages and pictures.
I've made a rough translation of the readme see here
Published: 2005/1/8 15:45 • Updated: 2005/1/8 15:45
Hello, I'm curious what the easiest way to wrap EXTERNAL content on another site might be?
I have to manage a non-profit site with some content stored as plain html pages on external hosts. It would be great if I could just put in a URL and have that one page wrapped in XOOPS theme.
Thanks for your help!
Published: 2005/1/29 15:07 • Updated: 2005/1/29 15:07
If the page is offsite to your own server, the easiest way is to use an iframe to display the page within a XOOPS custom block
Look in thr FAQ section HERE
To do this properly, you need to create a custom page using This FAQ here
Then insert the iframe into that custom page.
After that use multimenu to link to your new page.
It will automatically load the external site
Published: 2005/1/29 15:46 • Updated: 2005/1/29 15:51
This works perfectly and is quite simple to set up.
The only weird thing is having to adjust the height to pixels. Is there a way to just let it stretch vertically as it wants to?
Adding vertical scrollbars would help too, not sure how to do that yet.
Published: 2005/2/4 1:49 • Updated: 2005/2/4 1:49
you can use 'auto' instead of a defined height. Problem is the page usually displays a little longer than really required. If the page is going to change a lot in height, auto is best, whereas a fixed height gets a much tighter fit for fixed content size.
Published: 2005/2/4 7:03 • Updated: 2005/2/4 7:03
Ok. I think if there's one thing XOOPS needs the most is some kind of PR / Organizational effort that takes business objectives (I mean business loosely here) and says:
Commerce -> Use this block and here is a faq list
Static Content -> Use this block....
Wrapped External content -> ....
Wysiwyg Editing -> ....
News Publishing -> ....
Right now you have to go through 6 modules (APS, WFSections, News, etc. ) to figure out anything about managing stories. Same for anything else.
The language at XOOPS is too focused on modules for the sake of modules, and not enough on what people want to do in real life, leaving modules per se aside.
I hope I can contribute to such an effort
Published: 2005/2/4 10:27 • Updated: 2005/2/4 10:27
I hope I can contribute to such an effort
Pm me if you want to help with documentation, we have some exciting projects going on right now that are relavant to your commenst here
Published: 2005/2/4 12:05 • Updated: 2005/2/4 12:05
We have created a custom module which contains iframed content. We would like to have XOOPS blocks under the iframed content. However when we insert content blocks these blocks appear above the iframed content. Is there a code which would insert
a specified amount of space above content blocks.
Published: 2006/3/21 9:04 • Updated: 2006/3/21 9:04