davidbhayes

Thanks @westonruter! ??

Huh. I can’t reproduce this easily. The thought that the translation could be at issue occurred to me, but a quick trial of that doesn’t reveal a problem when I have my install in “Espa?ol” (es_ES) mode.

Do other plugins being off or on have an impact on this behavior? If you just run only this plugin does the issue still happen?

Another thing that may be useful is getting the JavaScript/Web Development/etc console open when you see it happen and see if anything show up there.

Final thought would be if you could give me access to the site it’d be a little easier to know what’s going on. Feel free to email me as david [At] pressupinc (dot) com if that’s amenable to you to figure out those logistics.

I’m not following what you mean by the “Upload new media” button — I’m finding I don’t see such a button any screen I’d think to look. Can you give some more details: which WordPress admin page are you on? Where’s the button? Etc.

I think that 1.2.1 may have had a small bug. I just released 1.2.2 this morning which *may* fix it. (Since I don’t yet understand your specific problem, it’s very hard to be confident.)

Hi sba7elfol,

Adding support for 4.4 is just comment and header changes so that it shows support. No code changes are/were necessary. 1.1.4 is essentially adding a translation and bumping comments/documentation.

Thanks for the reports. Please let me know if 1.1.1 doesn’t solve the issues.

That was actually the behavior before 1.0, but it was causing problems on older sites that had no featured images but would sometimes want to update older posts without them. Maybe this truly needs to be an option, as reasonable arguments can be made in both directions.

Hi, could you give some more details? I’ve not done extensive testing yet but it still works for me as it did before 3.9 in 3.9.

There are some featured image plugins that conflict with this right now, as they change the edit screen widget that the plugin is currently checking against. I’ve got a bit of a plan for getting rid of that dependency as time allows, but for now I’m wondering if that’s the issue you’re seeing.

The things that would be helpful for me would be a list of all other plugins you’re running OR a confirmation that an otherwise exactly equivalent setup worked on 3.8.x OR access to a site to debug it myself. Really probably the last on the list would be quickest, you could email [email protected] to move on that.

I hope we can solve this, and I appreciate the feedback!

Hey Sebastian, it does make some sense to at least consider moving it. I’m thinking I won’t plan to do so for now, but I’ll definitely keep it in mind going forward. Thanks for taking the time to mention it!

That’s an interesting idea, Sebastian. I suppose it would have the advantage that we’d have one fewer page under the Settings “tab.” Is that the only advantage, or am I missing something?

Generally, without more knowledge, I’m hesitant to move it there because I’d never think to look there for it if I were to want to change it. I’m open to being convinced that it’s worth the risk, though.

That’s a really interesting question.

I can’t say with certainty — a quick look turned up no such thing — but even if one exists I’d probably recommend against using it. Finding out what taxonomies used to exist isn’t a very performant operation, and you have to register your taxonomies before every page load. So while it’d be convenient the first time, your server would see a big performance hit overall as a result.

This same basic reason is why I generally avoid any of the numerous taxonomy plugins that exist. Though the fetching of the data the plugin itself stores in the database is more performant that finding unknown old taxonomies in your database, it’s all still slower than something hard-coded into a PHP file like your custom plugin would be.

Hi dylan!

The biggest thing that determines of whether not you can take that information with you when you change theme is if the taxonomies are registered in the theme or a plugin. If they’re in a theme’s functions.php, they’ll “disappear” when you change themes (though data would still be there, just inaccessible, in the database). If you instead do the registration in a custom plugin — I wrote a post that walks through the basics of what a plugin needs to have — you’ll be safe from theme to theme.

Hope that helps!