Eric's AutoTagger - problem with using aliases

[HansBKK]

Looks like an excellent tool for someone (ab)using tags as much as I do.

However it seems to break my TWs as soon as I try to use the Alias feature - which unfortunately is specifically what drove me to check it out.

All the other features seem to work OK, but as soon as I've created a tiddler matching the name enabled in the Alias configuration box, I'm unable to save any edits on any tiddlers - clicking Done does absolutely nothing. Disable the Alias feature or delete the TagAliases tiddler and everything goes back to being OK.

I'm using a latest-release MPTW - just tried on on vanilla TW no issue - any known conflcts with something taggly?

[HansBKK]

OK, I've rebuilt a new TW from scratch to get away from MPTW (TWT-Executive, very nice navigation tools there BTW).

But now AutoTaggerPlugin doesn't work there either, exactly the same symptoms!

So the conflict is obviously not with TagglyTagging.

An additional note - when I have tiddlers open for editing and go to refresh the page, I usually get a warning, but with AutoTagger's alias feature enabled and an TagAliases tiddler in place, not only does the "Done" button not save, but there isn't any warning - so it seems the "dirty" mechanism isn't working??

Any help in troubleshooting this - or an alternative to AutoTagger for the "tag alias" functionality - would be greatly appreciated.

[Eric Shulman]

> But now AutoTaggerPlugin doesn't work there either, exactly the same
> symptoms!

> Any help in troubleshooting this - or an alternative to AutoTagger for the
> "tag alias" functionality - would be greatly appreciated.

When "done" fails, it's because a 'fatal' error occurs during the
handling. If your browser has a developer debugging tool (i.e.,
Firebug for FireFox), you might be able to get some details about the
specific error that occurs. That would give me some idea where to
look in my code for possible causes.

In addition, if you can create a "Minimal Test Case" (MTC) document,
and post it somewhere online, I can take a look to try and locate the
culprit. An MTC starts with an *empty* TW document to which you apply
only the absolute minimum number of customizations and plugins, one at
a time, until the error condition is reproduced.

The resulting document makes it easier to isolate, diagnose and debug
specific causes by eliminating any extra handling and processing
overhead associated with other, non-essential customizations and
plugins. In fact, because the process of creating an MTC can isolate
the cause to a single change, you may even end up debugging the
problem yourself or even determine a work-around that avoids the
problem entirely!

The MTC also provides a reliable test case for me to verify any
potential solution *prior* to publishing changes to plugins. If a fix
is applied and the problem vanishes, then all is good and the update
can be posted online for people to import/install in their own
documents.

enjoy,
-e

[HansBKK]

I've got Firebug, but I've only used it for html/css devwork, didn't even know it did javascript, about which I (obviously) have not a clue. If you could give me a hint on what to do - how to generate a "debug log" or something? - I'd be more than happy to try it and post results back.

Re creating an MTC, ouch, that would be quite a project in and of itself - my starting ponit was TWT-treeview (Executive), quite a big cahuna on its own, and then I've added quite a few plugins since then. But I'll add the project to my list!

In the meantime, here's a list of enabled plugins - keeping in mind something in MPTW was also interfering - maybe something will jump out at you?

AttachFilePlugin
AttachFilePluginFormatters
AutoTaggerPlugin
ChangeSaveLabelMacro
CheckboxPlugin
CollapseTiddlersPlugin
ConfigTweaks
ConfirmSavePlugin
Cookie plugin
CookieJar
CookieManagerPlugin
CookieSaverPlugin
DeprecatedFunctionsPlugin
DisableWikiLinksPlugin
DoBackupMacro
ExportTiddlersPlugin
ForEachTiddlerPlugin
FullScreenPlugin
GotoPlugin
HTMLFormattingPlugin
ImportTiddlersPlugin
InlineJavascriptPlugin
IntelliTaggerPlugin
LessBackupsPlugin
LoadRemoteFileThroughProxy
LoadTiddlersPlugin
MatchTagsPlugin
MonkeyTaggerMacro
NestedSlidersPlugin
NewHerePlugin
PasswordOptionsPlugin
PrettyDatesPlugin
Publish Macro
QuickEditPlugin
QuoteOfTheDayPlugin
RearrangeTiddlersPlugin
RelatedTiddlersPlugin
RenameTagsPlugin
SaveAsPlugin
SaveCloseTiddlerPlugin
SearchOptionsPlugin
SetUserNamePlugin
SinglePageModePlugin
SwitchThemePluginMG
TaggerPlugin
TiddlerTweakerPlugin
TiddlersBarPluginMG
TreeviewPluginPlugin.24
TspotSetupPlugin
TwHelpSearchPlugin
UnsavedChangesPlugin
UploadPlugin
editA


