22
I added this code to the template "system_rss.html" to make RSS feeds 100% compatible with all aggregators:
Line 2 - after xml version:
Line 14 - after channel language:
I use the above smarty code because hardcoding the self-address of your rss feed (eg. "http://mydomain.org/backend.php") will break your feed in other modules that use backend.php to generate RSS feeds (namely wf-downloads).
Can these changes be added to a following release?
Line 2 - after xml version:
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
Line 14 - after channel language:
<atom:link href="<{$xoops_url}><{$smarty.server.REQUEST_URI}>" rel="self" type="application/rss+xml" />
I use the above smarty code because hardcoding the self-address of your rss feed (eg. "http://mydomain.org/backend.php") will break your feed in other modules that use backend.php to generate RSS feeds (namely wf-downloads).
Can these changes be added to a following release?
23
Le voilà. You got mail!
Hope you can add it in some (any
) future release. Until then I suppose it can be found on McDonalds Store.
Hope you can add it in some (any
) future release. Until then I suppose it can be found on McDonalds Store.
24
Hi McDonald!
Thanks again for a great module! I have written a plugin for the great whatsnew module from ohwada.
Can you give me your mail address via PM? I'll mail the file so that you can add it to some next release.
Thanks again for a great module! I have written a plugin for the great whatsnew module from ohwada.
Can you give me your mail address via PM? I'll mail the file so that you can add it to some next release.
25
I was also wondering if XOOPS search could be taught to ignore typo's like 'the cribsµ' instead of 'the cribs'. This typo is very common on azerty-keyboards (don't know 'bout qwerty). Could this be done?
26
@jeffgr
Simple! You can do this:
You have to change 'prefix' of course.
I tried the search patch and it's very promising. Too bad I had a problem with the page_nav not working. When I click 'next' when scrolling through module results, it will change the search numbers in front of the results (eg. 21-40) but not the search results themselves.
Switched back to old-school search
Simple! You can do this:
insert into prefix_config values (93, 0, 5, 'enable_deep_search', '_MD_AM_DODEEPSEARCH', '1', '_MD_AM_DODEEPSEARCHDSC', 'yesno', 'int', 0)
insert into prefix_config values (94, 0, 5, 'num_shallow_search', '_MD_AM_NUMINITSRCHRSLTS', '5', '_MD_AM_NUMINITSRCHRSLTSDSC', 'textbox', 'int', 1)
insert into prefix_config values (95, 0, 5, 'num_module_search', '_MD_AM_NUMMDLSRCHRESULTS', '20', '_MD_AM_NUMMDLSRCHRESULTSDSC', 'textbox', 'int', 2)
You have to change 'prefix' of course.
I tried the search patch and it's very promising. Too bad I had a problem with the page_nav not working. When I click 'next' when scrolling through module results, it will change the search numbers in front of the results (eg. 21-40) but not the search results themselves.
Switched back to old-school search
27
Thanks for the explanation phppp. This clears up a lot!
I like the new dynamism in XOOPS core development and I hope XOOPS Mexico & Brasil will be able to share their new code with you.
I regret the way this has sparked into a new feud. I would like for the rants made in the XOOPS section of the News module on xoops.org (eg. posts by XoopsCouncil & Foundation) to be moved to another section or to be removed altogether. This is highly unprofessional and scares off new users and developers!
In the future any disputes between Council, Foundation and Teams should be solved in a private forum.
I like the new dynamism in XOOPS core development and I hope XOOPS Mexico & Brasil will be able to share their new code with you.
I regret the way this has sparked into a new feud. I would like for the rants made in the XOOPS section of the News module on xoops.org (eg. posts by XoopsCouncil & Foundation) to be moved to another section or to be removed altogether. This is highly unprofessional and scares off new users and developers!
In the future any disputes between Council, Foundation and Teams should be solved in a private forum.
28
Quote:
Hi nachenko!
Could you post this bug-fixed version in the module repository? This way everyone can benefit of it.
Thanks for the tip btw!
nachenko wrote:
I use a search module developed by
Dan Musil and Jirka Vrba (http://www.qcm.cz)
It's just a modularized copy of the search engine, modified to use Smarty templates (oh, yes!), so you can tune looking and working without modyfing the core.
It's old, but still recommended. I think it' a good starting point for anyone that wants to improve the search engine. Instead of hacking the core, you just work on a module that can be removed at any time.
NOTICE: old version had a bug. I send them the fix, but don't know if they released a new version with the fix.
Hi nachenko!
Could you post this bug-fixed version in the module repository? This way everyone can benefit of it.
Thanks for the tip btw!
29
Hi everybody!
This may be a tad off-topic, but posting it here anyway.
I was wondering if somebody had hacked the search function to allow searching through synonyms or descriptions. Let me clarify with an example:
I type in 'restaurant', but I might also be interested in a 'tavern', 'cafe' or whatever. It would be nice if we were able to make a keyword list in XOOPS and make the search function display additional pages based on this list in the search results.
Has anyone done this? Is this possible? It's a bit like taxonomies-lite
This may be a tad off-topic, but posting it here anyway.
I was wondering if somebody had hacked the search function to allow searching through synonyms or descriptions. Let me clarify with an example:
I type in 'restaurant', but I might also be interested in a 'tavern', 'cafe' or whatever. It would be nice if we were able to make a keyword list in XOOPS and make the search function display additional pages based on this list in the search results.
Has anyone done this? Is this possible? It's a bit like taxonomies-lite
30
Quote:
You do not need the admin section for this! You can enable site-wide discussion easily through the discussion plugin.
Please visit the dokuwiki website for support on both the tag and discussion plugins.
I have no plans for a sitemap module plugin at this time.
nmshah wrote:
thamk you for your replies, i want to make the changes in admin as i want the discussion column by default. On going through the config options i saw what i needed, so is there anyother way to do so. and also is there a way to add the pages of dokuwiki in sitemap 1.30
You do not need the admin section for this! You can enable site-wide discussion easily through the discussion plugin.
Please visit the dokuwiki website for support on both the tag and discussion plugins.
I have no plans for a sitemap module plugin at this time.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|