Puddleglum

I’m going to say no as my rather important issue of the plugin no longer functioning has been ignored for that long.

Yes, this is the SOP of which I wrote…and yet it did break the old shortcodes.

All the worse if one uses plugin auto-update features.

A form of spam. No. You do not understand the word spam. How dishonest.

This plugin was an inline shortcode for executing php code. It was changed to a snippets plugin and broke the inline functionality. The new developer could have forked development with a new development path with an appropriate name but chose to leverage an existing plugin and all of its installations (including reviews/install #s/popularity ratings, etc.)

Just fork it. The worthwhile thing about your plugin was the lack of snippets nonsense. Now it has none. Dev-stopping a plugin, or in this case coopting a plugin people installed for one reason and removing that reason is rubbish.

I haven’t the foggiest what a USP is, but you have quoted my thoughts and sentiments precisely.

Horsefeathers. You’re reinventing a wheel which already comes in a variety of makes and sizes. You’re removing and/or EOLing the thing for which you were the unique provider. Or do you mean to fork and continue to develop the old version making sure it tests with each new version of wordpress? If so, keep the old and rename the fork to reflect what it has become instead of what it no longer is.

Lol. I removed the wrap=”i” just to see if you might have actually programmed it to default to one wrap or the other. Nothin’ doin’. ??

Whoops! It looks like you forgot to specify your html tag.

It’s being done by WordPress itself. Solved by the addition of this remove filter via another php plugin:

[insert_php]remove_filter('the_content', 'wptexturize');[/insert_php]

No good. Still somehow munging html outside of its boundaries. I don’t have wp-typography enabled, so it’s not being done by another plugin.

Heh… it did interpolate the & # 8243 ; in the last ‘code snippet’, the “View Source” one. It replaced it with the “Double Prime U+2033″ character. Which is why my HTML is failing, as that’s not a closing ”

I tried the edit from the Gibberish topic immediately preceding mine, but it did not correct the error (Just in case we had the same gibberish).

I’m going to try one last attempt using a sing quote around my echoed string.

It’s also screwing up layout when the mouse cursor is over certain elements… the title and the image specifically. Mouseover either and a black region appears behind… one that does not look correct and intentional. Shown in the two images below:

Over Text
Over Image

Learn something new every day. ?? Thanks.

I’ve not been able to find those settings in Aptana. So the file lacking ?> is completed elsewhere?

Not sure if I subscribed to this thread or not and it won’t let me w/o posting a comment.

Trying to delete and then reinstall results in a WordPress so broken that it can’t even serve the login page for wp-admin.

Last snapshot in the Wayback Machine is April 10, 2016 16:47:21.