benchwarmer

Hi Tobias. Yes I have LT for Firefox. Last update they did –according to their website–was 2 months ago (version 6.01). I trid a fresh install and it still is interfering, so I’ve just disabled LT on this site. Will just keep an eye out for the next update and hope they fix it.

Thanks for your help.

Thanks. Simple solution, which I wish I would have thought of in the first place!

Just correcting what I said above, the spacing problem occurs on all links that are also keywords–even after I exclude links in the plugin settings. It affects both leading and following spaces. I can manually fix this if I add spaces on either side of the keyword inside the tags, but man is that a lot of henpecking through the site to find affected links.

I’m having a similar problem with the Tooltipy plugin (which I otherwise love btw). I consistently see that when the tooltip is also a link, the leading space before the tooltip word/phrase is removed.

I actually excluded links in the tooltipy menu, but it doesn’t seem to apply to anchor links (or if it does, tooltipy still influences the formatting).

Any thoughts?

We’re seeing the same thing, and I’ve not been able to replicate it. In another thread on here (WP Forums), it was recommended we stop using the Credit Card Processing add on, which we did. That seemed to have helped, however today we got another seemingly unexplained payment failure. The same customer bought one thing successfully, and then was unable to buy a second product after multiple attempts. Same generic error message :

“Could not process order. Order status changed from Pending payment to Failed.”

WHich doesn’t give you any of the “Why” that would be helpful to understand if this is related to the others or something different.

So am glad to hear that they’re improving the error messaging. I hope that comes out soon.

Actually, while I’m here. Stupid question, but if you can still pay with a credit card after turning off credit card processing….what’s the difference?

Hi Niklas,

Since I came looking for the same reason, I was just wondering if there’s been any progress on identifying the problem. We’re seeing the same thing on our sites.

I actually had a similar question, so seeing as this is a new thread, I’m jumping in with Scott. Maybe it’ll give it more weight.

Most of the solutions I’ve come across for mega menus are not fully accessible. Specifically, I’m looking to be sure that any menu items I put in the mega menu are accessible via a keyboard interface (e.g. tab/arrow key to top menu item, opens the mega, tabs through content of the mega, then moves to the next top menu item). On the demo page it appears that only items that are text or form fields are highlighted on a tab through, but perhaps it’s because none of the images on the demo are links? I thoght I’d ask her before I look to purchase.

Like Scott, adding alt attributes to images and aria/role labels (if not already included) would be needed too.

OK got it. Thanks!

Well the Taxonomy name shows up in Pods and the “Associated Post Types” checkbox is still checked, but none of the fields for the taxonomy show up. So basically it’s an empty shell.

I went ahead and disabled all my plugins, cleared Pods cache, and again I did the import/export package migration from a backup. None of that fixed the issue.

Pods is clearly still associated with the custom taxonomies and CPT, because if I deactivate Pods the CPT disappears from the dashboard along with the associated taxonomies.

Is there a way to import existing Custom Post Types/Taxonomies into Pods? Since Pods has disassociated with the taxonomies I built with it. Could I use the standard WordPress Export tool to export the “lost” taxonomies and then reimport into pods? Or maybe CPT UI? I don’t know. I’m lost as to what to do here.

The taxonomies are still on the dashboard and still maintain relationships, but all the field data in Pods is absent.

• This reply was modified 3 years, 4 months ago by benchwarmer.

Why would I need a template for an extended post type? Isn’t the template the existing post type?

Not to crash the party, but I just joined up with Kinsta and was both disappointed and confused when told I could not use AIO WP Migration. That’s how I ended up here reading this thread.

It’s simultaneously banned AND listed as a one of the “powerful migration plugins” by Kinsta themselves: https://kinsta.com/blog/wordpress-migration-plugins/ (link off their migration instructions page),

Since I have a license for it and the Multi-site extension, I was hoping to use it to migrate my site over. Bummed that we’re in this stalemate.

Been almost 3 months @kinstahosting . Probably should re-evaluate this.

Agreed this does appear to be related to WP optimize. I have the same error and it also appears to not occur when WP Optimize is disabled.

I’d implore @marcusig to re-investigate this. Seems to have a 10 minute cycle.

I have comments disabled on my site btw.

I’m experiencing this issue. Thought it was on my end.

news.research.uci.edu