Search Results for 'move bottom ad'

hi,
in the latest version of the theme we have moved the google analytics code from bottom next to the header

Thanks for you message.
Radu A.

Hey Emil,

Thx for your awesome support!

to 4th. I think id be really helpful to support continious loading for similar articles since it is very important to keep people on the page by giving them fitting recommendations.

I just worked 2 nights tweaking the theme for social performance. Gonna run tests tomorrow. I added a second social sharing bar, which is fixed to the bottom on mobile devices. I moved the comments ahead of the similar articles and integrated facebook comments instead of wp comments. Reduced font a little bit. Also I added a feature to hide the comments and show them by clicking the show comments bar. you may want to take a peek at http://www.dailycat.de/unglaublich-vor-welchem-tier-sich-diese-starke-katze-fuerchtet-514/

Is it a lot of work to integrate the continious loading into the similar articles?
May be also a good feature for the theme to have a 4/5 option in the similar articles interface “random” and a second trigger continuous loading.

I really appreciate your fast and helpful replies.

Best from Germany, Manu

hi,
lets start from the begging, the reason way google is giving that “Remove render…..” is because when the source of the site get downloaded and loads into the browser it find resources like css and javascript files, font file, etc and the browser stop the downloading of the page to start downloading the other files (css, javascript files) and google says that is better to download the source of the page first and at the end to download other resources.

now that we found what happens, moving the css and javascript code at the bottom of the page – I think ???- it can be done by doing something like :
keep the style.css of wordpress, but put all the code in another css file, then
read the file and put the readed content between <style> and </style> in the
footer of your site (probably thru the use of hooks). do the same for javascript
files(need to use the <script> and </script> tags).

Now imagine that for every plugin that have css files and/or javascript files you need to do this reading of files and pasting in the bottom of the page. Is hard to do this but will insure that message “Remove render …..” will disappear.

==== about speed buster
all that td-speed-booster is doing is to move the javascript files from the header of the page to the bottom of the page. in theory this will have to increase the speed in google pagespeed application, but in your case seems that it fails, really don’t know way, this has to be checked.

Thanks for you message.
Radu A.

hi,
I see the problem,
you can try this css.it will only hide from view the home link, but the link is still there. I cound not remove the link and make mega menu to work , sorry about this:

#td-top-menu ul.sf-menu li:first-child a span{
 display:none ;
}

#td-top-menu ul.sf-menu li:first-child a {
  border-bottom-color : #ffffff;
  cursor: default;
}

here: http://screencast.com/t/YdKuPOh3i8

Thanks for you message.
Radu A.

Just for reference, the code I posted in the PageSpeed sticky topic – which can be added to bottom of functions.php file. Your mileage may vary 🙂

function remove_cssjs_ver( $src ) {
    if( strpos( $src, '?ver=' ) )
        $src = remove_query_arg( 'ver', $src );
    return $src;
}
add_filter( 'style_loader_src', 'remove_cssjs_ver', 10, 2 );
add_filter( 'script_loader_src', 'remove_cssjs_ver', 10, 2 );

• This reply was modified 12 years by simchris.

@orcn

gzip/deflate is managed at the web server level – it needs to be running for your hosting account. This allows the web server to automatically compress everything sent by the web server from your site to the web browser. This alone is good for 20+ points. This is the #1 thing which should be addressed. Ideally your web host should have this on for your account. If they won’t enable it, move to another host who will!

If you look at my posts there is an example of the .htaccess settings that I used for
the “expiration headers”

For images:
1) you need to use a compression plugin, like smush.it or similar (see comments from others in the thread); this will optimize all the thumbs created by WP and the theme
2) upload well compressed images (e.g., 25-40kb max, not 150kb or 700kb — unless you’re doing some kind of photo/portfolio site where quality is first concern)
3) consider changing the compression level by default in WP, which is done in the functions.php file at bottom using the code I’ve suggested in my posts — setting it to something like “60” vs the default “90” (I think), will cut the size of the thumbs by a huge amount.

For my particular brand of magic, try putting this at the end of your .htaccess file:

AddType text/javascript .js

