Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Zope: Web

"Token 'ATOM' required, 'EOF' found" error in zopeorg

 

 

First page Previous page 1 2 Next page Last page  View All Zope web RSS feed   Index | Next | Previous | View Threaded


ausum_studio at hotmail

Dec 21, 2004, 2:05 PM

Post #1 of 29 (4085 views)
Permalink
"Token 'ATOM' required, 'EOF' found" error in zopeorg

Try to search for "Zope and" and you'll get this error:

Error Type
ParseError
Error Value
Token 'ATOM' required, 'EOF' found

Looks like a ZCTextIndex bug. Is it already filed? I tried to look for it at
the Collector, but I'm not sure it isn't there already.


Ausum
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


tim.one at comcast

Dec 21, 2004, 2:41 PM

Post #2 of 29 (4060 views)
Permalink
RE: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

[Ausum Studio]
> Try to search for "Zope and" and you'll get this error:
>
> Error Type
> ParseError
> Error Value Token 'ATOM' required, 'EOF' found
>
> Looks like a ZCTextIndex bug. Is it already filed? I tried to look for it
> at the Collector, but I'm not sure it isn't there already.

Well, it's an invalid search phrase, so I'm not sure what you'd like better.
"and" is a keyword, and requires an atom on both sides of it.

Trying searching for

and

on its own, or trying searching for

or

on its own, and you'll see similar errors. If you want to search for the
literal word "and", you need to quote it, like:

Zope "and"


_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Dec 22, 2004, 1:43 AM

Post #3 of 29 (4003 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Tim Peters wrote:

>>Looks like a ZCTextIndex bug. Is it already filed? I tried to look for it
>>at the Collector, but I'm not sure it isn't there already.
>
> Well, it's an invalid search phrase, so I'm not sure what you'd like better.
> "and" is a keyword, and requires an atom on both sides of it.

This has long been a bugbear of mine. Yes, it is an invalid search
phrase, but should end users really see exceptions raised because they
accidentally tried to use a piece of ZCTextIndex functionality that they
didn't even know existed?

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


michael at d2m

Dec 22, 2004, 2:21 AM

Post #4 of 29 (3982 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Ausum Studio wrote:
> Try to search for "Zope and" and you'll get this error:
>
> Error Type
> ParseError
> Error Value
> Token 'ATOM' required, 'EOF' found
>
> Looks like a ZCTextIndex bug. Is it already filed? I tried to look for it at
> the Collector, but I'm not sure it isn't there already.
>

A while ago we talked about changing zope.org search to
google search (as it is with python.org already).

For testing, I have changed the Zope.org searchresults-page and
added a link to Google site-search. This allows searching
Google with the same searchterm and comparing the results.

Michael

--
http://zope.org/Members/d2m

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


andrew at zope

Dec 22, 2004, 7:54 AM

Post #5 of 29 (3997 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Chris Withers wrote:
> Tim Peters wrote:
>
>>> Looks like a ZCTextIndex bug. Is it already filed? I tried to look
>>> for it
>>> at the Collector, but I'm not sure it isn't there already.
>>
>>
>> Well, it's an invalid search phrase, so I'm not sure what you'd like
>> better.
>> "and" is a keyword, and requires an atom on both sides of it.
>
>
> This has long been a bugbear of mine. Yes, it is an invalid search
> phrase, but should end users really see exceptions raised because they
> accidentally tried to use a piece of ZCTextIndex functionality that they
> didn't even know existed?
>
> cheers,
>
> Chris
>
You can catch this in a python script handler the searches go to.....
This is how I've managed it in the past.
Andrew

--
Zope Managed Hosting
Systems Administrator/Software Engineer
Zope Corporation
(540) 361-1700
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


jim at ibang

Dec 22, 2004, 8:09 AM

Post #6 of 29 (4051 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

On Dec 22, 2004, at 4:43 AM, Chris Withers wrote:
> This has long been a bugbear of mine. Yes, it is an invalid search
> phrase, but should end users really see exceptions raised because they
> accidentally tried to use a piece of ZCTextIndex functionality that
> they didn't even know existed?

It might be nice to trap this exception, and treat all words as if they
were quoted. So this:
Zope and

...becomes this:
"Zope" "and"

