we would need a link to the site to see what is going on
Sorry – I should have included the link in original post. BTW, I am getting the same results in four browsers.
http://www.marthafbush.com
I don’t know what happened to the above link, but it should have worked. Here it is again.
Martha F. Bush
All the styling causing the problem appears to come from the plugin itself, so I don’t understand why it would works on another theme.
The plugin fixes the width of the content to 30px, it has a right and left padding on the container of 7px on each side, and a right left margin of 5px on each side of the share label
As a result there is no choice for the text but to be split on two lines.
We could override some of that styling to make it fit on one line, but it would be best to first check what options you have in the plugin, or ask the developer as it should be fixed on their side.
If you are unlucky with them come back and we will give you overriding rules.
I can make it work by increasing the container (#sthoverbuttons #sthoverbuttonsMain) width to 35px, and removing the 5px right margin on the label (#sthoverbuttons .sthoverbuttons-label)
Thanks scrambler for your input. It’s greatly appreciated.
I am running the same plugin on three other websites without a problem (the website in question is my wife’s website). Of course, none of them are using the Weaver II theme.
I know you’re right that it could probably be fix via css, but seeing as how no other theme is affected, as well as three other websites, I imagine that the plugin developer is not going to give it a lot of attention. However, I will contact them and see what they have to say. I’ll let you know what they say.
If you have a link to the other site where it works, I’ll check if there is something different.
If the developer does not answer, here are the two rules that you could add to weaver’s Advanced options > Head Section > Custom CSS Rule Box
#sthoverbuttons #sthoverbuttonsMain {width:35px;}
#sthoverbuttons .sthoverbuttons-label {margin-right:0px;}
Hey, scrambler. I used the css you recommended and as expected it did work. So thanks-a-bunch-a-millions. I know it was a little thing by comparison, but as I’m often told with sarcasm from my family and friends, I expect everything to be perfect. Unfortunately, they’re right.
If you don’t mind, I’ll keep this string open for a few days to wait on the plugin developer and come back here and tell you what they said. (The auto response email said they would respond within 48 business hours.) It might help others in the future. Then I’ll tag it as resolved.
Well, I was partially wrong.
There was a weaver rule that was making a difference and it is the word-wrap:break-word property.
Weaver sets the word-wrap property to break words when they do not fit in their space.
The plugin style creates a space that is indeed too small for the word, but if that rule is not on, the word just overflows its space and shows up on one line anyway.
So you can either use the two rules I gave you, or you can use the one below only. They both work.
#sthoverbuttons .sthoverbuttons-label {word-wrap:normal;}
Sir Scrambler – you sound as tenacious as I, just keeping on digging.
Now that you mention it, I’ve seen this word-wrap rule mentioned before about Weaver II. I can’t remember when or where, but have. However, at 70 years old, my memory is not what it use to be.
I think I’ll just keep your original css fix, but make note of this new css in case I need it in the future; possibly for a similar problem.
All I can say is, you are the man! Thank you so much for your persistence.
Sorry for the delay, but I just finished my correspondence with the “Share This” developers. It was silly, to tell the truth. People just don’t take the time to read what others write.
My first email to them said it was associated only with the Weaver II than and that I had tested the site with the four major browsers. Then I told them I had a temporary fix using CSS. They replied that they had looked at the site and there was no problem with the word “Share”, and they provided a snapshot to prove their point. Then they asked me if I was having a problem with any particular browser.
Obviously all three of these points were clarified in my original email to them. So I replied to them in a very stern language, and told them to go back and read my original email. That got their attention, and apologized for their misunderstanding, with the following response:
“Thank you very much to let us know the issue related to Weaver II theme. We will forward this to our dev team so that further action can be taken to overcome the issue.”
Pretty much what we expected. So thanks scrambler for your help. Not only did you care, you provided a fix; which is a lot more than I can say for the Share team.
We can close out this topic with a resolved if you like.
Feel free to close as resolved 🙂
