On 02/21/2014 07:05 AM, PMario wrote:
On Friday, February 21, 2014 4:46:47 AM UTC+1, Anton Aylward wrote:

    I've tried to make the non-working one as close to the working one
    as possible, same stylesheets and other plugins.
    But the debug defeats me.  i'm not a javascript programmer anyway
    and don't know what tools i'm supposed to use to insect.

    This is current firefox on current linux.


You could try to open the dev tools with F12

So open your "non working" TW and hit F12
Select the "Console" tab
Klick the tagSearch button.

You forgot that I had to tell the window to stay above others ...


If we are lucky, there may be an error message. if yes copy past it to
the group here.

Is this it?

08:09:50.765 ReferenceError: e is not defined BaseLine_Char_Loc.html:8454


And the code from the file around there reads

8475 // Check that a particular plugin is valid for execution
 8476 function isPluginExecutable(plugin)
 8477 {
 8478     if(plugin.tiddler.isTagged("systemConfigForce")) {
 8479             plugin.log.push(config.messages.pluginForced);
 8480             return true;
 8481     }
 8482     if(plugin["CoreVersion"]) {
 8483             var coreVersion = plugin["CoreVersion"].split(".");
 8484             var w = parseInt(coreVersion[0],10) - version.major;
 8485             if(w == 0 && coreVersion[1])
 8486                  w = parseInt(coreVersion[1],10) - version.minor;
 8487             if(w == 0 && coreVersion[2])
 8488                  w = parseInt(coreVersion[2],10) - version.revision;
 8489             if(w > 0) {
8490 plugin.log.push(config.messages.pluginVersionError);
 8491                         return false;
 8492             }
 8493     }
 8494     return true;
 8495 }

When I view the backstage/plugins pulldown it doesn't show any errors.
And no, the only tag on the plugin is 'systemConfig'

But also I don't see the variable 'e' in the above.

The header notes on TagSearchPlugin say it requires 2.5 or better,
This is 2.8.1

or this

Error loading source:
Could not load the source for javascript:;.
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.asyncOpen]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource://gre/modules/devtools/dbg-server.jsm -> resource://gre/modules/devtools/server/main.js -> resource://gre/modules/devtools/server/actors/script.js :: fetch :: line 4257" data: no]




If no :/   Can you describe a bit closer what "it doesn't work" means?
eg: ... The dialog pops up, but doesn't have content. or "there is no
dialog at all" ...

The dialogue box does not pop up.





The best possibility would be if there would be a downloadable minimal
"non working" testcase.html in dropbox or tiddlyspot.

I'll work on cutting away all the customizations...


--
I used to think that running an organization was equivalent to conducting a symphony orchestra. But I don't think that's quite it; it's more like jazz. There is more improvisation.
- Warren Bennis

--
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.

Reply via email to