Otherwise, worst case I'll continue without the tag alias feature, not quite a showstopper ATM. Thanks again for all your help.

[Paul]

On 6/21/2011 10:14 PM, HansBKK wrote:

I've got Firebug, but I've only used it for html/css devwork, didn't even know it did javascript, about which I (obviously) have not a clue. If you could give me a hint on what to do - how to generate a "debug log" or something?

I second HansBKK's comment.  I have Firebug but have never used it with javascript.  I'd appreciate a HowTo on the subject if anyone is willing to take the time.

[PMario]

On Jun 22, 7:14 am, HansBKK <hans...@gmail.com> wrote:
> I've got Firebug, but I've only used it for html/css devwork, didn't even
> know it did javascript, about which I (obviously) have not a clue. If you
> could give me a hint on what to do - how to generate a "debug log" or
> something? - I'd be more than happy to try it and post results back.

Hans, you could open/activate firebug. so you see the "console" tab.
Then reload you TW. .. firebug will be propperly initialized then.
Try to create the error state, and have a look at the console tab.
If you get a red error info post it. All of it. It may give Eric some
hints.

hope this helps
-m

[HansBKK]

Eric,

Sorry it took me so long to get to creating the minimal test case, I thought it would be such a huge project I put it off.

However it seems that the problem isn't with interaction with other plugins as I assumed.

Plain TW 2.62, no other plugins.

Import AutoTaggerPlugin and tag it systemConfig.

A - Create tiddler called AutoTaggerAliases

B - Enter the string to match above and check the option: "replace 'aliased' tags using definitions contained in:"

From this point on no edit can be saved, "done" doesnt' work at all.

Turned on the debugger console in Firebug, reports:

list[i].split("=")[1] is undefined  . . .  line 1646 in AutoTagger


Just on the off chance it's my FF3? Tried a clean profile (taking a gazillion extensions out of the equation). Still no go.

Tested in IE (yech) but everything works!

OK, so FF3's old, wouldn't expect you to fix that, it's about time I started looking at migrating my dinosaur extensions over to v4.

Downloaded FF4 (RC2 "final" portable version, only released end of March and they're already shoving FF5 down our throats? scandalous! but I digress. . . )

Same problem with FF4. 8-(

So at this point AFAIC if I really need to use AutoTagger's alias feature, I'll be doing that work in IE - but I imagine you'll want to have a look at the issue? If so, hope it's an easy fix!

As always, thanks for all your brilliant work. . .

Hans

[Eric Shulman]

> list[i].split("=")[1] is undefined  . . .  line 1646 in AutoTagger

This error occurs if AutoTaggerAliases is not *empty* and contains any
lines that do NOT have an "=". For example, a blank line. The only
recognized format for the content of this configuration tiddler is:

alias1=one or more space separated tags
alias2=othertag
alias3=othertag2 othertag3
etc.

Can you check to confirm that the error vanishes if you use a properly
formed configuration tiddler? If it does, then I can easily add a
small bit of code to the plugin to handle that conditino and avoid the
error, even when presented with a badly-formed configuration tiddler.
Of course, if that doesn't fix the problem, then I have to look
deeper.

-e

[HansBKK]

Whale that was easy! 8-O

Strange IE's handling bypassed the problem?

I guessed I missed the memo about a trailing hard return messing things up 8-(

Anyway if that's all it is I'm a most happy camper! The issue weaned me off MPTW and led me to the TWT-Treeview "Executive" template, so a productive side track in my TW journey. . .