SuperEnduro
Forum Replies Created
-
Okay, have submitted a ticket and thanks!
Now that makes perfect sense (didn’t think of that…) but….. doesn’t work for some reason?
We tried it for effect – initially as/is (via cut and paste) straight into Appearance > Edit CSS. We also get a message “Heading (h3) should not be qualified.” So of course we tried removing the h3 reference and re-trying but still no change. Hmmm
Previously we have made very minor changes using this method without an issue. We do use an old theme iNove Version 1.4.6 as our base but everything else works just fine regardless of the theme’s age!
Any other thoughts?
Done!
Thanks! We’ll look at that shortly. Is it a more simple option within the Pro version?
On this very subject, but with a slightly different request….We are using WPtouch (free) is it possible to remove the sharing icons bar shown beneath posts completely?
Or, as a compromise (if it can’t be removed), can we make it work properly? e.g. make the link to Twitter actually connect to the Mobile Twitter main screen – we currently get a Twitter message advising “that page doesn’t exist…etc” and the choice of Shares is wrong for our usage – Del.icio.us / Newsvine etc
Haven’t seen anything within the plugin that allows this to happen so far…
We already use AddThis which works fine on both the desktop view and the mobile view, so we effectively have duplication within the mobile view. Turning it off would be best for us if that’s possible?
Thanks in advance
Hmmmm Right, today’s work around until we go and look in detail and correct those little glitches (including the one you marked thanks WPyogi) is that by simply moving the calendar to the South_Sidebar instead of the North_Sidebar, it’s displayed correctly in Firefox (and all others). It’s not the appearance we really want, but that will return in due course after the other corrections. Thanks again for the quick insight.
Yeah, that could make sense couldn’t it. Especially as the ‘Add This’ plugin has also just been upgraded. Seems strange that only Firefox suffers, but a little beyond our knowledge there….. We’ll sort those other little typo errors out whilst we there! I imagine we can go back a version of the plugin and see if that solves the problem then. Give us a little time and we’ll see. Thanks so far.