RoamFree

I have a similar problem. The site’s home page (does not start with www, in case that matters) got redirected to /wpematico/13357/.

At least some other pages were not redirected, so it’s not a global effect.

I don’t understand why separate redirection is needed, as I’d expect the newly created posts to behave as the site has been configured to handle any new posts.

Oh, I see… A DYM widget appeared in Appearance > Widgets. If you’re willing to put a DYM widget where it will always be visible, then this is useful.

However, I don’t see any DYM results on the standard 404 page, so apparently one would have to edit the 404 page code if there is no widgets space visible on your default 404 page.

Doesn’t seem to be working for me in WP 4.0 with Weaver II theme.

The installation notes say “in Tab Plugin click “Did You Mean””, but I don’t see “Did You Mean” anywhere in the admin interface.

Or you can create 3 contact forms, each slightly different, such as having the subject “Web: Job1” on one form.

But it would be nice to have a tag which has the name or URL of the page on which the form was filled out.

link = link.replace(/%3Cbr(%20)?(%2F)?%3E/ig, “%2C%20”);

You can see above that my “less-than-symbolBR /greater-than-symbol” markup got executed instead of escaped so it would be legible.

It’s not hard to understand once the context is established as being for WordPress internal use. But “link to pages” can have several meanings, so maybe something can be added to the plugin’s description which makes clear whether the plugin requires theme alterations, or how the effects of the plugin can be used. Installation tab just says this can be installed as a plugin, but other pages don’t say what the effects will be nor where they will be visible.

Nope, does not answer my question. I was thinking of “link” as having the meaning of an “A” tag’s URL linking to a destination in the Web. It sounds as if you’re using “link” to refer to some WordPress data structure… which means the plugin’s description is even more ambiguous than I thought.

ToniBask, thanks for mentioning the typo. The “images_ids” typo is still present in the shortcodes examples.

Thanks, I had not noticed that is WordPress.com documentation. But the conflict between NGG’s old slideshow shortcode and other slideshow shortcodes remains. Because NGG’s slideshow shortcode is being deprecated, it would be nice if NGG would avoid registration of the shortcode if a shortcode is already registered. … not that there is any reliable order of registration and thus the behavior is unpredictable.

No, I did not use report-bug — I know that tool existed, but couldn’t find it when following the “Support” links and reading the instructions in this forum.

Yes, I know editing core is naughty. But sometimes you need to plug the hole which is sinking the ship because you can’t weld the hull until you get to port.

And I finally noticed the mention of wp-config in that Configuring_* page.

Resolved. wp-config is good enough.

There is no slideshow shortcode in WordPress by default.

There is a slideshow shortcode listed here:
https://en.support.wordpress.com/shortcodes/

It’s too bad that there seems to be no way to see which shortcodes have been registered with WP by which plugins. This topic marked as resolved, because it seems to be due to an interaction between NGG and something else. (I am aware that WP itself also has a slideshow shortcode, so there is a generic conflict issue out there.)

I have seen this same error message randomly appear for a different plugin, so there seems to be something more wide-ranging going on.