The drupal site has been 'idle' for many months, without quite being
polished, due to a decision to focus efforts elsewhere (back when we were
pushing the demo out the door). The errors you saw were caused by a module
that was broken by the ISP's tightening security (generally a good thing),
and I've turned that module off, as we weren't really using it.

To fix up the site, we'd want to:
- Clean up some minor problems in the CSS (the layout stuff). The new site
layout is actually a bit tricky to code, but I am sure that we can either
fix whatever's going on or simplify the layout to eliminate the layout
error.
- Copy any new content from the old site(s) to the new site. This could
either be just the Wiki content, or the entire static site.
- Teach whoever will be updating the site how to edit content (i.e. click
the "create content" or "edit this page" buttons, and the process
thereafter).

All of the above are fairly easy. How do we make the decision to do it?

I'll go for David' bot killer for now. I believe I suggested some sort
of human authentication routine along those lines already. Thanks for
finally picking up on it. As to the Wiki, I'll be out of town 8/20-8/28 to
study wave action, beach structures and solar incidence in Kauai so someone
else will have to keep on an eye on it. I've been checking it daily since
the first bot attack.

> On Aug 19, 2004, at 11:13 AM, Popkin, Laird (WMG Corp) wrote:
> > easily make the Wiki pages visible to all visitors, and editable only
> > by approved authors.
>
> Yeah... that's the part that I don't like. I don't want a list of
> "approved" authors for a Wiki. What I suggested is strictly an
> anti-robot system, it doesn't judge authors per se. I guess if there's
> a really easy way to add -yourself- to the approved author list (under
> whatever pseudonym you want), it's not so bad.
>
> Btw. When I tried http://gyaku.pair.com/~vote/drupal/ just now, there
> are still a bunch of things that don't look right. There's a minor
> alignment problem in the red horizontal bar at top (it "jumps" halfway
> through, on Safari at least). And there's a slightly ugly white bar,
> or just gap at the top of the left navigation.
>
> But the main problem is that at the bottom of the page I see a whole
> bunch of error messages:
>
> warning: fopen(): URL file-access is disabled in the server
> configuration in /usr/www/users/vote/drupal/modules/cloud.module on
> line 82.
> warning: fopen(http://www.blackboxvoting.org/): failed to open stream:
> no suitable wrapper could be found in
> /usr/www/users/vote/drupal/modules/cloud.module on line 82.
> warning: fopen(): URL file-access is disabled in the server
> configuration in /usr/www/users/vote/drupal/modules/cloud.module on
> line 82.
> warning: fopen(http://blackboxvoting.com/): failed to open stream: no
> suitable wrapper could be found in
> /usr/www/users/vote/drupal/modules/cloud.module on line 82.
> warning: fopen(): URL file-access is disabled in the server
> configuration in /usr/www/users/vote/drupal/modules/cloud.module on
> line 82.
> warning: fopen(http://www.verifiedvoting.org/index.asp): failed to open
> stream: no suitable wrapper could be found in
> /usr/www/users/vote/drupal/modules/cloud.module on line 82.
>
> All of this suggests that this site is still "not ready for prime
> time." For a Wiki, a little glitchiness isn't the end of the world.
> But the main face of OVC shouldn't look so "beta."
>

==================================================================
= The content of this message, with the exception of any external
= quotations under fair use, are released to the Public Domain
==================================================================
Received on Tue Aug 31 23:17:17 2004