Sorry not much help ๐
Did you try sharing an item and then do the attachment recapture option ?
I had to do that one day this past week for every post, but it works (most of the time).
Some people on the Yoast and Visual Composer forums are reporting issues with Yoast 2.1 and 2.1.1 with Visual Composer, including v4.5. Not theme related.
Check those support forums on the WordPress.org plugin repository for more info.
Perhaps a fix for Yoast will be coming ? Dunno.
With all the changes to plugins for the XSS flaws, I have a hunch this may crop up for the next couple of weeks with bunches of stuff.
-
This reply was modified 11 years by
simchris.
Try disabling your cache; try disabling all plugins except visual composer.
Try switching back to twenty-fifteen theme see if you can save posts.
Check to make sure you re-save permalinks; check to make sure your dbase is not overloaded, or if you have exceeded the storage space on your account, etc.
Try optimizing your WP database.
Try saving a draft post; then make sure you see the “post saved” message at top; then go to your “all posts” and see if there (be sure to make note of proper date setting on your post that you’re not saving it into the past where it would be buried on the index).
That would be my suggestion.
Worst case, reinstall theme and see if problem persists.
Might be issue with conflict with your FB comments plugin, etc. — pop up on your site super annoying for FB when I’m logged into one of my “pages.” Try turning off plugins to see if conflict; try different page.
Mine is working just fine, btw.
Facebook chooses how to show images based on several factors – size of original images, orientation, and the specific image set as featured in the og:image tag.
You have zero control over that, sadly.
Sometimes they capture with the image to side, then later it expands to full width. Only works usually if the image is rectangle, and large enough for their “large” image size.
The preview as in your example above isn’t always the “final” posted version on timeline.
Welcome to Facebook.
This is what I see in your robots.txt file, so apparently not cached …
User-agent: Googlebot
Disallow: /cgi-bin/
Disallow: /wp-admin/
Disallow: /wp-content/plugins/
Allow: /wp-content/plugins/*.css
Allow: /wp-content/plugins/*.js
Disallow: /wp-content/mu-plugins/
Disallow: /wp-content/cache/
Disallow: /wp-content/themes/
Allow: /wp-content/themes/*.css
Allow: /wp-content/themes/*.js
Allow: /wp-content/themes/*.gif
Allow: /wp-content/themes/*.png
Allow: /wp-content/themes/*.jpg
Disallow: /*.php$
Disallow: /*.inc$
Disallow: /*?
User-agent: *
Disallow: /cgi-bin/
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-content/plugins/
Disallow: /wp-content/mu-plugins/
Disallow: /wp-content/cache/
Disallow: /wp-content/themes/
Disallow: /*.php$
Disallow: /*.js$
Disallow: /*.inc$
Disallow: /*.css$
Disallow: /*?
# permitir o adsense em qualquer url
User-agent: Mediapartners-Google*
Disallow:
Allow: /*
# majesticseo.com
User-Agent: MJ12bot
Disallow:
#Sitemap
Sitemap: http://emagrecersemdieta.com.br/sitemap.xml.gz
I would likely try REMOVING everything in your robots.txt file.
Perhaps remove this: Disallow: /wp-content/themes/
Obviously you should be clearing your cache after doing any changes to website like this, updates, theme upgrades, WP updates, etc. Yoast SEO no longer manages robots.txt file – there isn’t even an option to edit it anymore in their menu (edit files is now gone, I noticed; at least in my setup).
Might be temp issue with FB.
I was having trouble sharing stuff a little bit ago (12pm PDT 5/8/15), and it cleared up about 10 minutes ago.
Obviously if you have an og:title tag populated, it can’t be an error for that info missing.
You might retry that now.
I believe any email sent via the WP system, via php has that — not theme specific. You’d have to dig into the support for WordPress in their Codex likely to fix that (unless somebody here knows how to fix).
You might also try one of the smtp plugins for sending email out from WordPress, which allows more customization of headers and sender info.
Normally in WordPress you paste from MS Word into the post editor, using the “visual” tab and not the text editor tab. I do this all the time. If you have any bad formatting in Word, this will carry over into WP, such as pasting OTHER content into your Word doc and THEN pasting into WP.
note that “import” is handled by WordPress and not the theme; as of v 3.9 they removed the “post from Word” button and now copy-pasting a Word file into the visual editor tab, will auto-recognize it’s a Word doc.
You can also do advanced import with tools like this
http://plugmatter.com/document-importer/
You might check with YOAST SEO support threads on WordPress.org for quick checkup.
Obviously the theme can’t update Yoast SEO in any way; as it’s not developed by TagDiv; nor is Visual Composer.
See thread on WordPress support page for the plugin:
https://wordpress.org/support/topic/yoast-and-visual-composer
this fix may not apply to your use case, but apparently still some issues even with VC 4.5 and Yoast 2.1:
I found that letting the SEO WordPress "Main Keyword" empty on the backend of my homepage makes everything fine.
Not having any issues in 1.71 with that (so far). Need to update my others sites from 1.6 to 1.71 … and that is on the docket for Friday here ๐
-
This reply was modified 11 years by
simchris.
And of course you should already be running 4.2.2 due to all the XSS security patches done in 4.2, and 4.2.1 and the XSS in the icons in twenty-fifteen theme (which you can actually just delete vs upgrading to 4.2.2 if mood strikes… )
Anyway…. shutting up now ๐
Well….. to be clear, 1.7 works with 4.2
— 1.6 works with WP 4.2.2, so 1.7 “should” …
I would skip 1.7 and go right to 1.71B (current file on ThemeForest).
-
This reply was modified 11 years by
simchris.
You might try manually uploading just the font files via FTP to ensure they are in “binary” format vs “ACSII” format — some systems may decompress that stuff incorrectly, or it might get zipped incorrectly, or even uploaded improperly via FTP the first time (some FTP software won’t “auto set” the format type from binary to txt on upload) — sounds stupid, but it’s happened to me.
Worth a try ๐
And, or course, make sure they are truly being called from your local domain and NOT off the CDN, unless you have CORS rules setup on the CDN.
-
This reply was modified 11 years by
simchris.
Yup. You can always download the theme files and check the changelog, too, as it will normally state stuff like that, such as XSS security patch to coincide with all the industry fixes (new WP 4.2.2 update today!). ๐
And just to clarify for all … issue is with Visual Composer and *not* with the theme files; meaning 1.71B is not the culprit, nor was 1.7 — it’s entirely something with VC which causes major system issues when say a page is getting 15,000 hits at once; multiply that by 20-100 pages in a one hour period, and system throws a wrench.
1.4 was ROCK SOLID; 1.5 didn’t have major hiccups. Version of VC included with 1.6 started the issues for us. And version with 1.7 killed the box (or tried to anyway).
I use “Auto Post Thumbnail PRO” (find on CodeCanyon) …
You need to DELETE old versions, not over-write.
Try my “how to” guide sticky post for best way to do upgrade. ๐
(to clarify my above comment; testing the shim on one site which doesn’t have VC installed on the DOMAIN at all)
For more on this, see
https://forum.tagdiv.com/topic/newsmag-1-7-1-killed-our-server-again/
-
This reply was modified 11 years by
simchris.
Radu,
I sent you copy of the error logs generated automatically (light versions), for the ‘overload’ which happened overnight from the ONE website — which is still running VC + NM 1.6 — just for reference. Anecdotal, and not necessarily useful from the standpoint of all server processes running, but specific to what was causing CPU spikes last night for one hour/period to generate the warning/alert email from server.
Look for email with subject
SHIM BETA 2 PROJECT / blah blah.
Sent that at 8:46 AM PDT 5/7/15.
Chris
HI, just to give you an idea ….
our site CaliforniaNewswire.com running the shim “beta 2” is right now trouble free; although I have not yet switched on mod_pagespeed but will be doing that today — it shouldn’t cause any issues.
By comparison, one of our other sites eNewsChannels.com – running 1.6 + VC got a huge influx of traffic last night, and some scraping from various syndicators, and our CPU went to
Time: Wed May 6 23:12:58 2015 -0400
1 Min Load Avg: 53.57
5 Min Load Avg: 14.23
15 Min Load Avg: 5.33
Running/Total Processes: 107/1111
Based on the Apache error log, that was all from that ONE site, being scraped from “54.160.202.74”
9-0 22697 0/51/52008 W 9.85 3 0 0.0 1.12 399.32 54.160.202.74 enewschannels.com HEAD /news/news-made-in-the-usa/ HTTP/1.1
One index page being scraped for all the headlines, used 9.85% of the CPU (!). And, um them be like QUAD XEON processors, too.
So, it’s pretty clear Visual Composer when ‘under load’ really whacks the system!
I do know that when I brought up the “can I buy a 10 pack” once upon a time, they did offer to credit me back some money if I did that on one order — in case anybody else thinks on that — since Envato doesn’t have quan. discount, and the license keys generated there anyway.
Hi … not to let cat out of bag, but working with RADU “beta testing” a light version of VC, basically what he’s calling a “Shim” — and it’s right now being tested with my CaliforniaNewswire.com site (which does *not* have VC installed, and it’s NOT on the server).
See my other topic on “1.71 crashed our site again” … if curious. ๐