Search Results for 'update'

Actually … I think this might be due to a caching issue with mod_pagespeed, but still testing. With mod_pagespeed “on” at all, I have issues with the “suggested” flyout, and the styles for the social sharing with tags box breaks.

Will update as I test this for plugin conflict, or cleaning the mod_pagespeed cache, even though it’s NOT supposed to cache anything in the wp-content/theme folder, like a stylesheet.

For those using mod_pagespeed – this is relevant, for everybody else just ignore these minor updates 🙂

I understand Radu, and we definitely do not want to make a mess of this beautiful theme! Keep up the outstanding work and updates as you and the rest of the team see fit.

Philip

Update for those using mod_pagespeed – either on hosting service using .htaccess or self-hosted and using .htaccess to control on/off stuff.

UPDATE for Newspaper 3.5:

do not use these as they break the slide out recommended posts widget.

ModPagespeedEnableFilters move_css_to_head
ModPagespeedEnableFilters combine_css

These settings also appear to cause the “whiteout page” issue with the tagDiv Speed Booster 2.1 plugin, with 3.5.

<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>

However, these minimal settings should *NOT* cause the page to “white out” since whitespace only removes empty spaces, comments are elements best removed anyway, and images and DNS has nothing to do with the Speed Booster AFAIK.

I will have to ping Radu on this issue once they get caught up on the current update cycle to sort out conflict with the speed booster plugin and mod_pagespeed, as obviously they should be able to work together and did so just fine in the 2x theme versions.

More later …

Hi
I’m updating this thread for consistency.

I just upgrade to Newspaper 3.5 and attempting to replicate this, with
Newspaper/includes/modules/td_module_1.php

if I remove the // for author name, it’s NOT printing on the posts although uncommenting on other modules does add the author byline to things like the sidebar modules or the indexes.

                <div class="meta-info">
                    <?php echo $this->get_category(); ?>
                    <?php echo $this->get_author(); ?>
                    <?php echo $this->get_date(false); ?>
                    <?php echo $this->get_commentsAndViews(); ?>
                </div>

e.g.,
http://ga-ga.com/1204/beginning-adventure-space-time-reveals-roots-doctor/

I have tried with tagdiv speedbooster on/off; I have mod_pagespeed off to ensure nothing is being cached; not using Jetpack.

This is CLEAN install of Newspaper 3.5; meaning the theme folder was uploaded as fresh folder and prior 2x folder was not over-written, so no mish-mash of old/new theme elements. No child theme being used.

Any idea why that might not be printing on page? Do I need to enable something else to cause the author byline to print on posts?

————————————

To repeat past posts as an opinion here:

“Byline” is one of the most critical things to all newspaper/magazine sites and should always appear below the title of article, or below the featured image; but typically the author and date are shown together in magazines and newspapers, so slightly annoying we still have to manually enable this EVERY update — look at TIME, or NY Times, or LA Times, or CNN, you will see the BYLINE and date top of every article. SO my big REQUEST would be to enable this by default “ON” and then let people comment it OFF which would be the exception vs the rule.

• This reply was modified 12 years by simchris.

Good job 🙂

Yes, we’ve had a *LOT* of trouble with Yoast SEO 1.5x due to their adding new features for bulk content changes, connectivity to Google Analytics. We are now looking for a more simple SEO tool, as we used to have an inhouse plugin to simply put all the social media and OG tags, custom field stuff in the head, without some of the other shenanigans now included, and adding more complexity and PROBLEMS. With Yoast SEO properly configured with all the extra crap turned off it does help manage a lot of things, and should not hurt pagespeed in the sense that nothing should be loaded externally or custom CSS, etc.

Jetpack however is a dog for speed even though cloud based. And many would disagree, but NOT using it unless you have to speeds up site tremendously. For bloggers it is awesome to add new features, for high content/traffic sites, not so much (in my opinion).

We’re looking at alternatives for a “simpler” SEO tool again, without the intrusive stuff they have been doing. No way to turn off the stoplight on right side of posts, broken google news features in 1.5, etc. Perhaps time to move on …. I will update as I move forward on this topic. 🙂

hi,
thank you for your suggestion
we will discuss this.

thank you for using our theme.

Thanks for you message.
Radu A.

Excellent that fixed my issue.

I dont think the old developer is going to allow me access to their account or provide me with updates. Is there any chance I can get it transfered via themeforest to my account. Or is there any other way if I provide you with the License?

hi,
please backup everything before you update (files and database).
most of the big changes are from version 2 to version 3.
if you upgrade from 1.4 to 1.x (x > 4) you should be ok.

Thanks for you message.
Radu A.

This is a feature I have been looking for diligently. Are you still on track for the update this week?

Thanks for all your help!

@jbenbitez
not sure if you use a dbase optimizer for your site, but one thing I do after any major updates every time is
1) resave permalinks (just because)
2) run wp-optimize plugin to clean up dbase

We’ve been able to lessen the load on all our sites by as much as 20% (we have a LOT of pages) by using wp-optimize regularly, and also editing the wp-config to limit number of draft saves, and longer time to save each.

In our case the “BIG” memory leak was from YOAST. Going backward on one site fixed it, and on another getting latest version.

One client site was crashing until we stopped using AddThis “layers” plugin and cleared the cache about five times (not running Newspaper). GoDaddy hosting on that one.

Anyway – this is just some feedback on our issues- again, perhaps not related in any way to your issue. Often you can look at your site “error logs” to see what is generating an error, as best place to start with this kind of thing.

I’ve tried all Radu, reverting to Yoast 1.4, disconnecting all plugins and nothing has worked. This is a very very very strange thing and started since I updated to 3.4 and also updated Yoast to the latest version. Any help? I can’t publish anything on sites, when I get the to load the back end…

Do you need any admin data? I’ll be more than happy to provide full access to anything you might need, thank you!

Be aware Yoast SEO had a big memory leak issue that raised our server processes by 30x on one of the 1.5x versions; and various other issues. We reverted to 1.4x due to that while they get their act together – might not be issue on your site, but see my other thread on that. Jetpack also had a recent update, and some folks had issues with that.

Might not be related — but this stuff is from the past 2 weeks, specifically.

Wow, I did not know, that my theme is so outdated. I will surely update. But what’s going to happen when I do? Which setting and widgets will be reset, which data do I have to input again?

Thanks for the reply
D.K.