@Shashank Shekhar
LOL: well, shows how long it’s been since I looked at Shareholic. Used to be on all our sites, and then they had some horrible down time which used to slow down our pages. Moved to AddThis for most of our sites, and has been very consistent. I think we had to hack it to make it “async” but there is a note from me about that someplace in the forum, if anybody cares 🙂

Actually, if you’re using mod_pagespeed and caching on your server, then (at least in our case), our images load faster via local cache after the first visit. And you have no control over the issues you’re having – you can’t change the URLs as used by Photon as the CDN likely uses the ?= for cache control to manage updates automatically.

Always a trade off on that stuff. And you would need to do some actual tests on “page load speeds” for the images to see how that works.

In our case, our dedicated server with APC and mod_pagespeed was faster than Amazon’s CDN after first load, unless somebody happened to be in a really far away country.

Your mileage may vary, obviously. But only way to get around the issues with outside sites impacting your rating, is simply not to use them 🙂

You might have a wait. Not everybody who is on the forum has time to fix your server for you. Your first chore would be to read through all the posts in the PageSpeed topic where many folks, including myself, have provided a wealth of FREE advice on how to optimize your server, pagespeed, caching, htaccess and set your server settings properly for gzip/deflate, time to live headers, etc.

The “tagdiv speed booster” plugin is only designed to help with issues of loading js and css files in the most efficient manner for the theme; it doesn’t do anything for your server side caching, account speed on the net (response time), gzip/deflate, expiration headers, or image compression. Put another way it’s not a “config file” for your server, it’s preset to speed up the theme, rather seamlessly in most cases. While you can add to it, if you need to have an additional plugin or something “optimized” for loading when theme pages load, it will NOT fix issues on your server or the content you upload.

Advice would be to first optimize your site content such as using GTMetrix to check your site for server side elements which need to be addressed FIRST, then move on to elements which can be addressed via htaccess, optimize images, and the like. Do all your checks with mod_pagespeed off as this caches elements while you’re working on things. Set the tagdiv speed booster last (only edit it if you understand what you’re doing); then when you have a decent setup, then switch on mod_pagespeed.

However, as noted in the PageSpeed topic, gzip/deflate, expires headers, and the like are good for 20 points all alone. Most common issue if your score is below 80 desktop.

Also, remember this forum provides theme support from the developer, not server management support. You need to learn to manage your server and hosting setup, and this is necessary regardless of what theme you run. So, unless you address those issues first, then the elements to fix in WordPress will not be very effective.

I’m sure Marius will be happy to help with questions on the td_speedbooster plugin included with the theme, but you really should read through the PageSpeed topic since I’ve provided a wealth of advice, and how-to elements there which are critical to optimizing your site — including my own mod_pagespeed settings!

• This reply was modified 11 years by simchris.

Always glad to help 🙂

I’ve been tweaking PageSpeed on a daily basis since we setup our new web server last December (or rather, I started last year on this topic, but then ran into needing new web server in order to run mod_pagespeed). We run a mix of both WordPress and old-school shtml sites, and so it’s been a challenge to optimize some things for both, especially on our main business website where we have 15 years of static content, wordpress ‘blog’ and then new area for content using wordpress, plus ecommerce area, all on one domain. Fun times! 🙂

I’m super happy with Newspaper, as the devs have been one of the *few* WP devs who understand that it’s not good anymore to have 12 js files and 5 css files linked from every page. One theme I looked at the other day “required” a child theme, and had 15+ js/css files, and one loaded from the child theme not the parent theme. Really nice theme, but very badly architected for modern PageSpeed.

So, in case I haven’t said so lately to Radu and co. BRAVO!!!!!!!!!!!!

• This reply was modified 11 years by simchris.

Well, in my own testing photon did NOT work properly on numerous fronts as it’s not the best way to manage optimization and placement, at least on our sites. It’s loading those images off wp.com and not your own site, so it will be slower and not managed locally by your own site/server speed. A lot of that stuff is for newbies who don’t want to dig in and manage their own site; it’s not for power users at all!