And, since we're messing with their search terms, maybe add a brief
note to the results page with examples of proper usage?

=jimA=

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
Jim Allman
Interrobang Digital Media
http://www.ibang.com/
(919) 649-5760

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


ausum_studio at hotmail

Dec 23, 2004, 10:20 AM

Post #7 of 29 (3994 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

A word of wisdom by GG:

"""
The "AND" operator is unnecessary -- we include all search terms by default.
"""

ZCTextIndex does the same AFAICK, the to-and-words-in-a-query thing.


Ausum



----- Original Message -----
From: "Andrew Sawyers" <andrew [at] zope>
To: "Chris Withers" <chris [at] simplistix>
Cc: "'Ausum Studio'" <ausum_studio [at] hotmail>; <zope-web [at] zope>
Sent: Wednesday, December 22, 2004 10:54 AM
Subject: Re: [ZWeb] "Token 'ATOM' required, 'EOF' found" error in zopeorg


> Chris Withers wrote:
> > Tim Peters wrote:
> >
> >>> Looks like a ZCTextIndex bug. Is it already filed? I tried to look
> >>> for it
> >>> at the Collector, but I'm not sure it isn't there already.
> >>
> >>
> >> Well, it's an invalid search phrase, so I'm not sure what you'd like
> >> better.
> >> "and" is a keyword, and requires an atom on both sides of it.
> >
> >
> > This has long been a bugbear of mine. Yes, it is an invalid search
> > phrase, but should end users really see exceptions raised because they
> > accidentally tried to use a piece of ZCTextIndex functionality that they
> > didn't even know existed?
> >
> > cheers,
> >
> > Chris
> >
> You can catch this in a python script handler the searches go to.....
> This is how I've managed it in the past.
> Andrew
>
> --
> Zope Managed Hosting
> Systems Administrator/Software Engineer
> Zope Corporation
> (540) 361-1700
> _______________________________________________
> Zope-web maillist - Zope-web [at] zope
> http://mail.zope.org/mailman/listinfo/zope-web
>
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 18, 2005, 1:53 PM

Post #8 of 29 (3955 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Andrew Sawyers wrote:

>> This has long been a bugbear of mine. Yes, it is an invalid search
>> phrase, but should end users really see exceptions raised because they
>> accidentally tried to use a piece of ZCTextIndex functionality that
>> they didn't even know existed?
>>
> You can catch this in a python script handler the searches go to.....
> This is how I've managed it in the past.
> Andrew

How? In most released versions of Zope, you can't import these
exceptions to catch them in untrusted code...

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


andrew at zope

Jan 18, 2005, 2:01 PM

Post #9 of 29 (4023 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Chris Withers wrote:
> Andrew Sawyers wrote:
>
>>> This has long been a bugbear of mine. Yes, it is an invalid search
>>> phrase, but should end users really see exceptions raised because
>>> they accidentally tried to use a piece of ZCTextIndex functionality
>>> that they didn't even know existed?
>>>
>> You can catch this in a python script handler the searches go to.....
>> This is how I've managed it in the past.
>> Andrew
>
>
> How? In most released versions of Zope, you can't import these
> exceptions to catch them in untrusted code...
>
> cheers,
>
> Chris
>
Not by carching an exception; by intercepting the search query and
looking for incorrect structure before passing it off to the catalog,
thus the 'handler the searches go to....' in the above.

Andrew

--
Zope Managed Hosting
Systems Administrator/Software Engineer
Zope Corporation
(540) 361-1700
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 19, 2005, 1:51 AM

Post #10 of 29 (3968 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Andrew Sawyers wrote:

> Not by carching an exception; by intercepting the search query and
> looking for incorrect structure before passing it off to the catalog,
> thus the 'handler the searches go to....' in the above.

Pre-parsing the query so the actual parser doesn't barf seems pretty
weird to me.

Still, I guess it's more likely than ever getting zope.org onto, say,
Zope 2.7.4, in which you CAN import the requisite exceptions.

But I still think there should be a knob to tweak on ZCTextIndex to say
"don't raise silyl exceptions"

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


ausum_studio at hotmail

Jan 19, 2005, 5:15 AM

Post #11 of 29 (3964 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Pre-parsing the query seems currently a must, as a matter of fact, if you
don't want to provide your users (who don't know anything about incorrect
queries) this sensation of being at an unfinished site that they get when
any error message comes up.

