Note Google+ is rebranding and reorganizing as of this week (Nov. 18), many things are not working right like #tags, and they are pushing folks to move to new layout.
Not much you can do except ensure you have the correct OG tags in your meta data. I’ve been manually submitting my most important items, but even then it’s just headline and image – no description. Even sharing from Google News does not pick up the description — so that should tell you something, their own sharing button doesn’t grab the snippets properly from their own site!
Their own sharing button in Google news ALERTS only picks up image; also again their own tech can’t resolve their own content properly.
-
This reply was modified 10 years by
simchris.
They have pushed out 3 bug fixes “so far” as I predicted … we’re waiting for 3.04 to even touch it! 🙂
Make sure tag name is not identical to a category name, post name, or author name; that is most common problem.
FYI:
3.0.3
Release Date: November 19th, 2015
•Bugfixes: •Fixes a bug where the snippet preview was broken.
3.0.2
Release Date: November 19th, 2015
•Bugfixes:
•Fixes a bug where disabling the visual editor caused our content analysis to break.
•Fixes a bug where the content analysis would break on installs that replace tinyMCE with ckEditor. Currently only supports the html editor.
•Fixes a bug where slug changes were not properly synchronized in the snippet preview.
•Fixes a bug where long slugs could be broken by wrongful synchronization with the snippet preview.
•Fixes a bug where digits were not analyzed well in the content, causing focus keywords or keyphrases with digits to no longer be matched.
•Fixes a bug where the url in the snippet preview was not in line with permalink settings. Fixed for permalinks containing the post name.
•Fixes a bug where focus keyphrases of more than two words would not be recognized properly in the content.
•Fixes a bug where the translation files were corrupted causing the translations to no longer work.
•Enhancements:
•Fixes caching problems. We’ve versioned file names for assets that have changed to circumvent caching strategies that consider preventing regular cache busting a good idea…
3.0.1
Release Date: November 18th, 2015
•Bugfixes: •Fixes a bug where users where getting error notifications about how their site was not indexable when in fact no check had been performed yet.
•Fixes a few broken links to help docs about the OnPage.org integration.
•Fixes an edgecase where the indexability check would go wrong for sites that filter the home url.
•Fixes a bug where the admin email that was sent to report the current indexability status was not rendered as HTML.
Hi
yes, the auto post thumbnail pro plugin does set a default featured image you select if none exists, and it will recrop based on theme settings, hence why you may need the free thumbnail upscale plugin also if you have a tall image that needs to be zoom/cropped for horizontal.
I have no financial relationship to the plugin author, company, etc., but we had similar issue on a WP website launched in 2005 which started with another CMS, then moved to WP, and then when we switched to newsmag last year we had 10 years of content/images to “make compliant” with modern WP practices. Worked great.
best $9 I ever spent 🙂
http://codecanyon.net/item/auto-post-thumbnail-pro/4322624
Frankly, I’m sure Radu could evaluate that plugin function and replicate it as a module or paid addon to their themes, but this is one of those great toolkit solutions that saved the day for us on numerous websites.
LOL….
well, there you go. I’m waiting for 3.04. Not that I don’t trust them, but ….
All kidding aside, they did major major changes to their engine, and I’m not fond of the outbound site check ‘feature’ and will need to see if that can be disabled (we self check our own site, we don’t need yet another ping from a site).
Upshot — you may experience all kinds of issues unrelated to ANY theme while they sort out the compatibility issues in 3x.
But I’m pretty sure anybody reading this thread has figured that out by now! 🙂
I salute all you brave souls taking the plunge early and breaking the virtual trails. Bravo!
Somebody going to the index page in your theme folder is not normal, so that isn’t a significant error related to other issues. That isn’t a site page or anything a normal person should go to, but it sometimes gets triggered when doing updates.
Might want to
a) scan site for security issues
b) reinstall WordPress and all plugins
c) switch to default theme temporarily
d) install clean version of theme
e) retest
You can add some spacing CSS to the widget class above/below.
You can also simply put an empty text box there and put line break in it, or a CSS div.
OG tags is one of the main features of YOAST SEO. You might try turning that off, or try reading the docs. I think it’s on the somewhat obvious “social” settings in Yoast.
Of course if you turned Yoast off and it’s still there then it likely is default item from theme, likely being loaded from the big functions file inside the booster folder.
Wait for TagDiv to chime in on where that is.
If you are using yoast, be sure to uncheck the “use open graph” tag features ( OG = open graph).
We use auto post thumbnail pro here, which is cheap on envato, and solved those same issues for us. We also use the free thumbnail upscale plugin which can help where smaller images need to be larger than they were uploaded.
We set our default size as 640xNNN and that seems to work pretty well, for the layout we happen to be using.
I use the Auto Post Thumbnail Pro plugin via Envato to solve this — we did the same thing for one site couple years back. Great cheap plugin solves the “attach to featured” issue. To enlarge images, also add the free “thumbnail upscale” plugin.
We use 640xNNN size images here as best “one size for all.”
Wow. Must have a great time machine, considering WordPress launched in 2003. You are a grand master of the universe. Based on the ‘How do I install a plugin’ question, I didn’t peg you as an expert as that is a newbie type query. Most folks look into the download folders, know how to FTP, etc.
Child themes are “normally” meant to allow basic mods without touching parent, except when major changes are made to WP core which has happened a lot this year, or if there is major theme upgrade to bring entirely new feature set at which point the child theme also needs to be upgraded.
Most of us using WP the past decade are aware of this.
Not trying to argue about it, but of course lots of themes to choose from. I love this one and we use it for our news network and have no troubles, but then we edit the main theme and never use child themes as they are a redirect of the CSS and you are eventually going to run into the issues you are now.
I’ve used dozens of themes and the child themes often change to address changes to WooCommerce, WP core, security patches, etc. And WordPress 4.4 next month brings additional changes to core.
In any case, I don’t work here — so sorry I posted anything here — didn’t intend to upset you.
It’s all good. Peace! 🙂
-
This reply was modified 10 years by
simchris.
Not really theme related, but this might help:
http://www.wpbeginner.com/wp-tutorials/how-to-redirect-your-404-page-to-the-home-page-in-wordpress/
Most themes work this way, so welcome to WordPress.
Yeah… I usually wait a couple of days for new full dot versions of YOAST, as they have totally crashed my site a couple of times. They seem to push the new version out then use the customer base as the beta testers, then they do 1-4 updates, then it’s good to go.
With them moving so much to Ajax/JavaScript there is already a ton of things happening in the admin panel with JavaScript, so it’s going to cause some major funky things as it’s totally different how they’re actually doing stuff. Probably need to go through and resave every option panel in YOAST 3x to be safe (as had to be done in couple of older versions).
We’re upgrading to a ‘pro’ license with them soon, so we can report goofy stuff and get reply.
Color me paranoid!! 🙂
-
This reply was modified 10 years by
simchris.
Wordpress how to install plugins:
https://codex.wordpress.org/Managing_Plugins
Manual Plugin Installation
There are a few cases when manually installing a WordPress Plugin is appropriate.
â—ľ If you wish to control the placement and process of installing a WordPress Plugin.
â—ľ If your server does not permit automatic installation of a WordPress Plugin.
â—ľ The WordPress Plugin is not in the WordPress Plugins Directory.
Installation of a WordPress Plugin manually requires FTP familiarity and the awareness that you may put your site at risk if you install a WordPress Plugin incompatible with the current version or from an unreliable source.
Backup your site completely before proceeding.
To install a WordPress Plugin manually:
1. Download your WordPress Plugin to your desktop.
2. If downloaded as a zip archive, extract the Plugin folder to your desktop.
3. Read through the “readme” file thoroughly to ensure you follow the installation instructions.
4. With your FTP program, upload the Plugin folder to the wp-content/plugins folder in your WordPress directory online.
5. Go to Plugins screen and find the newly uploaded Plugin in the list.
6. Click Activate to activate it.
Try removing some stuff:
a) have only one related element item in sidebar
b) remove related posts from footer
c) turn off the “you might like …”
d) turn off the “related posts/ more from author”
e) use normal menu not mega-menu
f) try using normal blog roll home page temporarily
g) make sure you increased default memory for WordPress in your wp-config.php file
Good places to start to see what it might be.
Basically every “show me a list of blah …” is a dbase “query” … so cutting back on that to dial in what your server allows, is good practice.
If you’re using YOAST SEO, be sure to turn that feature OFF in Yoast Seo.
I think you can remove most header stuff from the theme by editing the header.php, unless I am mistaken. I usually remove stuff like the pingback, myself.
Might be a function, if you don’t see it in the header.php file. But TagDiv will need to provide pointer on that.
(I don’t work here; just some feedback.)
-
This reply was modified 10 years by
simchris.
The all new version of YOAST may have some bugs; hence the inevitable 3.01 dot update and likely further dot updates from Yoast. Likely good to go BACK to prior version for the moment.
New version of Yoast using various JavaScript things now in place of dbase things.
Likely major clearing of caches/CDN reset will be required.
Note that “new” full dot versions of YOAST almost always have notable problems which are then “fixed” over the next few days with 1-4 dot updates.
Good idea to *never* install a full dot update of YOAST until the dot revisions are in place.
Seriously.
However, also be aware they may be launching it pre-emptively to be fully compatible with the pending December release of WordPress 4.4 which will bring a number of changes, which may impact all themes and plugins.
https://codex.wordpress.org/Version_4.4
-
This reply was modified 10 years by
simchris.
Looks like what the error says, you need to increase the execution time for php with your hosting php settings.
Did you also update the included plugins ?
Yes. You should never have duplicate pages, posts or category names as they are bad in Google SERPS (per their guidelines), but also confusing to internal permalinks in some cases.
Glad you sorted it! 🙂
If using Chrome you also need to fully clear browser cache as well. If your server runs mod_pagespeed you need to turn off MPS then serve new image until cache for MPS clears.
only the basic zip file – which is the theme; the “all files” also has docs, plugins, psd files, etc.
Always best to unzip on your PC to see what is inside a zip before uploading to your host.
Also, see the them docs (link right side page) on how to install 🙂