If you look through my posts on this topic, try instead
1) changing default setting for WordPress which uses server side imagemagik modules, change in functions.php by adding directive to set quality at 60 (default is 90)
2) use the plugin for auto creating featured images
3) use the plugin to auto resize images from featured image

These help to manage correct sizes, optimized images without going through another server (wp.com), and I don’t get warnings about any image issues from PageSpeed.

It usually takes awhile to show up; and also won’t work if you have a conflicting plugin running. You may want to open a new support thread since your query has nothing to do with “version 1.0” of the plugin for the theme 🙂

• This reply was modified 11 years by simchris.

Some elements in child them won’t over-ride certain custom modules, so to “hack” a new feature into an existing module (not a page template), it requires hacking the parent, unfortunately.

@thomaspe
obviously if you want that functionality now, why not just buy the plugin?

I personally don’t need the little graph element, but some people may find that cool.

I still really like this format: https://wordpress.org/plugins/mashsharer/

I have not used Masharer as originally it required a third party site to track the combined shares, which was dumb but simpler from an API point of view. The author is re-writing the plugin (mid Aug. 2014) to not use the third party site for the total tracking, so keep an eye on that plugin as possible awesome solution for the “Mashable style” total + clean buttons look. The *new* version will have support for the top 20 social networks, which is very cool.

Just some thoughts re this topic 🙂

I’ve used both shareaholic and addthis, and both have worked great.
I kind of prefer Addthis, myself, but both do the same thing really, just with different “styles.” With shareaholic I got tired of the gimmicky pop up thing, which was cool 3 years ago, but not as much now.

@rparlier
You may find it useful to read through the theme documentation found from link top right of page for this forum, as it explains about this in detail, along with a lot of other great info on using the theme:
https://forum.tagdiv.com/newspaper-documentation/

we use APC along with mod_pagespeed 🙂

Hi, I have no idea, as I’ve not used that element with the theme myself. Likely you’ll need somebody more experienced on that modification to chime in, or wait for Marius and Radu, etc. to be back on Monday their time. You could keep messing with it, but from first blush I would guess you forgot to add the style class to each item:

<li class="menu-item">

Hope that helped 🙂

(I don’t work here; just helping out!)

Google has only been doing “responsive” ads for a very short time (2014), so they are still figuring out how to make them work better on different layouts. One would presume a text box could resize, but since they never know the “layout” they cannot safely set 100% widths to some spaces, hence why you often still need to set a “hint size area” …

I think they are only responsive in the sense that they are not fixed sized graphics, but they are not responsive in the same way that one expects.

I went through that earlier this year, and went oooooohhhhh….. okay. Makes sense once you get the limitations of their ability to guess the layout space 🙂

Hi, the buttons look fine *except* the text at bottom of each button is partially visible/chopped off when I view in IE11/Win7-64. On Chrome/Win7-64 I only see the solid color buttons and no icons/letters and on hover the compress to half-width. So, something not quite right on those.

Oh, on Chrome if I expand the window to “full width” the icons are at top of page vs bottom of article and have the icons and text. Then if I shrink screen to my normal reading width I see the same issue with the icons, but text mostly off the button. If I switch to iPad portrait size, only solid boxes of color at bottom of article.

So … not working for me at this point, I would have to say … sorry! 🙁

If you use the responsive ad code from Google for your AdSense ads they will be responsive. Meaning, a different size ad will be loaded depending on viewport. Ads do *not* resize on the fly; meaning, if you shrink the browser viewport, the ad does not reload to new size as Google doesn’t allow ad “reloads.”

I have to remember how to do this each time I upgrade the theme, and so it wasn’t top of mind first time I looked at it. Had to “retrain my brain” on what I did last time 🙂

Glad I could help !

(and again – I don’t work here; just helping out to pay forward all the help I’ve gotten from others over the years — my thoughts, ideas, and suggestions do NOT represent TagDiv folk … )

