Since I updated to core 2.4.1 and after an import from another TW I
get the following error when using the for each macro: URIError:
malformed URI sequence.
You can click the message box away without any problem.
I suspect that there is a tiddler with a poor title, how to debug
this???
> Since I updated to core 2.4.1 and after an import from another TW I > get the following error when using the for each macro: URIError: > malformed URI sequence.
I've had that recently, and it took me half a day to debug - turns out there was a tiddler* containing "malformed" wiki markup*, which caused this exception when being rendered. So if you open the imported tiddlers one after another, you should be able to identify the culprit.
> > Since I updated to core 2.4.1 and after an import from another TW I
> > get the following error when using the for each macro: URIError:
> > malformed URI sequence.
> I've had that recently, and it took me half a day to debug - turns out
> there was a tiddler* containing "malformed" wiki markup*, which caused
> this exception when being rendered.
> So if you open the imported tiddlers one after another, you should be
> able to identify the culprit.
I had the same problem with a @ in the title. It was causing ForEachTiddler to fail.
It would be nice to have a list of special characters that cause this kind of fault and a means by which to list them (without error) so one can rename them, alternatively debug tiddlywiki to to allow more characters in the title without error.
On Tue, Oct 7, 2008 at 18:30, okido <bkn...@gmail.com> wrote:
> Hi FND,
> I opened all tiddlers and found one that had an % in the title. > Problem solved.
> Thanks, Okido
> On 6 Oct, 16:44, FND <F...@gmx.net> wrote: > > > Since I updated to core 2.4.1 and after an import from another TW I > > > get the following error when using the for each macro: URIError: > > > malformed URI sequence.
> > I've had that recently, and it took me half a day to debug - turns out > > there was a tiddler* containing "malformed" wiki markup*, which caused > > this exception when being rendered. > > So if you open the imported tiddlers one after another, you should be > > able to identify the culprit.
> debug tiddlywiki to to allow more characters in the title without error
It's already on the list of things we need to look into. The more information we have (ideally, reproducible test cases), the easier it will be for us to identify the problem.
> It would be nice to have a list of special characters that cause this kind
> of fault
Indeed, such a list would be good.
> and a means by which to list them (without error) so one can rename
> alternatively debug tiddlywiki to to allow more characters in the
> title without error.
I used YourSearchPlugin to find such culprits. But any search plugin
would be able to.