That was what lead me to believe that there was a bug in ZCTextIndex, that
Zope.org just got used to live with.


Ausum


----- Original Message -----
From: "Chris Withers" <chris [at] simplistix>
> Andrew Sawyers wrote:
>
> > Not by carching an exception; by intercepting the search query and
> > looking for incorrect structure before passing it off to the catalog,
> > thus the 'handler the searches go to....' in the above.
>
> Pre-parsing the query so the actual parser doesn't barf seems pretty
> weird to me.
>
(...)
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


andrew at zope

Jan 19, 2005, 7:30 AM

Post #12 of 29 (3978 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Chris Withers wrote:
> Andrew Sawyers wrote:
>
>> Not by carching an exception; by intercepting the search query and
>> looking for incorrect structure before passing it off to the catalog,
>> thus the 'handler the searches go to....' in the above.
>
>
> Pre-parsing the query so the actual parser doesn't barf seems pretty
> weird to me.
I never said I liked it; When I originally came across this situation, I
expected the catalog code to be smarter. I got shot down too :)
>
> Still, I guess it's more likely than ever getting zope.org onto, say,
> Zope 2.7.4, in which you CAN import the requisite exceptions.
Why?
>
> But I still think there should be a knob to tweak on ZCTextIndex to say
> "don't raise silyl exceptions"
You're asking for DWIM?
>
> cheers,
>
> Chris
>
A

--
Zope Managed Hosting
Systems Administrator/Software Engineer
Zope Corporation
(540) 361-1700
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 20, 2005, 2:11 AM

Post #13 of 29 (3973 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Ausum Studio wrote:

> Pre-parsing the query seems currently a must, as a matter of fact, if you
> don't want to provide your users (who don't know anything about incorrect
> queries) this sensation of being at an unfinished site that they get when
> any error message comes up.

Why?

> That was what lead me to believe that there was a bug in ZCTextIndex, that
> Zope.org just got used to live with.

It's not really a bug, just a missing feature...

http://collector.zope.org/Zope/1675

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 20, 2005, 2:12 AM

Post #14 of 29 (3968 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Andrew Sawyers wrote:

>> But I still think there should be a knob to tweak on ZCTextIndex to
>> say "don't raise silyl exceptions"
>
> You're asking for DWIM?

I don't think a checkbox that says "return zero results if a query parse
error occurs" is DWIM.

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


andrew at zope

Jan 20, 2005, 9:16 AM

Post #15 of 29 (3969 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Chris Withers wrote:
> Andrew Sawyers wrote:
>
>>> But I still think there should be a knob to tweak on ZCTextIndex to
>>> say "don't raise silyl exceptions"
>>
>>
>> You're asking for DWIM?
>
>
> I don't think a checkbox that says "return zero results if a query parse
> error occurs" is DWIM.
>
> cheers,
>
> Chris
>
No, but that's not what you said; you said don't raise silly exceptions.
:) There's a difference' silly != 0.

Returning 0 results when there's a query structure error is worse then
returning an error. You're just masking an end users mis-use of the
system; at least errors might generate feedback. No results would
likely lead one to belive the site has a horrible search backend or no
content. :)

In the cases where I've had to catch the query prior to passing it to
the catalog, one has the opportunity to inform the user.
A

--
Zope Managed Hosting
Systems Administrator/Software Engineer
Zope Corporation
(540) 361-1700
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 21, 2005, 1:51 AM

Post #16 of 29 (3970 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Andrew Sawyers wrote:
> In the cases where I've had to catch the query prior to passing it to
> the catalog, one has the opportunity to inform the user.

Well, if we could get zope.org onto 2.7.4 or some such, you can just
catch the requisite exceptions in the python script that calls ZCatalog.

Still, I've never seen Google return a "we're sorry, you didn't manage
to guess our arcane query structure syntax" message...

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


andrew at zope

Jan 21, 2005, 6:47 AM

