Brady Vercher

Hi @ma3ry, the blurry background is the intended design, but you can hide it with a bit of CSS if you like. A snippet like this should work:

.mejs-player-background { display: none;}

No problem, @ralf-r. I bumped that tag, so hopefully that helps you out with the warning.

Cheers,
Brady

Thanks so much for the positive review, @hcmobilemedia! We appreciate the support and you trusting us with your site.

This doesn’t appear to be related to Simple Page Sidebars. Your best bet is to get in touch with the theme author to ask them if it’s possible to do what you’re wanting.

@schnauzer42 Since this was primarily built for pages, I don’t believe the column gets registered for CPTs if you add support for them. To delete a sidebar, you would need to set each CPT using it to use the default sidebar instead.

Simple Image Widget should continue working with the latest version of WordPress. It’s considered stable and there aren’t plans to add new features, but bugs will be fixed as they’re reported.

Core has included a native image widget for a couple years now as well if you want another option.

To delete a sidebar, you just need to remove it from any page that it has been assigned to. When viewing the list of pages in the admin panel (Pages → All Pages), you should see a column with the assigned sidebar — you can click the sidebar name to edit it or choose which pages it has been assigned to.

That doesn’t sound pleasant, but it’s not something we’ve experienced and we haven’t had any similar reports. I tested with the current version of Cue using a shortcode and wasn’t able to replicate the issue, either.

Considering Cue the current version of Cue doesn’t have integration for the new editor and you’re using the default shortcode block provided by core, are you sure it’s a problem with Cue? Have you tried deactivating other plugins as well?

Feel free to reach out through our contact form and I’ll send over the latest release so you can see if it resolves the problem you’re having.

We appreciate the review, @moruku! Cue isn’t being abandoned as it’s the basis for most of the audio functionality in our themes and we have a couple of premium plugins that are based on it. We haven’t received similar reports about the glitches you’re experiencing, but we’ll look into it.

That being said, we actually have an unreleased update to add support for the new block editor. Feel free to reach out through our contact page if you’d like access to that.

Thanks,
Brady

Thanks for the thoughtful review, @messanoir. It’s much appreciated! I’ll looking into bumping the tested version soon.

Hi @aareeph, MediaElement.js builds the markup for the player, so replacing it with Howler.js would be pretty difficult, if it’s even possible.

All the content is stored in the database with the theme-defined widget areas. Are you sure you’re using this plugin (there are a few with similar names)?

Glad to hear you like it, @reelism!

1) The list of plugins is cached to prevent Plugin Toggle from causing performance issues, but if you visit the Plugins → Installed Plugins screen in your admin panel, it will clear the cache.

I’m not exactly sure why or how the toolbar link would remain after Plugin Toggle was deleted, but that’s not something that would be related to the plugin itself. It sounds like some sort of aggressive caching on the server or another plugin.

2) I run Plugin Toggle on sites with 100+ plugins and haven’t seen anything similar to what you’re describing. A screenshot might help. This may also be related to the first issue if you’re able to figure that out.

Hi @daniellepijpers, it doesn’t look like you’re using Cue on your site, although you are using one of our themes. The version of Marquee you’re using is a few years old, so you probably need to update to get the audio working again.

Thanks,
Brady

Hi @macronx,

It looks like something on your site is modifying the data that Cue outputs, which is preventing it from being parsed correctly.

If you have a plugin that minifies the output, you might try disabling that to see if it fixes the issue. If so, you can get in touch with the developers of that plugin and ask them how to prevent /*<![CDATA[*/ tags from being inserted into script tags.

To make the player full-height, you can add this snippet of CSS to the “Additional CSS” section in the customizer:

.cue-playlist .cue-tracks {
    max-height: none;
}

Cheers,
Brady

• This reply was modified 6 years, 2 months ago by Brady Vercher.