The Open and Copy empty underneath, save and reload method has worked for upgrade.
Fingers crossed I helps with my regular abend after time problem Thanks On Monday, 24 June 2013 15:19:50 UTC+10, Eric Shulman wrote: > > I received this message > >> *Problems were encountered loading plugins. See PluginManager for details >> **HoverMenuPlugin** >> Error: SyntaxError: unterminated string literal >> **MonkeyTaggerMacro** >> Error: SyntaxError: unterminated string literal >> **PopupMacro** >> Error: SyntaxError: missing : in conditional expression >> **TaggerPlugin↓** >> Error: SyntaxError: illegal character* > > > I've tested the TW2.8.1 upgrade process using Firefox (release channel, > v20.0.1) with TiddlyFox (1.0alpha16), and I am not having any problems with > upgrading. > > To load a plugin, the TWCore reads the content from the plugin tiddler and > then passes that content to the javascript eval() function for processing. > The TWCore then simply collects any error response and displays it in the > PluginManager. Thus, the errors you are seeing are not actually coming > from the TWCore itself. > > The problems you are reporting don't make any sense to me. If there was > some kind of central TWCore problem with loading plugins, it seems like it > would occur with *every* plugin you have installed, rather than just a > handful. In addition, all of the errors that are being displayed are > *syntax errors* within the code being eval()'ed, which suggests that the > contents of those specific plugins have been directly damaged, rather than > it being a systemic problem. To figure out what is happening, I suggest > that you start by looking at the content in those specific tiddlers. Does > it seem like they have been truncated, corrupted, or otherwise "mangled" in > some way? Was the content word-wrapped (which can add newlines into the > plugin's code, breaking some syntax)? Do those plugins have any multi-byte > UTF8 "symbol" characters embedded in them? TiddlyFox has had some issues > in the past with multi-byte character encodings that could result in > invalid content. Although I believe that Jeremy has fixes those problems, > it's still something to consider. > > Also, have you tried the "manual" upgrade process? > 1) Load a currently working copy of your document into the browser > 2) REPLACE the existing file on disk with a copy of TW281 empty.html > 3) From the loaded document, choose "save changes" > > The "save changes" handling first re-reads the document file from disk > (which is now an empty TW281), then merges the tiddlers currently loaded in > browser memory, and then writes the combined file back to disk, producing > an upgraded document in the process. Give that a try and let me know if it > works. Other than that suggestion, there's very little I can do to help > without being able to examine the upgraded document directly. Can you post > it somewhere online? > > -e > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
