Heh. Yeah, the ‘official’ FB plugins are always fun. Their ‘comment box’ code used to break stuff left and right. Their code is sometimes iffy, and I tend to blame them for problems over a theme.
Of course, it could be one of the bugs fixed in the new WP update today, too! So, maybe try that and then put the FB plug back ‘on’ and see if mayhem ensues!!! 😉
Best bet is to
First check your wp-config and htaccess to see if something got “munched” there.
1) make a backup of your dbase from phpmyadmin from hosting account
2) make backup of WP data from your wp admin panel if you can login; and backup your wp-config.php and .htaccess file if you use one for permalinks.
3) turn off all plugins
4) turn off the Newspaper theme; go back to default “twenty-something”
5) reinstall wordpress via FTP proper way; re-upload theme files via FTP
6) make sure site works with default theme
7) preview newspaper theme
8) activate theme; turn on only “required” plugins
It sounds like you have something broken unrelated to theme.
Also check your permission on whether the ftp owner or Apache ‘owns’ your content, as this can cause major headaches, and I’ve found having your WP install ‘owned’ by Apache/server just doesn’t work properly. This is something to check with your hosting provider, or via your hosting account site panel for the file viewer which will show “owner” for each folder in your root public folder.
Hope that helped. Often best to ‘clean house’ when you’re having problems you can’t trace back to any one thing.
Hi, the “next” pages work on both of my sites running theme with only the core set of plugins (no Jetpack!), plus using AddThis, AdSense ads, and no insert of ads in content (only header + sidebar).
Usually this “error” is from modifying a page, using a child theme with a bad addition to the functions file, or a conflicting CSS element from another plugin.
On one of my old themes, I also had another navigation plugin running from a prior theme and forgot to turn that off, and so it broke it.
Not sure if any of that helps. But it does work properly on both our test magazine site and a live production site (2004 site updated for 2014 with this theme) without any trouble, which implies a local issue vs a theme specific issue.
On another theme I found going to the admin > settings > permalinks and resaving the permalinks actually helped. Which is bizarre, but there you go.
Hi, Radu
that would be awesome. I switched from using the child theme so as to not impact my pagespeed adventures, and so the custom CSS I put at bottom of style.css didn’t have an impact in the way the child/style.css did. Being able to tweak a few things here or there with either a custom.css file, or perhaps more appropriately these days a “hook” to drop some code in the head at bottom before the body tag (Woo Themes does this fairly well, btw; they have all these little ‘hook’ locations to drop in code, although it does add a slew of if/then crap; disclosure we’re trying to ramp up your theme to replace Woo Canvas!).
So for us to be semi-done and in full “go mode” my laundry list of stuff needed is simply:
1) Google async alignment in top bar
2) websafe fonts option – which would save me hacking that one
3) custom.css injection hook in head, to over-ride couple of minor things (like making the author box bio text size smaller, when making the post side larger so the author bio isn’t over-large from the base adjustment)
4) not critical; but option to have a local image for author box (add new user meta field for ‘author image’ — we used to do this on our in house theme, not difficult) to not pull gravatar and save some bandwidth from external site — if you wanted to wow the kids, you could add a “grab my image from gravatar” option 😉 Peeps love the “automagical” stuff.
Otherwise, for us — you’re done! I’m hoping the v3 won’t introduce new issues, but right now we’re very happy.
BTW: for ‘web safe’ fonts, Adobe came up with some really quite brilliant ‘stacks’ of the best font mix to use across Mac, Windows, iOS, Android, et al. They can be found in Dreamweaver, and possibly their help system – but if you need those, just let me know. Much nicer than the old skool ‘Helvetica, arial, sans-serif’ stack. 🙂
Not sure “stupid” would be the right word for how the theme is setup, IMHO.
Works great for us on our sites, especially for vertical iPad on Retina display which many many responsive themes get wrong, especially many Bootstrap 3 themes which lose the sidebar entirely on iPad/Retina.
That’s also typically why themes have demos on Themeforest so you can test their “stupid” layouts before you purchase 😉
Hi Radu
the other reason we found the /posts worked better is that it’s the “public facing” page for the G+ account unless somebody is already in your “circles.” (TRY the URL without /posts — Google will do a redirect to /posts !). So, this also helps with on page links or other referential uses from the wp admin > user > user account > social media fields. For whatever reason it’s the method that seemed to work when the author option was first rolled out, so we’ve stuck with it. “Your mileage may vary.”
Dual monitors – not sure this FB photo is publicly reachable, but let’s try shall we:
https://fbcdn-sphotos-b-a.akamaihd.net/hphotos-ak-prn2/954774_10151456063618435_1875947256_n.jpg
Hi, Anna
we’re running the latest “stable” release from November. The current January version is an “edge” (or “Beta”) which is on different development track. So, hoping the stable version will be updated end of January with some of the new fixes.
Since our main sites are mission critical we dialed back all the filters server wide to just the CoreFilters minus one lazy load element (have an over-ride to lazy load images on page load and not on scroll as that did weird things).
Originally tested with a “full set of best choices for WordPress” but we’d see that something caused conflicts and so doing side by side speed of loading tests, most of the time the pages would load more quickly with mod_pagespeed OFF, which didn’t make much sense.
Now, I’m testing the filters sort of case by case, then testing the “mix” of elements (e.g., fonts, adsense, grvatar, addthis/social buttons) with each option, trying to use as few as possible to not actually slow things down (meaning why have mod_pagespeed do something which doesn’t actually need to be done — 10 extra filters adds some latency somewhere, although if done pre-cache not a biggie “in theory”).
It’s also worth noting I hacked the addthis plugin to add the “async” method which is not built-in (stupidly); which can be found in one of my other posts.
The adventure continues on Saturday!
Also note that some “master filter” settings enable sub filters, as so:
ModPagespeedEnableFilters rewrite_images (apache)
in the configuration file. This is equivalent to enabling
inline_images, recompress_images, convert_png_to_jpeg, and resize_images.
And then recompress_images is a master ‘group’ filter set for the following:
This is also a group filter, and is equivalent to enabling: convert_gif_to_png, convert_jpeg_to_progressive, jpeg_subsampling, recompress_jpeg, recompress_png, recompress_webp, strip_image_color_profile, and strip_image_meta_data.
So as you can see there are
master group >> sub master group >> end filters part of sub-master group
hence the phrase “tricky” 🙂
I am testing the master groups first to find what doesn’t work; then sub-groups, then down to specialized sub-filter settings.
Pagespeed mod test update: settings 0.4
Google Pagespeed 93/100 on main GPS Insight
page: http://ga-ga.com/1262/fiction-area-code-666-part-18-del-arton/
– google adsense – no ads for test
– addthis plugin replace social media buttons with single button ‘on’
– gravatar loaded dynamic over network for author box
todo:
1) load author image locally either with plugin, or add field to functions.php to add new user datafield, then call user meta for the field instead of gravatar code.
2) reduce server response time — typical is 0.32 seconds (320msec) up to 4 seconds; but Google now saying <200msec is the “ideal” — not sure tradeoff on optimizations for everything else; but I did see a post the other day about server tweaks to speed up “first byte” load of WordPress pages to deal with that so called “error.” Solving this would negate the penalize from Google AdSense being on.
3) super annoying “reder blocking” CSS almost “quashed” and ironically the error is from mod_pagespeed trying to fix:
Optimize CSS Delivery of the following:http://ga-ga.com/…ootstrap.css.pagespeed.cf.n0P3fhMJJz.css
http://ga-ga.com/…/A.style.css.pagespeed.cf.JAYrGYtjNo.css– so in typical GPS fashion, one Google product complains about another Google product which is designed to fix the complaint in first place (ARGH!). This one will take some playing around with the “filters” which is where I got stuck this past weekend.
Hope this is entertaining somebody 🙂
and I forgot to mention here is the code I’m using in my htaccess file for mod_pagespeed testing, in addition to CoreFilters being on from the main .conf file at server level, eventually this would be a <directory> directive in the .conf and not in htaccess for better optimization.
<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters move_css_to_head
ModPagespeedEnableFilters combine_css
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>CHANGE to my prior htaccess code for expire headers to solve one javascript file for comments in the core wp code:
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>I also added these to the end of the htaccess after the cache control headers, to solve the ETag problem and also the damn spammers hitting my ping script.
<IfModule mod_headers.c>
Header unset ETag
</IfModule>
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>AS EVER: do not make changes to any of your files/settings unless you have backups done.
THis is all experimental at this point; when I have a solid Apache-friendly setup, I will share all the settings in all the files for those interested in this discussion. 🙂
Cheers,
Christopher Simmons
member: PRSA, ASCAP
CEO, Neotrope®
Torrance, CA, USA
(please don’t call me asking for help on anything at this point in time; I will resume my consulting biz once I have my own ducks back in a row, as it were!)
Some our sites generate 2+ million page views per month and have been online 14 years with 230,000 inbound sites for pagerank. We have been managing our own servers since 1996, and ran a hosting company from 1996-2005. We did Oprah Winfrey’s ecom solution for her “Begin with Love” videos a decade ago. Pretty savvy. We are also PCI-DSS certified, and have weathered serious server attacks so have complex security stuff in place. ‘=)
We do use nginx along with Apache 2.2 – for instance phpmyadmin runs on nginx. 32GB of RAM, dedicated 1GB switch at SoftLayer in Texas. Power to burn. Replaced our 2008 server with 12GB RAM and 8 cores. Wild times compared to the days of, say Cobalt RaQ4 (google it).
Still playing with mod_pagespeed stuff as they have lots of cool things like “inline_google_font_css” (Inlines small CSS files used by fonts.googleapis.com into the HTML document.) which I’ve not yet been able to get working. Defer javasceript is another one built-in which is cool.
Stable version from November, edge version from January, and you can’t mix ’em.
Anyway… I’m trying to find the balance of the traditional hacks
1) mods to the wp-config.php
2) mods to functions.php
3) mods to htaccess (Apache)
4) manual optimization of css file if a rewrite system breaks it
5) upload best practice optimized images to begin with; generate smaller thumbs to start with using built-in compression of WordPress vs plugin for initial files; remove duplicate sizes in media setup to match theme size
6) use mod_pagespeed to manage cache (with memcache, eAccelerator, APC, etc.); rewrite on the fly to cache copies with comments removed, delete white space (instant minification!); combine CSS, combine JS, etc.
6) when all that fails to keep a “92” dump the CSS/JS onto the CDN, keep images local.
This is my mission for January. Once done, I’ll have a better sense of what actually works and what is truly a fool’s errand.
BTW: my friends at GTMetrix have a nice plugin for WordPress for testing/tracking pagespeed adventures (recommended!).
MOre later in the pagespeed “forum” here 🙂
I will probably end up doing some kind of ebook for this whole shenanigans.
Chris