Post #17 of 29 (3983 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Chris Withers wrote:
> Andrew Sawyers wrote:
>
>> In the cases where I've had to catch the query prior to passing it to
>> the catalog, one has the opportunity to inform the user.
>
>
> Well, if we could get zope.org onto 2.7.4 or some such, you can just
> catch the requisite exceptions in the python script that calls ZCatalog.
Well, I was talking to Jens day before yesterday, I'm sure there's
several capable people who'd be more interested in helping with zope.org
if it was just a simple CMF site with skin to make it pretty. Maybe
it's time for us to reexamine things? None of us have the desire or
time to sludge through what's there now. At one point, Jens and I had a
completely migrated zope.org (the old one) onto a straight CMF based
site. Now who knows what's there; it's not even on a CMS anyone at ZC
uses on a daily basis (i.e. it's based on Plone which adds several
layers of unecessary indirection) and we don't have people who are
familiar with it chomping at the bit to help us out. This is a huge
roadblock IMNSHO.
>
> Still, I've never seen Google return a "we're sorry, you didn't manage
> to guess our arcane query structure syntax" message..
True, true, true
.
>
> Chris
>
A

--
Zope Managed Hosting
Systems Administrator/Software Engineer
Zope Corporation
(540) 361-1700
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


jens at dataflake

Jan 21, 2005, 9:03 AM

Post #18 of 29 (4038 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

On Jan 21, 2005, at 15:47, Andrew Sawyers wrote:

> Chris Withers wrote:
>> Andrew Sawyers wrote:
>>> In the cases where I've had to catch the query prior to passing it
>>> to the catalog, one has the opportunity to inform the user.
>> Well, if we could get zope.org onto 2.7.4 or some such, you can just
>> catch the requisite exceptions in the python script that calls
>> ZCatalog.
> Well, I was talking to Jens day before yesterday, I'm sure there's
> several capable people who'd be more interested in helping with
> zope.org if it was just a simple CMF site with skin to make it pretty.
> Maybe it's time for us to reexamine things? None of us have the
> desire or time to sludge through what's there now. At one point, Jens
> and I had a completely migrated zope.org (the old one) onto a straight
> CMF based site. Now who knows what's there; it's not even on a CMS
> anyone at ZC uses on a daily basis (i.e. it's based on Plone which
> adds several layers of unecessary indirection) and we don't have
> people who are familiar with it chomping at the bit to help us out.
> This is a huge roadblock IMNSHO.

Amen to that.

It's not just the fact that there is other software that adds
unnecessary layers and that no one at ZC uses, unfortunately those
layers are also badly done and badly broken in way too many places.

The current maintenance strategy is based on the hope that a lot of
fixing will some day make the software do better, but IMNSHO I cannot
see that succeeding. There are too many problems and too many
fundamental flaws in the design and implementation.

While speaking with Andrew I have volunteered to help create a saner
basis for zope.org. It is unlikely that ZC is willing to spearhead such
an effort (no time, no willingness to throw good money after bad, etc),
which I understand. The biggest problem that creates is a leadership
vacuum and any efforts would soon peter out in a flood of discussions
from a whole lot of more or less well-meaning people. It cannot work
without a tightly organized *small* group of developers that can work
without interference from the community at large. That's how things get
done.

jens

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


simon at joyful

Jan 21, 2005, 1:09 PM

Post #19 of 29 (3960 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Absolutely. It needs to be simplified and IMHO to run standard software
that the community knows well - dogfood that we eat etc. There aren't
the resources to maintain so much custom code for just one site.

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


simon at joyful

Jan 21, 2005, 1:16 PM

Post #20 of 29 (3972 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Simon Michael wrote:
> Absolutely. It needs to be simplified and IMHO to run standard software
> that the community knows well - dogfood that we eat etc. There aren't
> the resources to maintain so much custom code for just one site.

PS I'm don't mean to argue for or against plone here, just non-standard
stuff.

Arguably a standard plone site could be less "custom" and familiar to
potential maintainers people, though heavier, than a cmf site with
whatever tweaks that would need. I don't know.

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


robert at redcor

Jan 21, 2005, 11:53 PM

Post #21 of 29 (3969 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Jens Vagelpohl wrote:

