OK, I just did some click exploring and I think I reproduced your error. 
I think you clicked on the Project page batcher (the alphabet) after you'd logged in. Nifty. I never do that. 
That's a good catch. Thank you. 

I think if you keep logging out, going to the projects page, logging in, and hit the Projects page batcher, the error goes away. 
Maybe its something happening with a new session?
Still, it's a click trail I never thought of, so I'll have to get it sorted. 

Thanks, 
Chris 


On May 2, 2014, at 12:29 PM, tim Rowledge <tim at rowledge.org> wrote:

> 
> On 02-05-2014, at 7:24 AM, Chris Cunnington <brasspen at gmail.com> wrote:
> 
>> http://oopfile.com
> 
> and sadly, in the ‘oops’ file, I got this error page when attempting to click one of the letters in the ‘packages’ page. 
> http://box4.squeak.org:9971/seaside/smserver?_s=ihZFaoLtWqDwHaLE&_k=pNNinKg6&11
> (which, in case that isn’t a stable page link, read in part as -
> Seaside Walkback
> 
> WAComponentsNotFoundError: Components not found while processing callbacks: {a WAAlphabeticBatchedList}
> 
> Debug Full Stack
> 
> Possible Causes
> 
> 	• you do not implement #children correctly
> 	• you do not backtrack #children correctly
> 	• you do not implement #states correctly
> Stack Trace
> 
> 	• thisContext
> WARenderContinuation>>componentsNotFound:
> self
> a WARenderContinuation
> aCollection
> {a WAAlphabeticBatchedList}
> 	• thisContext
> WARenderContinuation>>unprocessedCallbacks:
> self
> a WARenderContinuation
> aCollection
> {a WAActionCallback}
> owners
> {a WAAlphabeticBatchedList}
> 	• thisContext
> WARenderContinuation>>processCallbacks:
> self
> a WARenderContinuation
> aRequest
> a WARequest GET /seaside/smserver
> lastPosition
> 0
> callbackStream
> a WACallbackStream
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Base 8 is just like base 10, if you are missing two fingers.
> 
> 
>