Pocket Query Plugin creates JS Error in IE9
Asked by mvolkmar:

Hi,

after we have activated Pocket Query Plugin at our Confluence 4.3 Plattform a JS Error appears on the dashboard and on all content pages.

SCRIPT5007: F?r die Eigenschaft "setMacroJsOverride" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert   
batch.js, Zeile 2484 Zeichen 357

The error appears in that script:

(function(c){var a="http://www.scandio.de/en/atlassian-en/plugins/pocketquery/pocketquery-documentation/";var b="";b+='\<a class="aui-message shadowed success pocketquery-help" target="_blank" href="'+a+'"\>';b+='\<span class="title"\>';b+='\<span class="aui-icon icon-success"\>\</span\>';b+="\<strong\>Click here if you need help!\</strong\>";b+="\</span\>";b+="\</a\>";AJS.MacroBrowser.setMacroJsOverride("pocketquery",{beforeParamsSet:function(e){var d=c("#macro-browser-dialog");d.addClass("pocketquery-macro-preview");d.find(".dialog-panel:last").append(b);d.find(".dialog-title").html(function(f,g){return g.replace(/\&amp;#8216;/g,"")});return e}})}(jQuery));  
/\*\*  

For me it seems like Pocket Query wants to add a dialog to the macro browser. But on the Dashboard there is no macro browser.

Thank you for your support.


Answers:
author: mvolkmar
body: Btw, the errors appears in FF as well.


author: Felix Grund (Scandio)
body: I uploaded a [new version](https://marketplace.atlassian.com/plugins/de.scandio.confluence.plugins.pocketquery/versions#b1166) that fixes this bug. I'd be very happy if you left a review if you like PocketQuery (despite this little inconvenience ;)).

comments: author: Christian Koch
body: I uploaded a [new version](https://marketplace.atlassian.com/plugins/de.scandio.confluence.plugins.pocketquery/versions#b1166) that fixes this bug. I'd be very happy if you left a review if you like PocketQuery (despite this little inconvenience ;)).


author: mvolkmar
body: OK, thanks. We will test it.


author: mvolkmar
body: Unfortunately after the update you cannot insert the pocket query macro anymore since the macro browser view is broken now. Therefore it became useless for us.


author: Felix Grund (Scandio)
body: What do you mean by "is broken now"? We've tested the new PocketQuery MacroBrowser thoroughly and I've only gotten very good feedback so far.


author: Felix Grund (Scandio)
body: Hi Theresa,

you mean, the office macros won't work if you have a PocketQuery macro in the same page? I'll fix this as soon as possible!

A bad review on the marketplace is definitely the worst option. Unfortunately, we do not currently have an issue tracker for PocketQuery. That's why we set our Email address as the support address at the marketplace.

Regards, Felix

comments: author: resah
body: Hi Felix,

thanks for the heads up.
> you mean, the office macros won't work if you have a PocketQuery macro in the same page? I'll fix this as soon as possible!

Actually this happens without adding the PocketQuery macro to the page. I guess you added some JS which is loaded by the macro browser (to load custom macro configuration view?) and this seem to collide with the office macros.

Regards

Theresa


author: Felix Grund (Scandio)
body: Ok, thanks! I'll fix this and prepare a new release sometime this week.


author: Felix Grund (Scandio)
body: Please find our new PocketQuery release now at the [Atlassian Marketplace](https://marketplace.atlassian.com/plugins/de.scandio.confluence.plugins.pocketquery).

comments: author: resah
body: Hi Felix,

after updating the plugin to 1.10 the office macros aren't working properly anymore. E.g. when trying to insert **viewppt** macro into a page no dropdown to select a file is shown in the macro configuration screen. After disabling the PocketQuery plugin this worked fine.

Could you please fix that?

Do you have an issue tracker at Scandio? I didn't know were to report such a problem without giving you a bad review in Marketplace ;)

Regards

Theresa


author: Felix Grund (Scandio)
body: Hi,

thanks for your interest in PocketQuery! We will release the next major version 1.10 of our plugin on Friday, October 25th. Besides many major improvements, this JS bug will be fixed in this release.

I know I promised a new release much earlier, but I couldn't find the time to work on the plugin thoroughly enough earlier. There will also be a blog article on the improvements with the new version. I'll keep you up to date here.

Regards, Felix