> On Jan 21, 2005, at 15:47, Andrew Sawyers wrote:
>
>> Chris Withers wrote:
>>
>>> Andrew Sawyers wrote:
>>>
>>>> In the cases where I've had to catch the query prior to passing it
>>>> to the catalog, one has the opportunity to inform the user.
>>>
>>> Well, if we could get zope.org onto 2.7.4 or some such, you can just
>>> catch the requisite exceptions in the python script that calls
>>> ZCatalog.
>>
>> Well, I was talking to Jens day before yesterday, I'm sure there's
>> several capable people who'd be more interested in helping with
>> zope.org if it was just a simple CMF site with skin to make it
>> pretty. Maybe it's time for us to reexamine things? None of us have
>> the desire or time to sludge through what's there now. At one point,
>> Jens and I had a completely migrated zope.org (the old one) onto a
>> straight CMF based site. Now who knows what's there; it's not even
>> on a CMS anyone at ZC uses on a daily basis (i.e. it's based on Plone
>> which adds several layers of unecessary indirection) and we don't
>> have people who are familiar with it chomping at the bit to help us
>> out. This is a huge roadblock IMNSHO.
>
>
> Amen to that.
>
> It's not just the fact that there is other software that adds
> unnecessary layers and that no one at ZC uses, unfortunately those
> layers are also badly done and badly broken in way too many places.
>
> The current maintenance strategy is based on the hope that a lot of
> fixing will some day make the software do better, but IMNSHO I cannot
> see that succeeding. There are too many problems and too many
> fundamental flaws in the design and implementation.
>
> While speaking with Andrew I have volunteered to help create a saner
> basis for zope.org. It is unlikely that ZC is willing to spearhead
> such an effort (no time, no willingness to throw good money after bad,
> etc), which I understand. The biggest problem that creates is a
> leadership vacuum and any efforts would soon peter out in a flood of
> discussions from a whole lot of more or less well-meaning people. It
> cannot work without a tightly organized *small* group of developers
> that can work without interference from the community at large. That's
> how things get done.
>
> jens
>
> _______________________________________________
> Zope-web maillist - Zope-web [at] zope
> http://mail.zope.org/mailman/listinfo/zope-web
>
If anybody does take the lead, we at redCOR (and not only me) will be
happy to help on implementig.
Robert
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


mark at zopemag

Jan 22, 2005, 10:29 AM

Post #22 of 29 (4018 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Hi,

I am
On Jan 21, 2005, at 6:03 PM, Jens Vagelpohl wrote:

> On Jan 21, 2005, at 15:47, Andrew Sawyers wrote:
>
>>
>
> Amen to that.
>
> It's not just the fact that there is other software that adds
> unnecessary layers and that no one at ZC uses, unfortunately those
> layers are also badly done and badly broken in way too many places.
>
> The current maintenance strategy is based on the hope that a lot of
> fixing will some day make the software do better, but IMNSHO I cannot
> see that succeeding. There are too many problems and too many
> fundamental flaws in the design and implementation.
>
> While speaking with Andrew I have volunteered to help create a saner
> basis for zope.org. It is unlikely that ZC is willing to spearhead
> such an effort (no time, no willingness to throw good money after bad,
> etc), which I understand. The biggest problem that creates is a
> leadership vacuum and any efforts would soon peter out in a flood of
> discussions from a whole lot of more or less well-meaning people. It
> cannot work without a tightly organized *small* group of developers
> that can work without interference from the community at large. That's
> how things get done.

Am in agreement to that but to a point. What software runs in the
backgroun / is easier to maintain I leave to the people who actually
have to maintain / work with the code.

But how would you approach this? What would happen to custom things
that are on the site. Could this for example impact the
two to three link items we need for the doc section.

If its only two people who decide what and how a new zope.org is set up
than that would rub many the wrong way.
Especially when their is not just interest but a commitment to help out.

Cheers,

Mark

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


chris at simplistix

Jan 24, 2005, 2:12 AM

Post #23 of 29 (4009 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

Mark Pratt wrote:
> But how would you approach this? What would happen to custom things that
> are on the site. Could this for example impact the
> two to three link items we need for the doc section.

The point is, there are currently zero people in a position where they
feel comfortable to do these things. That's largely due to what's there
already.

There's also an element of presenting a solution to a problem you have
when you may not be the best person to judge what the correct solution is.

By that, I mean if you were in a position to judge, you would have
implemented those components already, as it is, I'd hypothesise that you
have a problem and think you've found the right solution. However, what
might work better is to say "hi, we in the docs group have found this
problem, what should we do to solve it". You may find you don't even
need any new components ;-)

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


