m4olivei

Here is a quick and dirty patch that is working for me. Long term, this plugin should probably move away from jquery.tooltip.

It was using jQuery.browser.msie, which jQuery hasn’t had for awhile, to detect IE 5.5 / 6. Safe to say most people don’t have to support that anymore, so I removed that check and the corresponding supports for those old browsers.

https://gist.github.com/m4olivei/2b489e0709162a6fe339e8fc9810b243

Hope that helps.

Yep, I ran into this today as well. Seems like jquery.tooltip is no longer supported. The project page states the latest version is 1.3, which is what ships with this plugin.

https://bassistance.de/jquery-plugins/jquery-plugin-tooltip/

It also states you can use jQuery migrate, but as you say that won’t rut it for jQuery 3.x.

We’re an approved Apple News channel. So being an approved channel doesn’t lift this limit. I just noticed that we get these errors. We’ve been getting them since July (at least according to the log data I have access to). Apparently it hasn’t been an issue for our editors (yet).

Hey,

I put it in a custom plugin, should also work within functions.php in a theme. Change the name of the function to something other than do_action and update the call to add_action() accordingly. Sorry about that. In my plugin I have the function as a method of a class so I didn’t run into that naming collision.

Thanks,
Matt

Thanks. I remembered the same thing, I just hit the Permalinks page in the Admin and it fixed it.

I’m having the same issue. I defined a post type called ‘story’ and all posts of that type are 404’ing.

Did you solve the issue?

@xnau that didn’t fix the issue for me. setting a default argument for $id_or_email in the get_avatar() function as mentioned by @draiz however, did.

Hey,

Found the same issue. The problem is that WPML filters the sticky_posts option (in wp_options table), which is where the sticky data lives in the database. WPML joins on their own icl_translations table to translate the sticky data, which is good, only it hardcodes a check that the post is of type post. Thus WPML won’t allow custom posts types to be sticky. To fix this, you need to patch WPML. Open plugins/sitepress-multilingual-cms/sitepress.class.php

I’m using version 2.8.1 and so the line I needed to alter was 6320. It’s the option_sticky_posts function and we need to edit the query line to the following:

$posts = $wpdb->get_col("SELECT element_id FROM {$wpdb->prefix}icl_translations WHERE element_id IN (".join(',',$posts).") AND element_type LIKE 'post_%' AND language_code = '{$this->this_lang}'");

eliawk, where is the thread on the WPML forum about this that you allude to? I’d like to submit a patch to them.

Thanks,
Matt

I noticed that when I used the theme switcher with my theme, for some reason the menus and widgets dissapear.

I traced through wp_nav_menu() with a debugger and found that it passed through get_theme_mod, used the get_option(‘stylesheet’) and seemed to break down there because it was not using the name of the switched theme, but the “Real theme” (as defined above).

I swapped in you’re dev version and it worked.

Looks like something similar to this thread is going on:

https://www.ads-software.com/support/topic/issue-with-get_theme_mod-and-toolbar-theme-switcher?replies=6

I used the dev version linked there and all is well for now.