Bego Mario Garde

Thank you for your feedback. I just released a new version which takes care of the error handling, if no exceptions were set. Hope this solves your issue.

Best regards, Bego (@pixolin)

Hello mdawg32,

I just release an update of the plugin which adds a settings field in which you can set CSS classes of sections, that should be excluded. I think this is a cleaner way to handle the conflicts. I also added .accordion a[href*="#"] as an exception to handle the conflict with Bootstrap’s accordion. I hope that helps.

Kind regards, Bego

Hello mdawg32,

thank you for your feedback. According to the documentation, Bootstrap uses anchor tags for their accordion, which conflicts with the animation of this plugin. I’ll try to find a solution to exclude the Bootstrap anchors in a future release of the plugin.

Best regards, Bego

I would recommend to Read The Fine …?documentation first and take a look into the examples the plugin provides in your back end at wp-admin/admin.php?page=shortcodes-ultimate-examples

I’m closing this thread due to inactivity.

Thank you very much for your feedback and sorry for the inconvenience.

I wasn’t aware, that Woocommerce uses anchor tags for tabs on their product pages, but fixed it now by adding another exception for all anchors starting with #tab on pages where the body class contains .woocommerce.

Adding another settings field for additional CSS classes certainly sounds like an interesting idea and I’ll try to implement it in the next version.

Just installed Spacer, WPi Designer Button and WPi Easy Button Shortcode, but the anchor icon is still visible and works as expected. Did you try to clear your browser cache or use another browser? Is there an error message if you open your browser’s developer tools?

Of course you can just add the shortcode yourself. The shortcode is called sta_anchor and takes two arguments, id and (optionally) class(if you want to add your own CSS class to change the layout). It would look like

[sta_anchor id="summary" class="anchor"]

which then will be rendered as e.g. Anchor: summary in the front end (depending on your settings).

Sure! Here is a screenshot showing the toolbar of the visual editor.
The red arrow points to the anchor icon.
(You can also see an anchor shortcode that was placed into the content field with an ID “test”.)

Thank you for your feedback.

I updated the plugin and added a link on plugins.php to make it easier to spot the settings section. Hope that helps.

The plugin indeed has no own settings menu, but extends the existing WordPress menu Settings in the submenu Reading at wp-admin/options-reading.php (you should find the settings at the bottom).

The shortcode which is inserted when you add an anchor while editing a page or post will get replaced by the appropriate HTML in the front end. It will get rendered according to your own settings.

Hey Edi,

thank you for your kind feedback. I’m happy you like it.

Best regards,
Bego

I get the same error on a fresh, plain vanilla WordPress 4.4 install with all plugins (including “Hello Dolly”) entirely removed and Twenty Fifteen activated. Therefor I doubt the error message comes from a plugin conflict.

It’s also somewhat disturbing that your plugin includes older files with a tilde (~) (readme.txt~ and wp-qr-code-generator.php~).

Best regards,
Bego @pixolin

That’s awesome! Thank you very much.

Thanks a lot for your immediate response.
As always, you are simply awesome.

@shapeshifter 3:
You don’t seem to get my point. I am fully aware, Twenty Sixteen will be the default theme for WordPress 4.4 which hasn’t been released yet. My point is though that a theme, which is available to the public should also work with at least the latest released version of WordPress or should at least show some information why it doesn’t work with the current version of WordPress.

People trust in the WordPress repository as a source of working themes and plugins. Currently this theme doesn’t.