kendallq

A follow up. The author has added back support for Bootstrap 2.3.2, which should save 99% of users. But I would have preferred that consideration from the get go and I still would not continue with the plugin. I know the author works hard on this and don’t doubt that many find it still a great plugin. But I’m seeking a gentler approach to prevent widespread live site mess ups.

I’m not asking for the displacement of any responsibility. I’m responsible. However, I don’t want to continuously be forced to change development forks based on your development cycle. So I reverted to my backup, I’m removing the short codes and implementing pure bootstrap and then figuring out how to install bootstrap 2.3.2 and then properly creating a copy of my site on my development bench to examine the path to 3+ should I want it. What was a convenient plugin, has become a ball and chain that when stuck on the original fork, without any updates, could become a security risk.

You are free do develop as you want. I found it odd that with a plugin populated with so much advertising on the Dashboard, that you wouldn’t have used that area to give some notice. And in the plugin area where you advertise iControl, you couln’t have said “Upgrades to new fork of Bootstrap, which may require significant changes to your coding especially if you are using the functionality of 2.3.2.”

Sure you have to make a buck, but a little care in cultivating your free user base, would seem a more wise approach. But even with notice in the WP plugin itself, I would had to have left anyway. Once I saw that you will be auto upgrading, in the future, the thought of losing control over backups and revisions was enough for me to want to stay far, far away.

Your style is very invasive. This should have been a new plugin, not an update because you totally forced people to choose a major new fork on bootstrap. This would break nearly every blog and that is behavior that warrants 1 star. Not even an option to let users decide if they want the new or old fork. Nothing graceful, nor respectful that you could be throwing peoples sites into severe disarray. To quote you:

Version 3.0 of Bootstrap is hugely different and I spent a LONG time reworking much of this to try to ensure they work with Bootstrap 3.0.

A more considerate approach would have not forced what you yourself say is “hugely different” upon droves of people totally abandoning what was the only way to go just 10 days prior. I was on the Bootstrap site and it was all about the other fork 11 days ago. It seems uncontenable that you think any site would be ready to completely change so quickly. And to a brand new fork that you yourself admit is buggy. Bugs don’t belong in production code. You offer a dropdown selection to select other Bootstrap OPtions (all with version numbers) so it seems odd that you would not give the option to use the fork that all sites are depending on. This would have allowed us to test and see if bootstrap 3.0 was ready or going to be compatible.

I stand at 1 star, if I’m the only person that feels this way I might reconsider but I believe you have abandoned your users for the sake of novelty.

I really wish I understood that this would have broken even more than short codes. All of my accordion implementations are broken. I wish I knew how to go back.

Hi I saw your post and then found something that works for me. Turns out there are a lot of ways to order the images. As evidenced here;

Link to Codex

But I just wanted to define an order of this image and then that one etc. Here is what I did first:

<!-- BEGIN CAROUSEL           ================================================== -->[carousel exclude="489,491,529,530,532,536,541,650,3828,3829,3869,3870" orderby ="name" interval="5000" comments="0" file="0"]

<!-- END CAROUSEL           ================================================== -->

I added orderby ="name"

which you can see by the codex page I referenced orders by slug. There is a “Slug” field for each image. I simply prepended each image in that carousel with a letter (numbers aren’t advisable), so the first image I wanted to show up now has a Slug starting with “a-” and the second image in order is now “b-“.

Worked like a charm for me. Hope for you too!

Thanks. Unfortunately, the solution only produced memory errors and after raising the memory to 700M it just produced a white scree (with no error). Looks like I’ll have to search to find the right plugin combination. ??

Hi! There were a few unrelated JS errors and I’ve cleared them.

Here is effectively what is in the event manager template file:

<?php
$glossary_path = WP_PLUGIN_URL . '/' . 'enhanced-tooltipglossary/';
wp_enqueue_script('tooltip-js', $glossary_path . 'tooltip.js');
wp_enqueue_style('tooltip-css', $glossary_path . 'tooltip.css');

global $EM_Event;

/* @var $EM_Event EM_Event */

echo $EM_Event->output_single();
?><!-- #test --><?php

?>

I see the “test” comment in the page source so I know my child template and your code is making it to the page. Have I done it wrong?

That didn’t produce any result.
I tried :
$glossary_path = WP_PLUGIN_URL . ‘/’ . ‘enhanced-tooltipglossary/’;
wp_enqueue_script(‘tooltip-js’, $glossary_path . ‘tooltip.js’);
wp_enqueue_style(‘tooltip-css’, $glossary_path . ‘tooltip.css’);

In a few different ways, in my child template functions.php, and in a child template of the page itself. I’m sure the code was making to the page but no tooltips were produced like on other regular wp pages.

I hope the plugin authors would listen to you on that. They obviously don’t know what a toll their plugin takes in the real world. Sure sometimes things work great but other times it damages the blogger user relationship.

The problem is that all of the social icons are little data miners (that tacitly make money for the social media companies) and yet they don’t have the respect to keep their data centers and network operating at a sufficient grade of service to always make pages load well. There poor (greedy) performance is amplified by the number of icons you show. If several are experiencing problems your site can come to a screeching crawl!

I recommend to all of my clients to get rid of plugins like this and opt to put locally served icons and hard links the social sites. It is a shame that the plugins don’t allow you to control this or do what you said and have a fail safe.

Bloggers work hard and create original and valuable content and they should revolt against the social media companies that totally use them and have little regard for great gift we give them.

They should pay you for putting those social beacons on your site. You get money when you put ads on your site so why not some compensation? Even when those beacon icons load fast they still cost you. Unless you have a sweet deal, you pay for hosting right? Bandwidth costs, server CPU time costs. Just because there is a giant remote element, doesn’t mean your server is not impacted. When you consider all the beacons on all of the pages the world over, those little beacons amount football fields full of servers paid for by bloggers all doing work to mint metric data cash for someone else.