/language/english/search.php

Ok, got this working with a bit of javascript.
Check http://www.zoologia.bio.br/dicts.html.
Feel free to combine those forms, make'em pretty, etc.
My part of the job is being released to the Public Domain and I'm not liable for copyright violations or any kind of damage or mass destruction resulting from the use of this code

Now...
I guess this could be done very quickly in PHP (perhaps with XOOPSForm ) so that people with javascript off (do they still make those?) could use the service.

Perhaps this could result in a nice module:
A "Search" block, a stats one, and an admin interface with blacklisted words and stats info. Ideally, tons of search engines/databases/dictionaries should be included, with all sorts of search-engine-specific functions, and the admin would set which ones are available (user options to search using more than one would be nice). An interface to add your own search engines would be cool, but would have to be very foolproof.
The module could count queries (like in MyLinks visit.php) and have statistics of the most popular words, most searchy users , preferred engines, etc. Oh, and if there's a way to include referrer info in the queries*, people searching from your site would be spreading your url on referrer lists

*Just tried it... how about sending searches like
Quote:?
I know I would spot this kind of thing on my server logs

Well, although it's not actually what you asked for...
You could use a custom block with a form that has a text field (tf) and a submit button. Set form action to Quote: (not sure about sintax, probably needs javascript or php, but you get the idea).
You'd need to adapt your code to solve "word word" queries (usually sent as word+word).
Lots of different resources can be accessed this way:
Quote:
I believe you shouldn't have any kind of copyright issues using their content this way.

[edit]
I guess it'll be easier to put this stuff in a block than it was to get this post to display properly [/edit]

Same here, but the feed is there, it just won't appear inside XOOPS.
I can see the raw RSS but Headlines module wont render it in
http://news.bbc.co.uk/rss/newsonline_world_edition/science/nature/rss091.xml and
http://bnhm.berkeley.museum/rss/BNHM.xml

BTW, I've just made the RSS url field larger and if anyone have to do this, here's the trick:
First thing to do is change the field type in MySQL: it's set as VARCHAR(255) (255 characters) and you should set it to TEXT, which allows 65535 chars (unfortunatelly, there's no intermediate value).

Then you have to change two module's files:
Open /modules/xoopsheadline/admin/index.php and find and replace
Quote: (which appears, and has to be replaced, twice) with
Quote:, XYZ being the new size in bytes for your RSS url field.
In /modules/xoopsheadline/class/headline.php, find
Quote: and replace "255" with the same value used before. This might be handy if you want to display customized Amazon RSS feeds

The best way to do a simple redirect, IMHO, is to put an index.php file in your base directory with Quote:You might want to add the "Permanent redirect" code too:
Or you might simply set News as your start module

Actually read your error messages and security advisories before contacting developers about (inexistent) bugs

Quote:
TINYTEXT == 257 bytes
TEXT == 65538 bytes (64KB)
MEDIUMTEXT == 16777219 bytes (16MB!)
LONGTEXT == 4294967300 bytes (4GB!!!)
So... hmmm... TEXT is way too big, MEDIUMTEXT makes no sense at all. Perhaps a nice way to avoid nasty things (like someone using their 64KB to store random data instead of a sig) would be retrieving the sig with a SUBSTRING query, so that the admin can have a granular control of the amount of data retrieved (also, limiting the post operation seems worthy). I'd say we're talking about a max of 500 - 2k bytes here, right?

* A block with "Next X events", titles only

* RSS feed of the content of the "Next X events" block (so other sites can display it)
* Count down block also exporting RSS

* "This day in history": Examples (1) (2) (3). Not sure about the best way to implement this... perhaps a default external link to empty days? Or better, each day could have "events" and "facts" or "info", i.e., things that will not happen but that are related to that day. Filters like those for events categories would be great (say someone wants to see all holidays or all curious facts).

* A simple way to add multiple events (or "infos"), like importing from a text file. Anything that would allow us to submit lots of different info would be great, just like it would for lots of modules (like Links or Downloads).

Herko you make me soooo happy
I'll contact him, last I recall I was lost inside a template file

Slowly, slowly... Ok, this is ugly and very very crude, but I can't do better (yet?)... hopefully someone with the skills will get interested

In the XooPSHeadline .sql file, I added Quote:
Inside class XoopsheadlineHeadline, function XoopsheadlineHeadline() Quote:
Added a "var $_arch;" in class XoopsHeadlineRenderer and a "$this->_arch = $items;" in it's function renderFeed. Down there, I added a Quote: to retrieve just the items for a channel. Now I'll try to figure out how to get $_arch appended to the "headline_arch" field, then what is needed to make it searchable, then... hmmm... parsing headline_arch to display. Oh, and I have to figure out when or where getArch() is called. What a mess