yesterday i found out that the browsers do not allow the colorpicker pop-up window to use a function in its parent window (parseColor) at antville.org and thus prevents the colorpicker from working.

i read across some google results regarding mozilla's security model for javascript and tried out

netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserRead UniversalBrowserWrite")

but without a signed script this does not seem to work. (a signed script cannot be the solution, can it?)

i assume the problem arises from the different domains of the site which is loading the colorpicker (xyz.antville.org) and the colorpicker scripts which are "located" at www.antville.org. reason: the colorpicker works locally and at helma.org.

i rather don't want to put the colorpicker scripts into the site's domain because this would mean redundant download of one and the same functions for each site.

does anyone have an idea or a solution for this?

please help, i need some advice from an expert how to do the rss output right, finally. i think i made quite a lot of moves regarding the encoding of description values (from no encoding over <-like encoding to CDATA sections).

now there's muttering about the CDATA again, which leads me back to <-like encoding or even way back to the beginning because "use of encoding within description elements considered harmful"...

so please, somebody who admires his own expertise in rss questions might state a last word now – and please not for the sake of any specific feedreader having troubles with rss – but for the sake of the rss specs and a format we still can use in the near future:

which way to do it right? (ie. if/how to encode html tags, if/how to encode special characters etc.)

ps. CDATA has to go definitely.

kann mir bitte jemand auf deutsch helfen ich finde mich nicht recht zurecht!

Danke

hi,

is it possible to use antvilleblogs upside down ->the latest articel at the bottom?

thank you for answers!

actually, i didn't want to implement the weblog on the frontpage feature. i was thinking about improving the static version.

but while thinking of it, i had the following idea: we use a regular weblog, say site.antville.org, which is displayed on the frontpage by using a yet to created macro. i.e. the page www.antville.org looks exactly like site.antville.org. the comments, image, file, stories and skin managers can remain on site.antville.org. i suppose this means there is no need to define all weblog functions for the main site.

(Test: Ä, ä, Ö, ö, Ü, ü) neuerdings werden Umlaute (in den Textfragmenten unter recently modified) nicht mehr korrekt dargestellt (HTML-Code stattdessen; der Fehler scheint inkonstant zu sein, mal geht es, mal nicht) - how come? what can I do? thx

i think we still have an encoding problem, haven't we?