pipfroschpress

Bingo – set it to 20 in Plugin B and that did it. Thank you so much.

No I didn’t but I bet that would work, thank you. Will try now.

Found a second bug as well, so I fixed both and stayed up instead of sleeping to test the fix thoroughly. First plugin I’ve written in eons. Anyway both resolved.

Hi – coder here, but not for WordPress.

With minor releases, most software (including WordPress) generally do not alter any of the public interfaces that things like themes and plugins should be using. When a minor update breaks a theme or plugin, there is a decent (though not certain) chance the theme or plugin was either doing something it should not have been doing or was using a feature with a security vulnerability that had to be fixed.

With major releases, most software (including WordPress) generally broadcast the API changes during the development cycle long before the actual release, which gives plugin and theme developers time to adjust their themes and plugins to adapt to any new changes they need to adapt to.

My personal frustration with WordPress is not that it updates too frequently, but that it doesn’t bring the changes I want – such as deprecated PHP pre 7 or introducing PSR-7 autoloading into core, etc.

So be happy I’m not in charge, and cut them some slack. Plugins and Themes that break are likely not the fault of the WP core devs, who are way more conservative than I know I would like.

The plugin and theme developers need to read about upcoming changes and adjust accordingly. That’s part of the responsibility of publishing a plugin or theme.

I got it all figured out and working. Biggest problem was a typo, but that wasn’t the only issue.

Once again, thank you for the advice!

I looked into it some more and using that filter would have broken the ability to use a child theme with it. I don’t need a child theme but someone else may want to do it that way.

Okay thanks. I just saw that the style.css was being loaded by calling get_stylesheet_uri() which included the hardcoded style.css in it.

So just ignore that function (don’t use it) and thus do not bother with a filter, that’s simpler.

Thank you.

Oh and than you.

Anyone happen to know which piece of JS is called when switching from Text to Visual?

That’s undoubtedly where the code that converts the entity is, I could just probably edit that. Might have to repeat every WP update but that would solve #1 and let me solve #2 by continual to use visual except when I need to add an entity or custom markup.