Sometimes it’s also something stupid like the relational paths are not set properly in the plugin so it can’t find its pieces and it can find path on localhost but not on server.

Note you can buy copy of VC to get direct support for issues with Visual Composer.

Likely you will need to locate the file which has the login widget code and edit it to put in generic links on that dropdown, or add query if the links are unique to each user.

If you look in your theme folder, under includes > widgets > td_login_widget.php

you would likely add the links there.

e.g.,

            echo '<ul class="top-header-menu td_ul_logout">
                    <li class="menu-item">
                        <a href="#" class="td_user_logd_in">' . $current_user->display_name . '</a>
                    </li>

                    <li class="menu-item">
                        <span class="td-sp td-sp-ico-logout"></span>
                        <a href="' . wp_logout_url(home_url()) . '">' . __td("Logout") . '</a>' .
                        get_avatar($current_user->ID, 20) .
                    '</li>
                  </ul>';

Always good to “explore” the files and folders for the theme to look at what is there, as this is often the starting point for any special customizations not built into the theme itself. Most of the stuff “included” onto pages/posts that are not main templates are found in the /includes/ folder.

Hope that helped! 🙂

I think the admin panel uses the default fonts of WordPress which are now Open Sans. You should be able to just delete the one block having to do with writing the google fonts into the head of the document, which have nothing to do with the admin interface fonts.

Hmmm….. v4 changed some stuff for more loops ….. hm…..

try only commenting out line 48 in functions.php

// wp_enqueue_style('google-font-rest', td_global::$http_or_https . '://fonts.googleapis.com/css?family=PT+Sans:400,700,400italic|Ubuntu:400,400italic|Open+Sans:400italic,400|Oswald:400,700|Roboto+Condensed:400italic,700italic,400,700'); //used on menus/small text

No idea. Not part of theme. Likely you will want to hire a programmer to help customize accounts and how their user data shows up in custom menus. Might be a WPMU plugin for that.

• This reply was modified 11 years by simchris.

Yup. Web server is different from a local PC since you don’t control the PHP settings, security settings, or the order things load, or external async elements.

You can’t presume anything that works on localhost will work on web; and fact that it doesn’t would likely cause one to reconsider use of “brilliant” in this context.

My experience has been – test on the web with the actual server. Some plugins are not tested against say an nginx environment vs an apache environment, or with timing of how things load in production environment on server, even though one would assume if it works on localhost or virtual machine it should work on the web, not always so.

I’ve had a lot of great plugins which break on version xxx of WordPress, and can never be used ever again. Also note that the theme has been optimized around some of the pending changes for WP 4.0, and not all plugins have done that yet.

But you asked me to look at this, so just giving you my thoughts. If it doesn’t work on the server, you need to figure out what is loading before it that breaks it.

• This reply was modified 11 years by simchris.

Upshot: not all plugins work with all themes, and sometimes it’s due to the plugin author not properly escaping something, or doing a query that isn’t reset when done, or which duplicates a call to something like bootstrap code or jquery, etc. Or, worst of all, uses a non-unique function call, which is already used by the theme or bootstrap or other common plugins.

My rule of thumb is, I try to get a plugin to work three different attempts; then move on to something which isn’t a piece of crap.

(Just my four cents …) 🙂

• This reply was modified 11 years by simchris.

My pleasure. I ended up not using cache plugin, since mod_pagespeed does great job in combination with server-based cache since it doesn’t have to run through the php system or wordpress code as a caching “plugin” does. You *can* use one, but I found it didn’t help much really and caused too many issues when I need to update a page or template.

Trick is knowing how to clear the cache on server when you go to update the theme to clear out everything before and after upgrade so web browsers can “see” the new versions of the style sheets.

But I think you’ve got it 🙂

I did pretty much the same thing; basically using the Gill Sans stack; and simply replaced the stacks in style.css. I didn’t need to change the loop files, since I think those call the “default” font, so if you change that in styles.css I think all you need to tweak each time the theme is updated is just functions.php and styles.css and leave rest alone (unless I’m wrong … ) 😉