[TW5] Internal Javascript message upgrading to 5.1.8 from pre-release

[Jon]

Hi,

 

first of all thanks to Jeremy and everyone for the new release.

 

I have 2 wikis on the pre-release. One upgraded perfectly (by dragging and dropping the wiki on to the upgrade wizard) but the other generates a rather large Internal Javascript error message and won't proceed any further.

 

Any ideas?

 

Thanks

Jon

[Neil Griffin]

I had this problem (discussed in this thread: https://groups.google.com/forum/#!topic/TiddlyWiki/T6WkSLAzjVc).  If it's the same thing, then it's due to a bug in the prerelease.  I solved it by using a different upgrade path.  If you do a filter search for [all[tiddlers]] then export the results to a JSON tiddler file, you can then drag the resulting file onto an empty v5.1.8 tiddlywiki file from tiddlywiki.com, and you should be back to a bug-free version.

Neil.

[Jon]

Thanks Neil.

When I tried this and dropped the JSON file on to an empty 5.1.8 file and then imported it, I only see the JSON file and not my original tiddlers...?

Regards
Jon

[Eric Shulman]

On Monday, April 20, 2015 at 11:03:33 PM UTC-7, Jon wrote:

When I tried this and dropped the JSON file on to an empty 5.1.8 file and then imported it, I only see the JSON file and not my original tiddlers...?

If you are dropping the file into an empty TW5, it is easy to miss the "drop zone" if you drop it randomly in the big empty space.  Try dropping the file ** near the top of the document ** and make sure the green "drop here" message bar appears before you let go.

enjoy,

-e

Eric Shulman

TiddlyTools / ELS Design Studios

YOUR DONATIONS ARE VERY IMPORTANT!

HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...

   http://TiddlyTools.github.com/fundraising.html#MakeADonation

[Jon]

Hi Eric,

I can't try it again until later tonight but I think I did hit the "drop zone" because it presented the file with the option to import it, but I'll try again later.

Thanks

Jon

[Jeremy Ruston]

If you've got an 5.1.8-prerelease wiki that won't upgrade to the final release, you can try to fix it by first taking a backup, then opening the file in a text editor and using search and replace to replace ' with a single quote. Save the file try opening it in the browser.

-- EDIT search string corrected 24 April 2015

As others have noted this sorry saga is the definitive reason why everyone should avoid using the prerelease for anything important.

Best wishes

Jeremy.

[Jon]

Hi Jeremy,

That worked - amazing!

Point taken about being careful with pre-releases.

Many thanks
Jon

On Tuesday, 21 April 2015 15:30:04 UTC+1, Jeremy Ruston wrote:

If you've got an 5.1.8-prerelease wiki that won't upgrade to the final release, you can try to fix it by first taking a backup, then opening the file in a text editor and using search and replace to replace ' with a single quote. Save the file try opening it in the browser.

As others have noted this sorry saga is the definitive reason why everyone should avoid using the prerelease for anything important.

Best wishes

Jeremy.

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/76649de9-428e-4f30-b25d-9e84af6c4de0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Jeremy Ruston]

>If you've got an 5.1.8-prerelease wiki that won't upgrade to the final release, you can try to fix it by first taking a backup, then opening the file in a text editor and using search and replace to replace ' with a single quote. Save the file try opening it in the browser.

Apologies, those instructions are incorrect. The correct string to search for is:

'

Best wishes

Jeremy.

[Jon]

Hi Jeremy,

The previous instructions did allow the upgrade and the wiki appears to be working as normal.

Should I revert to a previous version and apply the new instructions to that?

Sorry to be a pain.

Regards

Jon

[Jeremy Ruston]

Hi Jon

The previous instructions did allow the upgrade and the wiki appears to be working as normal.

Should I revert to a previous version and apply the new instructions to that?

I would advise doing a search and replace for the corrected string on your current file (having backed it up). The reason is that the incorrectly encoded single quotes will display OK in body text, but not be interpreted correctly when used to quote attributes of widgets or HTML elements (for example). So you might still have some of the incorrectly encoded quotes without necessarily being aware.

Best wishes

Jeremy.