Check you have all of the proper nonce codes in your wp config file, and be sure to clear all caching after upgrade.
Use Contact Form 7:
https://wordpress.org/plugins/contact-form-7/
Be sure to clear your cache as it does work … π
It will move js to bottom but not main CSS which is supposed to be at top or page would flash with no styles first … for any custom plugins stuff you’d have to add those items to the plugin per the theme docs to have the move to bottom.
Luckily a lot of savvy plugin devs are now automatically having option to move stuff to bottom vs putting at top.
You need to edit the CSS the way you want it.
You could copy the code from the other template you like into the template you want to use (mix the different headers).
TagDiv support back on Monday if that didn’t make sense π
In the theme panel under ‘post settings’
Set fewer modules on home page, sidebar, footer and related items under post.
Google recently changed their mobile algorithm for checking, and so it has started throwing an error on just about everything from image sizes, to anything not plain text having some kind of render blocking. If you can get your mobile score to 88 or above, you’re good. Below 85 is not as good, below 80 is “bad.”
Yes, that is the new lazy load option… You can turn that off.
Why not just edit the header style 8 template?
Try fresh install of theme and visual composer, no child theme, all plugins off except visual composer, clear caching, at least 128mb for php.
Not my theme, buddy. I don’t work here, just giving advice.
Upload works for me, just fine. Maybe you got a bad download.
If the error message is coming from your server, maybe double check the settings.
If Envato plugin not working, that’s not an issue with the theme, but a problem with Envato’s crappy plugin.
Oh well… I’m sure you will figure it out. FTP best way to update all WordPress themes as it avoids the exact issue you’re having with YOUR web server config.
TagDiv will be back Monday to help if you can’t sort out the issue before then.
Yes, you don’t seem to be able to read my help … as noted in my first reply.
YOU NEED TO RECREATE THAT USING ONE OF THE WIDGET CONTENT BLOCKS INCLUDED WITH THE THEME.
See the theme docs on the different blocks:
https://forum.tagdiv.com/blocks/
Maybe block 7?
Good luck !
Well, you need to deactivate the default element created by the theme — the popular category item …
so if you *do* actually switch the footer template; then both your second and third columns should now be EMPTY!
Then in the appearance > widgets, you will add a module/block for the popular category, then add a text widget below that in “Footer COL 3” just like normal sidebar.
Basically you should be TURNING OFF the automatic stuff in the second/third column — they should be blank… then you need to put in the stuff you want in both second and third column manually.
You would likely need to setup a javascript button, to switch CSS, then create alternate copy of the style.css file …
we used to do this to allow people to load different size fonts for the old handicapped requirements …
use a simple javascript switcher to switch to style-desktop.css which removes the @media queries for viewport π
jquery method (I’ve not used this)
http://www.cssnewbie.com/simple-jquery-stylesheet-switcher/#.VTvbsGeBFaQ
and here is code we used to used in the olden days (circa 2009?) ?
http://www.dynamicdrive.com/dynamicindex9/stylesheetswitcher.htm
Go to theme panel and the footer settings — switch from default to the version where the first column has default items but second and third column are blank.
[ X ] [ . ] [ . ]
You can then put your own content into cols 2 and 3 from the appearance > widgets
That has never worked right for us, as “permissions” on your hosting account may not be writable for that plugin to work — it’s never worked right for us, and not a problem with the theme.
I find it’s better to do update via FTP, as you can also make backup of your files (download old files to your HD), at same time.
Make sure you’re using the zip file with just the theme files and not “all files.”
Or, unzip the file on your HD, then upload the files via FTP, and make backup of your old site content at same time for safe keeping in case you need to “roll back.”
Main differences (my impressions on this topic only, not ‘official’ in any way)
Newspaper — wider layout for those doing things like 3 column newspaper pages, or where a wider post area needed to do 2 columns of text with photo wraps, for presentation “like a newspaper,” or for those who want a larger playing field. Support for wider ad units in post area.
NewsMag — more compact layout with keylines, like a magazine or older TIME magazine print layout where everything is boxed. NO “wide screen” layout (fixed more narrow grid).
“Bells and whistles” may end up being same between the two at some point, both may lose any R-T-L support, both may support the new TagDiv “API” to hook in extra functions and features.
Main difference is the “width/layout” area and hence slightly different layouts and modules with visual composer, and slightly different default and custom layouts on “category/archive” pages.
In our case, we chose to go with Newsmag as it was more what we wanted when Newspaper was first launched and did have a narrow layout. We wanted to migrate from our in-house responsive (grid 960 custom layout, pre bootstrap) theme, and/or Woo Canvas to seomthing more “shiny and cool” … with “some sense of pagespeed optimization” which most foundries were clueless about in Fall of 2013, but Tagdiv was trumpeting (as we had been doing so here).
I think some folks might end up buying both and trying them out with your specific content and images then choosing the right one for your needs, knowing you’ll have similar workflow, plugins, and “bells and whistles.”
My two cents anyway π
Just to clarify, it’s not really a ‘theme’ issue – for those curious. It’s an issue with Google’s bot having issues with scraping pages to verify actual content vs spammers who try to trick google with content in META data that doesn’t match what is actually on the page.
So, this is why it “seems” like Google’s bot is just ignoring the “description” tags; they use that as “hint” then read the page and look for stuff in certain common “blocks” of content, like “first full paragraph of text on page” …
I am trying to sort out why this happens on some templates, layouts and not on others, across various top websites and small ones, too.
For example I tested page from WIRED mag the other day, and it grabbed the first paragraph; where I tested a page from our main news service portal — which does not use WordPress or any popular CMS [in house system we built in 2005 and I built the templates myself from scratch using customized bootstrap 2.3x code] — and these “should” work but also don’t get the first paragraph captured by G+.
(e.g. this page “should” work — I built it myself π but does not:
https://www.send2press.com/newswire/tickets-on-sale-for-music-festival-drawing-big-name-acts-to-ohio-aiding-cancer-charities-2015-0416-03.shtml )
this page on wired.com does NOT work (odd they have no G+ buttons; bad SEO!)
http://www.wired.com/2015/04/porsches-new-boxster-made-just-driving-enthusiasts/
So far does NOT appear to be these specific elements, with NewsMag
a) “wide screen” headline — across top, 2 columns
b) category buttons/links above headline, after breadcrumbs (on/off no diff)
c) not issue with using mod_pagespeed for comment and whitespace removal, or rewriting images
d) not issue with https vs non https
*anecodatal: have run into couple of issues with Google News, when scraping page couple of times they grabbed the category buttons in place of the story headline or appended them in front of headline — contrary to news XML sitemap — stupid, stupid, stupid! Possibly need more “separation” from those and headline — not yet sure on that.
So, I’m playing with it in the midst of doing major security audit of WordPress plugins, and code across 15 websites (ugh). Only time we had a WP website “hacked” was way back (something like v 1.6 or 2.6 or something? — Al Gore’s website hacked same day ours was …Nov 2007 for those who know their beans). So, we stay on top of security stuff pretty strictly but these new vulnerabilities are a nest of vipers waiting to get milked for their toothy sting juice (have fun with that sentence English translators!). π
Clearing cache after theme update really good idea π
-
This reply was modified 11 years by
simchris.
@pslice
thanks for kind words π
@bichareh
here is the one I’m playing with:
“Disqus Conditional Load”
https://wordpress.org/support/plugin/disqus-conditional-load
Have not had much time to mess with it since I’ve been updating 15 sites for all the various security issues, and auditing everything on case by case basis.
(stupid visual composer!!!!) π
π been there !!