Closed maiksd closed 11 years ago
Just wondering, are you using the OnDemand service or running Stash yourself?
This is our own Stash installation.
Hmm... I just tried to reproduce it with a clean installation of Stash and didn't run into any trouble. Is there any exception or anything else in your log output?
Unfortunately, nothing shows up in the logs at all. No exception, and nothing else.
I tried it on another Stash instance I have, where it works. The one where it isn't working is running on Mac OS X Server, which I know is not officially supported, but we don't have any other problems there. The only other difference is Java 6 (OS X) vs. Java 7 (Linux). Could it be that? Stash 2.x is still supposed to be working on Java 6.
Thanks for the info. I'm actually running it myself on a Mac (although not OS X Server) using Java 6.
Next, can you provide any info on what the browser is getting? In Chrome, before trying to enable the plugin, you can open the Developer Tools and go to the Network tab to see the request being made. What response are you getting back? Is a 404, 500, something else? I'd be interested to see if anything shows up in the response body. Also, any sort of Javascript errors that appear in the console?
Looking at the error console, did the first two messages appear before you clicked the Enable button? It appears that the WebFragments object isn't defined on your page (for some reason or another). Are there any 404s, etc. that occur earlier in the page? Seems there's some Javascript missing somewhere.
Yes, those appeared before. And now at my next try I have a triangle to click them open:
Uncaught TypeError: Cannot read property 'length' of undefined batch.js:584 jQuery.extend.each batch.js:584 B.widget batch.js:1172 (anonymous function) batch.js:1314 (anonymous function) batch.js:1510 Uncaught TypeError: Cannot call method 'load' of undefined hooks:127 (anonymous function) hooks:127 (anonymous function)
Do these errors still occur after disabling the plugin? My guess is that this is beyond the scope of the plugin, but still interested to know what might be going on.
Ha, found the culprit. It's the README parser plugin. Once I disable that, the errors are gone, and now your plugin shows the response it's supposed to!
Awesome! Glad to hear you figured it out. And thanks for letting me know.
Using Stash 2.5.0, installed the plugin freshly for the first time.
When I try to enable the plugin on an repository, I only get neverending spinning ball.