sidnei at awkly

Jan 24, 2005, 3:16 AM

Post #24 of 29 (4036 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

On Fri, Jan 21, 2005 at 09:47:37AM -0500, Andrew Sawyers wrote:
| Well, I was talking to Jens day before yesterday, I'm sure there's
| several capable people who'd be more interested in helping with zope.org
| if it was just a simple CMF site with skin to make it pretty.
|
| Maybe it's time for us to reexamine things? None of us have the
| desire or time to sludge through what's there now. At one point,
| Jens and I had a completely migrated zope.org (the old one) onto a
| straight CMF based site. Now who knows what's there; it's not even
| on a CMS anyone at ZC uses on a daily basis (i.e. it's based on
| Plone which adds several layers of unecessary indirection) and we
| don't have people who are familiar with it chomping at the bit to
| help us out. This is a huge roadblock IMNSHO.

I think I'm allowed to give my input here, being the original person
in charge of migrating the old site to the current one.

If you guys think doing it all again will solve all the problems by
miracle, sorry but you are completely wrong.

Saying that the problem is in Plone, or that removing Plone will fix
the current problems is just pointing fingers elsewhere than the
problem is.

All the complaints I've read so far in this list are related to:

1. Workflows
2. ZCatalog
3. Skin

Plone, as you know, apart from CMFFormController is barely a skin. All
the content in current Zope.org is CMFDefault's. Documents, News
Items, etc. What is not CMFCore is some other custom product. If I
recall, the workflow is not Plone's standard or even CMF's standard
but a custom one.

At one point during migration, I thought people would start
complaining that Plone was getting into their ways and I've tried to
make a pure CMF skin. The result is that it worked pretty flawlessly
except for one or two scripts that would have to be copied to this
skin.

I warn you, don't be too ambitious. You *will* end up with another
dead-on-water Zope.org migration plan. If you think Plone is the
problem, the solution is simple:

1. Set the skin to CMFDefault's standard skin
2. Replace the custom workflow to CMFDefault's standard one, or fix
the existing one.
3. Test every common operation, like adding and editing content for
all content types as a 'Member'.
4. Adjust the skin to look like the current one.

That done, you will very likely have accomplished your goal with
minimum effort and everyone will be happy.

Doing those steps you will have removed 99% of Plone's functionality
within the site, pending removal of the software itself and persistent
objects on the database. And you have no excuse on saying that 'doing
it all from scratch' is better or easier solution than this.

--
Sidnei da Silva <sidnei [at] awkly>
http://awkly.org - dreamcatching :: making your dreams come true
http://www.enfoldsystems.com
http://plone.org/about/team#dreamcatcher

Se o filme fosse gaścho...

Uma Linda Mulher -- Uma Chinoca Buenacha
_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web


jens at dataflake

Jan 24, 2005, 3:38 AM

Post #25 of 29 (3965 views)
Permalink
Re: "Token 'ATOM' required, 'EOF' found" error in zopeorg [In reply to]

On Jan 24, 2005, at 12:16, Sidnei da Silva wrote:
> Doing those steps you will have removed 99% of Plone's functionality
> within the site, pending removal of the software itself and persistent
> objects on the database. And you have no excuse on saying that 'doing
> it all from scratch' is better or easier solution than this.

Having had the "pleasure" of trying to make the original implementation
work I fully agree that Plone by itself is probably not the problem.
The problems are...

- half-hearted "integration" of the Plone components (it is more or
less slapped on)

- faulty migration process that left a large part of the content either
broken or not integrated (HowTos for example)

- badly implemented migration process that migrated within the same
ZODB with the result that the ZODB itself is damaged (you should seee
those ZEO server logs, they are scary) and all the old content and
software is still left in there with everyone too scared to try and
remove it for fear of hidden dependencies.

Removing Plone would not solve much. I'm sorry, this just is *not* a
viable foundation to work with, period. What we have now is duct tape
and bailing wire.

jens

---------------
Jens Vagelpohl jens [at] zetwork
Zetwork GmbH http://www.zetwork.com/

_______________________________________________
Zope-web maillist - Zope-web [at] zope
http://mail.zope.org/mailman/listinfo/zope-web

First page Previous page 1 2 Next page Last page  View All Zope web RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.