Avrom

Hi Aashik, well it’s a start to have the hook or filter – but doesn’t really help in this case without the snippet. There are a couple of us here asking you to adjust the filter, as its placement is not a good location. We’ll just use Automate Woo and/or Mailchimp for this project.
Cheers

Hi Daniel,
Thank you for the reply back. As you can see below, the MailPoet hook is at the top of the checkout info, but it should be above the checkout button. Or above the agree to terms checkbox. I hope that clarifies…
Cheers

Yes, we have the same issue as well on our self-hosted UpdraftCentral. We also see the same issue on UpdraftCentral Cloud. We submitted a support ticket yesterday, so they are aware, and I am awaiting their response.

Make sure you don’t click on the eye-icon or you won’t be able to get that menu option back.

Pavel, thank you for the followup. We installed a different plugin for Instagram, and it worked perfectly fine out of the box. No issue with responsive display.
Thank you.

Hello CharlieRich,
This is a forced accesibility update that seems peculiar to Ocean WP. Try setting the outline to 0 instead of none. Then clear cache and reload page etc.

We added the below code to Appearance > Customize > Additional CSS (instead of the style sheet) and it worked fine for us on several sites.

a:focus {
 outline: 0 !important; 
}

Hi Shahin,
Thanx for the reply. But this isn’t the issue. Yes we have CDN and caching, and yes we’ve already disabled plugins and tested.

NO, we are not going to install your Ocean WP Extra plugin. It’s just extra bloat and features we don’t want or clients need, not to mention the upselling and ads in it.

Other multi-step checkout plugins worked just fine, even with the CDN and site caching. Two of those plugins were not a problem with the checkout steps scrolling back to the top or where they were supposed to scroll when previous or next menu items were clicked.

We just wanted to use what was already built into Ocean WP, as its a good framework, but we’ll revert to one of the other plugins if we have to. Or look at another base theme that is lighter.
Cheers

• This reply was modified 2 years, 9 months ago by Avrom.

Nevermind, I see this is a feature of paid pro plugin.
Cheers

Thank you! ??

Thank you for the answer!

I was just asking a question, which you answered. I don’t really know what your last paragraph has to do with asking a question. It had noting to do with pre-sales, and how would I know that feature is only in the Pro version? I would think asking you how to change the arrow size was perfectly valid.

Hi Andrew,
Thank you so much for following up! Rolling back to 5.4 solved the issue (perhaps temporarily). I think you are absolutely correct. We have an older theme, a few too many plugins, and I can easily see problems and conflicts from that.

Yes I have been aware of the JQuery Migrate Helper. As we are rebuilding soon, we’ll let this one slide unless we have further problems.

Thank you again.
Cheers
Avrom

• This reply was modified 4 years, 7 months ago by Avrom. Reason: spelling typo for "the"

Hi Andrew,
Thanx for the advice on testing. No we cannot start disabling plugins and testing on a live production site.

The testimonial widget in SiteOrigin is the issue, as it worked fine until WordPress 5.5 update. The JQuery migrate helper is a possible band-aid. Please fix on you end as you are able – and please let us know, thank you Andrew.

Great news, and thanx for the super-fast reply!

Hi Brandon,
Thanx for the reply, appreciated. But other social media plugins don’t require you to create an account – so I am not sure why that is necessary. Really, this is just simple sharing buttons.

Anyway all the best, and have a good Xmas and holidays.

Cheers

Hi there, thanx for getting back. ??

Sun 11/26/2017 7:10 PM
Smartcat Support <[email protected]>
You have created a new request for support

Your request (#1924) has been received

However, the hope is as more and more work is done on Gutenberg; less and less will want to turn it off.

Hi Tammie,
I see you using this quote a lot for the 1 and 2 star responses. And I’ve also seen in other posts you mention plugins to switch Gutenberg off.

Rather than layering another plugin to switch off Gutenberg, why can’t the on/off switch be enabled in core directly?

SO those who like Gutenberg 1/3 of users here, can have the full functionality of it enabled.

But to rest of us 2/3 of users here, who develop on WordPress as a CMS and need the current features, we can just disable it. This would be a very good way for us to test current sites and plugins on client sites.

It’s not just about editing, which honestly Gutenberg doesn’t do that well IMO, but about the full functionality WP was built on. There are numerous posts about all of those here (i.e. custom posts, meta etc.). I can’t believe all of this simply an afterthought.

I have to be honest with you Tammie, like many thousands of other developers out there, we can’t continue with WordPress anymore in this state of flux. There is too much risk moving forward – my clients and I simply don’t need the uncertainty.

I’m not going to use the line from Walking Dead when Negan tells Rick “____” (gotta keep it family friendly here). But it is then followed by, “…And you’re going to thank me for it.”

Hmmm, I don’t think so – bye WordPress!