Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter kendhal

    (@kendhal)

    You can take your FYIs, wrapped in senselessness, and keep them for yourself. Your reply is comparable to a waiter in a restaurant giving a similar response to a customer who complains about a terrible meal. What you probably fail to understand is that the customer later walks down the street and sees that the restaurant has closed.

    The latest WordPress update broke Woo’s original paid-for PayPal Express plugin. My dashboard asks me to download this plugin instead. But upon uploading your plugin, it does not work either. Confusing? Of course.

    Woo stated they are moving away from the paid-for plugin, yet my dashboard and the emails I get from Woo ask me to renew the plugin for around $50. Confusing? Of course.

    What is equally confusing is:

    A. Woo moving to a free plugin with no communication about this to me, their customer.
    B. The free plugin being downloadable from a non-branded Woo site (this site) and looking basic, with a two star review and an unhelpful author.
    C. No clear link as to how this plugin links with Woo. I mean, who are you? Are you Woo? It seems not. How come you have ended up being promoted on my dashboard through Woo, and are apparently responsible for the success of my website? As such you put yourself directly in the path of customers such as me.
    C. The fact that Woo, a seemingly professional outfit, is letting this happen.

    I foresee Woo coming to an end soon. Shopify has it right. I called them on the phone and got to speak to somebody straight away. They are incredibly helpful.

    Woo has a history of breaking things following updates. This just adds to the absolute nonsense. I’m wasting no more time on this. Shopify, here I come.

    Your stylesheet has reverted back to how it was. I don’t know how.

    Follow the steps I gave before.

    Make sure you flush any caches you may have. And flush the cache in your browser (for Chrome: settings > history > clear browsing data and then tick every box and remove everything from the beginning of time).

    I want to be seeing those cheeky little icons appearing back on your site! Let’s liberate the code and get those blighters out for the world to see and to click on.

    I know it’s a nuisance, but when it comes to websites it’s never easy. It’s like walking across a beautiful English field (I’m English, I have no idea what fields in other countries are generally like but I’ll go with ‘very similar, if not the same’) in summer and not standing in sheep dung; the journey is amazing but along the way you’re going to get distracted by stuff you really would rather not deal with.

    Effblog – I still see the issue as you haven’t made the changes I suggested. How are things?

    Hey, effblog!

    If you go here you will see the stylesheet in your site for the social media icons in question. To find the file within WordPress, go to Plugins > Editor and choose the Simple Social Icons from the dropdown at the top right. To the right of the screen you will see the files associated with the plugin.

    Find the style.css file, open it and then you will see what you saw when you clicked the link above.

    Select everything within that file, delete it and paste this in (I’ve just replaced every instance of ‘fontello’ with ‘ssi-icomoon’:

    @font-face {
    	font-family: 'ssi-icomoon';
    	src: url('../font/ssi-icomoon.eot?78492063');
    	src: url('../font/ssi-icomoon.eot?78492063#iefix') format('embedded-opentype'),
           url('../font/ssi-icomoon.woff?78492063') format('woff'),
           url('../font/ssi-icomoon.ttf?78492063') format('truetype'),
           url('../font/ssi-icomoon.svg?78492063#ssi-icomoon') format('svg');
        font-weight: normal;
    	font-style: normal;
    }
    /* Chrome hack: SVG is rendered more smooth in Windozze. 100% magic, uncomment if you need it. */
    /* Note, that will break hinting! In other OS-es font will be not as sharp as it could be */
    /*
    @media screen and (-webkit-min-device-pixel-ratio:0) {
      @font-face {
        font-family: 'ssi-icomoon';
        src: url('../font/ssi-icomoon.svg?11995952#ssi-icomoon') format('svg');
      }
    }
    */
    
    .simple-social-icons {
    	overflow: hidden;
    }
    
    .simple-social-icons ul {
    	margin: 0;
    	padding: 0;
    }
    
    .simple-social-icons ul li {
    	background: none !important;
    	border: none !important;
    	float: left;
    	list-style-type: none !important;
    	margin: 0 6px 12px !important;
    	padding: 0 !important;
    }
    
    .simple-social-icons ul li a {
    	border: none !important;
    	-moz-box-sizing: content-box;
    	-webkit-box-sizing: content-box;
    	box-sizing: content-box;
    	display: inline-block;
    	font-family: 'ssi-icomoon';
    	font-style: normal !important;
    	font-variant: normal !important;
    	font-weight: normal !important;
    	line-height: 1em;
    	speak: none;
    	text-align: center;
    	text-decoration: none !important;
    	text-transform: none !important;
    	width: 1em;
    	-webkit-font-smoothing: antialiased;
    	-moz-osx-font-smoothing: grayscale;
    }
    
    .simple-social-icons ul.aligncenter {
    	text-align: center;
    }
    
    .simple-social-icons ul.aligncenter li {
    	display: inline-block;
    	float: none;
    }

    Hope that helps!

    I owe you apology – it’s all good. I had the following in my functions.php, which I removed and it sorted the issue. Clearly, this conflicts with the updated version, but I don’t need it anyway:

    //* Do NOT include the opening php tag
    
    add_filter( 'simple_social_default_glyphs', 'custom_simple_social_default_glyphs' );
    function custom_simple_social_default_glyphs() {
    	$glyphs = array(
    			'dribbble'		=> '',
    			'email'			=> '',
    			'facebook'		=> '',
    			'flickr'		=> '',
    			'github'		=> '',
    			'gplus'			=> '',
    			'instagram' 	=> '',
    			'linkedin'		=> '',
    			'pinterest'		=> '',
    			'rss'			=> '',
    			'stumbleupon'	=> '',
    			'tumblr'		=> '',
    			'twitter'		=> '',
    			'vimeo'			=> '',
    			'youtube'		=> '',
    		);
    
    	return $glyphs;
    }

    Agreed, kwill2000.

    I have even installed on a fresh install of WP on a new test site and the problem arises.

    Boo!

    Clearly a bug in WordPress. I’ll wait for an update as opposed to messing about in my browser settings – like I have time for that!

    Thread Starter kendhal

    (@kendhal)

    Thanks, Wayne.

    Email sent.

Viewing 8 replies - 1 through 8 (of 8 total)