# BEGIN Expire headers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 2500000 seconds"
ExpiresByType image/jpeg "access plus 2500000 seconds"
ExpiresByType image/png "access plus 2500000 seconds"
ExpiresByType image/gif "access plus 2500000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2500000 seconds"
ExpiresByType text/css "access plus 700000 seconds"
ExpiresByType text/javascript "access plus 700000 seconds"
ExpiresByType application/javascript "access plus 700000 seconds"
ExpiresByType application/x-javascript "access plus 700000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>

<IfModule mod_headers.c>
    Header unset ETag
</IfModule>
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>

NOTE: if you use pingback or post by email, don’t put in that last 3 lines, as I do this to keep spammers from posting comments via pingback even when comments are off (!).

The above assumes your web host is running Apache, and not IIS, or nginx or other. If so, you might have to tweak those for your particular host. Apache is the most common, however.

Also: make backup, via FTP, or your hosting panel fileManager of your .htaccess file first; then if your site doesn’t load with the new elements, put back your original version.

Hope that helped.

• This reply was modified 12 years by simchris.

hi,
in : http://screencast.com/t/PeGVUjNb

change :

/**
     * More stories box
     */
    if(tds_more_articles_on_post_enable == "show") {
        //adding event to scroll
        jQuery(window).scroll(function(){

            var cookie_more_box = td_read_site_cookie('td-cookie-more-articles');
            //alert(cookie_more_box);

            //setting distance from the top
            if(!isNaN(parseInt(tds_more_articles_on_post_pages_distance_from_top)) && isFinite(tds_more_articles_on_post_pages_distance_from_top) && parseInt(tds_more_articles_on_post_pages_distance_from_top) > 0){
                var set_distance = parseInt(tds_more_articles_on_post_pages_distance_from_top);
            } else {
                var set_distance = 400;
            }

            if (jQuery(this).scrollTop() > set_distance && cookie_more_box != 'hide-more-articles-box') {
                jQuery('.td-more-articles-box').addClass('td-front-end-display-block');
            } else {
                jQuery('.td-more-articles-box').removeClass('td-front-end-display-block');
            }
        });

        //adding event to hide the box
        jQuery('.td-close-more-articles-box').click(function(){

            //hiding the box
            jQuery('.td-more-articles-box').removeClass('td-front-end-display-block');
            jQuery('.td-more-articles-box').hide();

            //cookie life
            if(!isNaN(parseInt(tds_more_articles_on_post_time_to_wait)) && isFinite(tds_more_articles_on_post_time_to_wait)){
                //setting cookie
                td_create_cookie('td-cookie-more-articles', 'hide-more-articles-box', parseInt(tds_more_articles_on_post_time_to_wait));
            }
        });
    }

with this:

/**
     * More stories box
     */
    if(tds_more_articles_on_post_enable == "show") {
        //adding event to scroll
        jQuery(window).scroll(function(){

            var cookie_more_box = td_read_site_cookie('td-cookie-more-articles');
            //alert(cookie_more_box);

            //setting distance from the top
            if(!isNaN(parseInt(tds_more_articles_on_post_pages_distance_from_top)) && isFinite(tds_more_articles_on_post_pages_distance_from_top) && parseInt(tds_more_articles_on_post_pages_distance_from_top) > 0){
                var set_distance = parseInt(tds_more_articles_on_post_pages_distance_from_top);
            } else {
                var set_distance = 400;
            }

            var scrollPosition = window.pageYOffset;
            var windowSize     = window.innerHeight;
            var bodyHeight     = document.body.offsetHeight;

            var set_distance_from_the_bottom = Math.max(bodyHeight - (scrollPosition + windowSize), 0);
            var set_distance_to_stop = 400;

            if (jQuery(this).scrollTop() > set_distance && cookie_more_box != 'hide-more-articles-box') {

                if (set_distance_from_the_bottom < set_distance_to_stop && cookie_more_box != 'hide-more-articles-box') {
                    jQuery('.td-more-articles-box').removeClass('td-front-end-display-block');
                } else {
                    jQuery('.td-more-articles-box').addClass('td-front-end-display-block');
                }

            } else {
                jQuery('.td-more-articles-box').removeClass('td-front-end-display-block');
            }
        });

        //adding event to hide the box
        jQuery('.td-close-more-articles-box').click(function(){

            //hiding the box
            jQuery('.td-more-articles-box').removeClass('td-front-end-display-block');
            jQuery('.td-more-articles-box').hide();

            //cookie life
            if(!isNaN(parseInt(tds_more_articles_on_post_time_to_wait)) && isFinite(tds_more_articles_on_post_time_to_wait)){
                //setting cookie
                td_create_cookie('td-cookie-more-articles', 'hide-more-articles-box', parseInt(tds_more_articles_on_post_time_to_wait));
            }

        });
    }

