gbever

Via experimentation, I was able to figure out that your answer works perfectly with unset($gateways[‘stripe’]);

Marking this closed and thanks for the great support.

Thank you so much for the super fast response. This code seems to work perfectly but it does the opposite of what i need. I only want to show ACH.

I assume id only need to change:

$gateways[‘stripe_ach’]

but Im unsure of what to set that to. Tried a number of variations including cc, credit_card etc.

• This reply was modified 9 months, 2 weeks ago by gbever.

You are 100% correct about 2 different versions of JQuery being loaded. I found that the original developer of this site included a version of JQuery manually in an included file. Removing this conflict fixed everything. Thanks!

Ive learned that this is not enabled by woocommerce unless you purchase the paid subscriptions plugin. Closing the issue.

Hey there,

Just confirming your latest patch seems to have fixed this issue. Thanks so much!!

In my case, we wanted to insert DFP tags for banners, a common use of widgets in a sidebar. When adding in the code, it sees a var in the javascript code that is defined elsewhere and wont let me save. It really defeats the purpose of adding in a HTML widget, there are too many possibilities to attempt to validate the contents. The functionality is pretty good itself and they probabally spent a lot of time on it, but it doesn’t have a place here. Either that or add an option to turn it off.

Ok will do, thanks.

• This reply was modified 7 years, 3 months ago by gbever.

Ok, Thanks Beda. So in General any wysiwyg fields created with ACF will be broken after taking control of them with types it seems, which means ill just need to leave ACF installed. I would rather use types since its so much better, but I had already used ACF to start before I tried types plugin. Not a problem and thanks for your help.

Completely understand , this would be a fringe case. The way you could replicate this ( I also use the free version of ACF ) is to add a wysiwyg custom post field using ACF to Posts and populate some data. Then install types and take control of that post type. If you return to the post and both ACF and Types are active, you will see the field twice, once displayed by ACF recognized as a wysiwyg field type, and again displayed by types, as a multiple line field type.

Same problem, and Im attempting to move only a portion of the posts so moving the entire media library is not an option. Even still when i look at source, its still requesting the images inline from the old site.

Hi,

I apologize, I didn’t get notifications for your earlier responses. Thanks for those solutions. I realized it was a low priority during the project i was working on to get it running locally. Once i saw your solution, I tried it on our dev server ( which is not locally hosted ) and it worked perfectly, so I will be building it in to the final project after all. Thanks for the help.

Ok, no problem. Ill cut over there and get you the error.

I just gave up and deleted the plugin as the response was not adequate for me either. Im just too busy with clients to screw around with it anymore when there as so many alternatives.

Hi,

I made that change, and specified another handle just like you said. It still does the same thing, now it shows the extra handle ( i already follow the first one so it doesn’t show after I share ) and AddToAny is still there. Any suggestions before i delete this and give up on it all together?

I’ve already added that markup specified in the link attached to your message, before i even put in the original ticket. Mine is verbatim except for the @addtoany, its our own handle. That part is fine, but after the share, the popup comes up and still says follow add to any as a recommended follow.

My code looks like this
a2a_config.templates = {
twitter: “Reading: ${title} ${link} by @ouruniqehandle”
};

It still pops up after users share and asks to follow addtoany