Hey, your menu looks great, but how is it done?

Do you add something to the metafooter? Or to the Index.php or mainfile.php?

Thanks,
Harry

I like the Coolmenu's a lot and am looking to integrate them into some PHP content system. Hopefully Xoops, if they fix the cookie problems


<small>[ Edited by topoftheworld on 2002/3/11 10:24:06 ]</small>

Tnx This really helps a lot. Could this be integrated into a new release of xoops?

Herko

Please take a look at www.geigant.de. I just integrated the Coolmenu from www.dhtmlcentral.com in my theme.php. Its hand-made, but it is functionable. Perhaps this will help you ..

Hi,

Xoops rules, but since it's in active development, I'd like to add a request of my own.

I want to make a distinction between information blocks and navigation blocks. Now these two are intertwined quite randomly and this doesn't make for a good site navigation, or at least of a decent control over it.

I'd like to be able to build a windows-style pulldown navigation menu. And I'd like it to be horizontally, placed at the top (just below the header) and/or at the footer of my page. It will only show those modules which I selected for this menu, and only the top levels of those (ie. news, and not news, submit news and archive). On a mouseover it will show (if any) underlaying pages (ie. submit news and archive). Like I said, only those modules that I selected for this (ie. not stats and partner sites).

Any ideas on how to do this??

Herko

Ok... found the problem.

Those online checkers dont like the closing tag.
They like it:
<meta name="keywords" content="hello, there">

They dont like it:
<meta name="keywords" content="hello, there" />

But just check W3's xhtml checker:http://validator.w3.org/

Example 1 is invalid, because all tags must be closed in XHTML. I think those online checkers are simply not up to date.

So, if anyone knows better than me... close meta tags, or dont close them?

BTW: I just checked XOOPS original header.php, and XOOPS originally closes meta tags too.

Also, Keyword injection, shuffle, & user agent discrimination is done Just need to fix non english chars, and add a keyword limit. And send me your common words :o)

<small>[ Edited by Half-Dead on 2002/3/1 12:06:54 ]</small>

Hmmmm effectively wierd...just tested a few online checkers and they all seemed to fail

AddWeb PRO extracts the proper keywords when i sik it on my site tho.....

I use XHTML 1.0 headers, and format in function of XHTML.

all tags lowercase, all propreties lowercase, tags with no closing tags terminated with />

<META NAME="Something" CONTENT="Whatever">
is invalid xhtml

<meta name="Something" content="Whatever" />
is valid xhtml


If someone finds the prob, lemme know!

I wonder if Search Engines can read this keywords.
I usually test my pages with "www.abondance.com".
With the "original" hack, it used to work. With the new ones it answers "no description, no keywords", even if I can see them in the source code...

User agent discrimination will be in the next one, i'll also try to fix the latin character probs

I took a look at some spider codes here.

And a few other ideas i got is:
Keyword injection: words you always want
Keyword shuffling
and maybe keyword limitation (since usually engines want no more than 20-30 keywords.).

If anybody using this wants to help....PM me your list of common words

Maybe didn't make myself clear. I'm not against cloaking. It is as I said very very useful. Just don't get caught thats all.

Also, I would still like to run the script in this hack even when users view the page as the changes to the title tag are the most important part of the hack. Let me explain; XOOPS normally displays the same title for every single page. However even if I get a page on a keyword into a good SE ranking, it could fail to deliver decent traffic because the search results from some SE use the title and description tags off your page as the results text. Currently these would describe the general theme of the site that you keyed in to admin/preferences. But if the keyword is more exact then you would want the title and discription to be more exact and so the hack become useful in changing the title. You would still want the same title to apear on the browser when the visitor arrived so maybe that part of the hack should remain.

If you really want to save on server load, you could miss out the keyword creation part completely. Only the smaller, or older SE's still use metakeywords in ranking. Instead they parse the real text of your page the same way that your script does and decide on there own keywords to use. So if you missed all the metakeywords out and just stuck with title and description few SE's would notice (and any that did would not be worth bothering about)

The word Cloak comes from Star Trek where the Klingons were capable of "cloaking" their ships invisible

Hehehe
http://www.dictionary.com/search?q=cloak

As for your two pages, they seem to encourage it.
Also XOOPS and many other sites already by default, forge the headers to report fake time of creation/modification times... so no 2 times you load the page will give identical results: Which means your current XOOPS site with or without this hack will fail the bitwise test anyways.

Not to mention pages with hit counters, javascript, external headlines..etc etc.

So no, i dont see where it would be bad. Keywords are meant for search engines not for users anyways. And if you can cut down the extractors cpu/mysql overhead by 99% by simply checking user agents...why not

Especially usefull for very active sites, since currently keywords are "always" exctracted, even if your normal user couldnt care less bout them.

Also the extracted words ARE relevant to the page being accessed, since they are directly compiled off the page's contents, so there's not even the factor of deception.


But thanks for your concern