http://screencast.com/t/zBEmdCdU4

Thanks for you message.
Radu A.

• This reply was modified 12 years by Radu A.
• This reply was modified 12 years by Radu A.

hi,
about the feed, can you try disable all the plugins and try again, some plugins modify the feeds, also the /feed is managed by wordpress and has nothing to do with our theme.

about the duplicate post, use a different page template (with pagination) : http://screencast.com/t/pj0N7d1dTbue.

with the space at the bottom I can help you but only if you remove infinite load, because I can not reach the bottom of the page.

Thanks for you message.
Radu A.

This may not be specific to your issue, but FOUT is a common issue with the trade off between fancy fonts and page load/speed.

This is called “flash of unstyled text” (FOUT) and is a common issue with using Google Fonts (etc.), as they are loaded from someplace other than your own site/server. SO, often the page starts to load, uses browser fonts, then the fonts load from external source (e.g., Google CDN). This is somewhat unavoidable if you’re going for maximum “pagespeed” as not everything can load at same time even when async or using the speed booster beta plugin; many times the loader for such fonts is deferred and moved to bottom of page to allow “above the fold” content to load quickly for a better pagspeed rating — such as with Google PageSpeed Insights).

Often something is slowing page down like a plugin, too large image, or similar, and this “holds up” getting to the font loading.

Solutions typically
1) change order of font loading
2) switch to web-safe fonts only
3) if using CSS over-rides on style sheet embedded in page AFTER main style loads, better to edit style sheet if there is measurable delay between the default style loading and the over-ride (meaning if main style is at 48 and your over-ride is 40; then the 48px still loads first, and then gets over-ride – by not doing over ride and editing core file, it starts at 40px to begin with).

FOUT isn’t too terrible, but it can be annoying.

Some of the above may be only informational to your issue, but I’ve been learning to live with this on some of our sites for better speed.

Got it.. okay, here’s where we’re at.

Your original method DID work. However, because there is an advert and our social media icons plugin in between the bottom of the post and the author box, it didn’t show any differently. I just moved $buffy .= $this->get_author_box(); above the content, and the box appeared above. So your method did work afterall.

However, I need a way to get that author box above the social media icons plugin and the advert, effecively taking priority as the very first thing after the post content.

Any ideas?! Thank you for your help.

Yes r1kay it’s basically this:

function revv(){
   global $post;
   $test_module_inst = new td_module_1($post);
   $review = $test_module_inst->get_review();
 return $review;
}

function content_injector($content) { 
		global $wp_query;
		global $post;	
		$postid = $wp_query->post->ID;                  
		if (get_post_meta($postid, 'top_ad', true) != 'off' ) {	
			//top_ad code
		} 		
		if (get_post_meta($postid, 'bottom_ad', true) != 'off' ) {	
			//bottom_ad code
		}
		 if (is_single()) {
			$share_after_ad = do_shortcode('[shareaholic app="share_buttons" id="4703992"]');
			$related_after_ad = do_shortcode('[shareaholic app="recommendations" id="4704000"]');
		 }

		$review = revv();
	        
		$content = $top_ad . $content . $review . $bottom_ad . $share_after_ad . $related_after_ad;
		
		return $content; 
}
add_filter('the_content', 'content_injector');

By using the code above you can move the review to the top of the post, bottom, after content and before ad, etc.

Thanks for helping me out Radu.

Also you will need to comment out or remove the function that calls the review on td_module_1.php

You can manually move the get review code in td module 1 to somewhere else on the page. It is located in the footer clearfix of the module 1 file. Thats how i added my own social sharing buttons an fb comments box and moved the get next and prev post to the bottom of the post pages.