291932
Quote:
This does make a lot of sence.
I've tried to use the TC as an 'about' module. Putted some subitems -of items I've created- within its xoopsversion.php etc., to realise what I wanted. Instead of using its block.
As you can imagine this way of working is not quit of handy, especially when there are some changes made afterwoods....
I recommend myself as a 'playlover' with such an about module
grtz.,Shine
Does this make sense? It would be like a mini-WF-Section module, only for static content... and without the many bells and whistles...
This does make a lot of sence.
I've tried to use the TC as an 'about' module. Putted some subitems -of items I've created- within its xoopsversion.php etc., to realise what I wanted. Instead of using its block.
As you can imagine this way of working is not quit of handy, especially when there are some changes made afterwoods....
I recommend myself as a 'playlover' with such an about module
grtz.,Shine
291933
I have been working on something like this with WF-Sections this last week.
It would be easy enough to have this 'WF-Channel'(Where do you get those names from lol) without that much of a problem.
I will start on this tonight and see if I can get something out in the next few days for all to play with.
Nice idea m8
It would be easy enough to have this 'WF-Channel'(Where do you get those names from lol) without that much of a problem.
I will start on this tonight and see if I can get something out in the next few days for all to play with.
Nice idea m8
291934
Hey, Catzwolf:
I'm not sure about what g0nk1 would want, but here's my own take:
Imagine a module callet, hmm, let's see: WF-Channel. It's a fairly simple thing that lets you build a content channel.
Let me explain. Most modules that include categories let you define the categories and then submit content that can fit in those categories. WF-Channel would have a single page and as many children pages as needed. Every page would need to be easily edited.
I know this can be done with Tiny Content. but TC's additional pages are indexed in a block. What separates WF-Channel from TC is that it includes the additional pages as subitems in the main menu entry, as well as optional related content links at the end of the index page.
Another dreamt of feature of WF-Channel: It creates its own instances. So, maybe g0nk1 wants an About Us page with three subpages: "History", "Site awards" and "Submission guidelines". Then he remembers he wants to put a What we do "channel" with "Products", "Services", "Guarantees"... He fires up WF-Channel, clicks on "Create new instance" and lo and behold!: He can do it, and he can manage every instance from within the same module...
Does this make sense? It would be like a mini-WF-Section module, only for static content... and without the many bells and whistles...
Cheers.
I'm not sure about what g0nk1 would want, but here's my own take:
Imagine a module callet, hmm, let's see: WF-Channel. It's a fairly simple thing that lets you build a content channel.
Let me explain. Most modules that include categories let you define the categories and then submit content that can fit in those categories. WF-Channel would have a single page and as many children pages as needed. Every page would need to be easily edited.
I know this can be done with Tiny Content. but TC's additional pages are indexed in a block. What separates WF-Channel from TC is that it includes the additional pages as subitems in the main menu entry, as well as optional related content links at the end of the index page.
Another dreamt of feature of WF-Channel: It creates its own instances. So, maybe g0nk1 wants an About Us page with three subpages: "History", "Site awards" and "Submission guidelines". Then he remembers he wants to put a What we do "channel" with "Products", "Services", "Guarantees"... He fires up WF-Channel, clicks on "Create new instance" and lo and behold!: He can do it, and he can manage every instance from within the same module...
Does this make sense? It would be like a mini-WF-Section module, only for static content... and without the many bells and whistles...
Cheers.
291936
g0nk1:
You have at least three options to do that:
1) Get the module called impressum. It's German and all it handles is a single page with text.
2) Get the module called About. Does the same.
3) Use an instance of Tiny Content to create your "About Us" online.
The three options are fairly easy to implement.
Cheers.
You have at least three options to do that:
1) Get the module called impressum. It's German and all it handles is a single page with text.
2) Get the module called About. Does the same.
3) Use an instance of Tiny Content to create your "About Us" online.
The three options are fairly easy to implement.
Cheers.
291937
Is there a module out there that would or could be used as a "About Us" Page?
Something that could display a histy of the site, site awards, submission guidlines, etc.. so it could be listed in the main menu and loaded as a seperate page like the Contact Us module...
Something that could display a histy of the site, site awards, submission guidlines, etc.. so it could be listed in the main menu and loaded as a seperate page like the Contact Us module...
291939
Novell uses eDirectory and openLDAP for authentification on their forge site (http://forge.novell.com), and they are currently upgrading that code to XOOPS2. Perhaps you can find some answers there.
Herko
Herko
291940
Hello,
does anyone run a XOOPS site requiring strong authentication ? I'd like to run a XOOPS site asking for a X509 certificate instead of a login/password, and matching certificate data with usernames (e.g. ; could be e-mail etc.).
Any hint how to do that simply ?
Thanks in advance for your ideas.
Xad
does anyone run a XOOPS site requiring strong authentication ? I'd like to run a XOOPS site asking for a X509 certificate instead of a login/password, and matching certificate data with usernames (e.g. ; could be e-mail etc.).
Any hint how to do that simply ?
Thanks in advance for your ideas.
Xad
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|