carlocapocasa

Hi there! In case you’re still following this, here’s an answer.

Noted Jetpack as an incompatible plugin and I’ll see what I can do about it.

Audiobar adds a # because it wraps your entire site into a so-called iFrame (a browser window in a browser window).

Then it maps the part after the # to the URLs in the iframe, and vice versa. If I were to leave out the #, the complete browser window would reload when you click a link and Audiobar would stop playing.

Hi there!

Supporting mobile devices properly is high on the priority list.

It’s probably not that hard to code, either. But it is hard to test.

Open Source development depends a lot on being able to get started right away if you have a spare hour and really feel like coding, and having to borrow devices first and make plans just puts a curb on that.

It’ll happen though. First iPhone, then iPad, then Android. No blackberry.

Carlo

Hi there!

I haven’t tested Audiobar with multisite installations yet… Noted in the to-fix-list.

Thanks for giving it a try! For now I can only recommend to use it for single site installations only, or wait for an upgrade that solves the problem.

Carlo

Hi All!

Said update has arrived! To fix your problem, please upgrade to Audiobar 1.0.1 with the Upgrades tab in WordPress. 1.0.1 has been created specifically to fix this issue.

As a bonus, you’re blog’s going to be more responsive, especially if you have a lot of songs on one page.

Thanks for using Audiobar!

Spread the Music,

Carlo

PS: Worried about slow forum response rate? Don’t. I’m getting to the issues, one by one.

Hi you two!

That’s a real great idea… I’ve got something like that cooking in my mind but it might be a while until it gets round to being implemented.

Thanks for using your ideas to help make audiobar better!

Best, Carlo

Hi there!

Whoa, sorry about that pal… Only just started monitoring the forum.

If you’re still there and it’s still an issue, please give an URL and I’ll look into it.

Thanks for taking the time to report!

Carlo