I'm working on a module to integrate htdig with CMS. This is my first module, so I'm learning a lot as I go a log, and borowing heavily from the skeleton module, but there's one thing that I'm really stumped on.
I have one situation, where the action is set to default. This displays the search bar. I have another case for the search result (using action=search). It works as expected on the normal page, but on the search results (in moduleinterface.php) it ends up displaying both of them as the search results! Using {cms_module module='Examine' action='default'} doesn't seem to help at all. I've provided a workaround, using {cms_module module='Examine' force='default'} and adding a bit of code, but it's not very intuitive, and probably not the best way to do it.
Any help?
module recursiveness
Re: module recursiveness
I assume you're using CreateFormStart()?
There is an extra parameter in there for doing stuff "inline". This means that the results will be displayed in your cms_module tag and not in moduleinterface.php. The params are:
function CreateFormStart($id, $action='default', $returnid='', $method='post', $enctype='', $inline=false)
Set the inline to true and you should be set.
Hope that helps!
There is an extra parameter in there for doing stuff "inline". This means that the results will be displayed in your cms_module tag and not in moduleinterface.php. The params are:
function CreateFormStart($id, $action='default', $returnid='', $method='post', $enctype='', $inline=false)
Set the inline to true and you should be set.
Hope that helps!
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: module recursiveness
excelent, cuz an htdig integration thingy was on my list.... can't wait till it's available.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
-
trick
Re: module recursiveness
Well, here's a status on the project. I have it working on my own test server (I'd love to show it to you, but a mail server is stealling my DNS). However the level of integration is pretty bad, and the code need a bit of cleaning up. There's also a bit of documentation work that needs to be done, and I need to write a whole admin interface, before I can let this thing go into alpha. Provided I don't get incredibly swampped with real-life work, I'm planning to release something weekly. Here's a bit of a timeline:
0.5: Very basics. Do not expect it to be usable at this stage unless your familiar with how htdig works. (And if you get funny messages about how this is actually the skeleton module - I didn't do it, I swear <_< )
0.6: Some level of integration, the ability to administer rundig etc from the cms admin interface.
0.7. Ability to edit templates from the admin interface
0.8. Newbie-friendly configuration utility for htdig.conf
0.8.5 Support for Windows (actually, this might not be needed, but just to be careful)
0.9 Official Beta Release
0.5: Very basics. Do not expect it to be usable at this stage unless your familiar with how htdig works. (And if you get funny messages about how this is actually the skeleton module - I didn't do it, I swear <_< )
0.6: Some level of integration, the ability to administer rundig etc from the cms admin interface.
0.7. Ability to edit templates from the admin interface
0.8. Newbie-friendly configuration utility for htdig.conf
0.8.5 Support for Windows (actually, this might not be needed, but just to be careful)
0.9 Official Beta Release
