Home User profile
tagDiv Member
Christopher is a long time WordPress user. Anything else you need to know is private ;-) I *do not* work for TagDiv, but I've been using their themes since late 2013.
simchris
tagDiv Member

Not a fiasco, just need to learn how to upgrade themes when there are major updates.

simchris
tagDiv Member

DUPLICATOR is the only thing I’ve used to migrate a site to another location, including changing name of one site to shorter version.

The upgrade docs are found in the documentation link top right of forum.

simchris
tagDiv Member

Visit the home page for TagDiv, and go to the theme for demos
https://demo.tagdiv.com/select_demo/select_demo_newspaper

(I don’t work here; but am guessing they may be updating the demos for new version; dunno.)

simchris
tagDiv Member

Well, theme devs not responsible for moving a working site to another server — that should be done via the migration tool on the hosting server, or using DUPLICATOR plugin for best results; for probelms with using Updraft, you might check with their support team if their solution for moving your site doesn’t work. Not really a theme issue there.

And you can email TagDiv privately – note the email bottom of every page. 🙂

DUPLICATOR plugin is best solution for migrating a website to new server if the new host doesn’t have a migration tool (e.g., Plesk setups can do this, as can most cpanel hosting providers).

simchris
tagDiv Member

Just fyi —

The envato ‘plugin’ updater will never work 100% of the time and may break site.

Always *best* to do it via FTP, as you can make a safety backup of your site before uploading new folders, in case something breaks or bad plugin causes site to not work at all due to some unexpected compatibility issue.

Also remember when doing major upgrade
– backups should be made of working website
– you will need to update theme, and theme related plugins; disable other plugins for testing
– disable any caching plugins, clear caching
– ideally disable mod_pagespeed during upgrade if using that via htaccess
– after upgrade you may want to use the wp-optimize plugin to help clean up any gremlins in dbase; –and– you should resave your ‘permalinks’ to clear transients
– you will also need to clear your history/cache in web browser to ensure you’re seeing the new CSS for site being loaded properly, or site may look broken/different

Also worth considering
a) copy the text/shortcodes from your home page layout into text file
b) copy/export any custom css
c) copy/export to text file any complicated widget codes you have setup

Chris

simchris
tagDiv Member

Just fyi —

The envato ‘plugin’ updater will never work 100% of the time and may break site.

Always *best* to do it via FTP, as you can make a safety backup of your site before uploading new folders, in case something breaks or bad plugin causes site to not work at all due to some unexpected compatibility issue.

Also remember when doing major upgrade
– backups should be made of working website
– you will need to update theme, and theme related plugins; disable other plugins for testing
– disable any caching plugins, clear caching
– ideally disable mod_pagespeed during upgrade if using that via htaccess
– after upgrade you may want to use the wp-optimize plugin to help clean up any gremlins in dbase; –and– you should resave your ‘permalinks’ to clear transients
– you will also need to clear your history/cache in web browser to ensure you’re seeing the new CSS for site being loaded properly, or site may look broken/different

Also worth considering
a) copy the text/shortcodes from your home page layout into text file
b) copy/export any custom css
c) copy/export to text file any complicated widget codes you have setup

Chris

simchris
tagDiv Member

Just fyi —

The envato ‘plugin’ updater will never work 100% of the time and may break site.

Always *best* to do it via FTP, as you can make a safety backup of your site before uploading new folders, in case something breaks or bad plugin causes site to not work at all due to some unexpected compatibility issue.

Also remember when doing major upgrade
– backups should be made of working website
– you will need to update theme, and theme related plugins; disable other plugins for testing
– disable any caching plugins, clear caching
– ideally disable mod_pagespeed during upgrade if using that via htaccess
– after upgrade you may want to use the wp-optimize plugin to help clean up any gremlins in dbase; –and– you should resave your ‘permalinks’ to clear transients
– you will also need to clear your history/cache in web browser to ensure you’re seeing the new CSS for site being loaded properly, or site may look broken/different

Also worth considering
a) copy the text/shortcodes from your home page layout into text file
b) copy/export any custom css
c) copy/export to text file any complicated widget codes you have setup

Chris

simchris
tagDiv Member

Just fyi —

The envato ‘plugin’ updater will never work 100% of the time and may break site.

Always *best* to do it via FTP, as you can make a safety backup of your site before uploading new folders, in case something breaks or bad plugin causes site to not work at all due to some unexpected compatibility issue.

Also remember when doing major upgrade
– backups should be made of working website
– you will need to update theme, and theme related plugins; disable other plugins for testing
– disable any caching plugins, clear caching
– ideally disable mod_pagespeed during upgrade if using that via htaccess
– after upgrade you may want to use the wp-optimize plugin to help clean up any gremlins in dbase; –and– you should resave your ‘permalinks’ to clear transients
– you will also need to clear your history/cache in web browser to ensure you’re seeing the new CSS for site being loaded properly, or site may look broken/different

Also worth considering
a) copy the text/shortcodes from your home page layout into text file
b) copy/export any custom css
c) copy/export to text file any complicated widget codes you have setup

Chris

simchris
tagDiv Member

LOL … I forgot to actually paste in the changelog text (doh; coffee not kicking in over here …)

##
Release notes:
Newspaper – Version: 8.7
new: tagDiv AMP plugin – tagDiv’s solution for implementing Google AMP in WordPress
new: tagDiv Newsletter plugin – The beautifully designed Newsletter subscription form
new: tagDiv Multi-Purpose plugin version 2.0
new: Nature love installable demo – view now
new: Raw & Wild installable demo – view now
new: Ink Parlor installable demo – view now
new: City News installable demo – view now
new: Crypto installable demo – view now
new: Wine Aroma installable demo – view now
new: News Week installable demo – view now
new: Coffee Blog installable demo – view now
new: Responsive options for shortcodes in tagDiv Multi-Purpose plugin
new: Responsive font options for shortcodes in tagDiv Multi-Purpose plugin
new: Responsive options for theme’s shortcodes
new: Responsive font options for theme’s shortcodes
new: Content length option for blocks and Big Grids
new: 1 new content block – The new Flex Block is here to help you design spectacular news pages
fix: Allow ‘underscore’ and ‘space’ characters into the sidebar name
fix: PHP 7.2 compatibility
fix: Save row and inner-row option in tagDiv Composer
fix: Caption alignment in WordPress 4.9
##

simchris
tagDiv Member

The envato ‘plugin’ updater will never work 100% of the time and may break site.

Always *best* to do it via FTP, as you can make a safety backup of your site before uploading new folders, in case something breaks or bad plugin causes site to not work at all due to some unexpected compatibility issue.

Also remember when doing major upgrade
– backups should be made of working website
– you will need to update theme, and theme related plugins; disable other plugins for testing
– disable any caching plugins, clear caching
– ideally disable mod_pagespeed during upgrade if using that via htaccess
– after upgrade you may want to use the wp-optimize plugin to help clean up any gremlins in dbase; –and– you should resave your ‘permalinks’ to clear transients
– you will also need to clear your history/cache in web browser to ensure you’re seeing the new CSS for site being loaded properly, or site may look broken/different

Also worth considering
a) copy the text/shortcodes from your home page layout into text file
b) copy/export any custom css
c) copy/export to text file any complicated widget codes you have setup

Chris

  • This reply was modified 8 years by simchris.
simchris
tagDiv Member

They probably can’t work on both at same time; historically, the newspaper theme is updated, then any quick hot fixes done; then newsmag update follows that. NP is the flagship, so there is some trickle down to newsmag once tested on newspaper.

The stock answer will probably be they are working on it, but no specific ETA.

simchris
tagDiv Member

Probably both since mobile responsive and AMP are two totally different things.

Or, just use desktop/responsive (classic mode… I suppose), then AMP for Google AMP support.

So>
– classic mode would be desktop templates; responsive for desktop, ipad, phone
– AMP plugin for AMP compatible devices/browsers if accepted into AMP index

Or>
– desktop templates for desktop
– mobile plugin for devices that don’t support AMP
– AMP plugin for AMP compatible devices/browsers

I think that’s how you’d wrangle that.

simchris
tagDiv Member

You can copy the code from top of woocommerce template into the td version. Often the template change is minor and many times i found only change was version header, which causes useless warning.

simchris
tagDiv Member

Yep. Not ready for 7.2 as noted. Use 7.1 until new version released… real soon now, supposedly.

simchris
tagDiv Member

And, since the landscape keeps evolving … good to read up on what is *actually* happening with the AMP format “right now” vs where it was in 2016 when we started with it:

e.g., some of the latest wonk
https://www.ampproject.org/docs/reference/components/amp-story

https://searchengineland.com/amp-stories-new-accelerated-mobile-pages-format-google-291907

  • This reply was modified 8 years by simchris.
simchris
tagDiv Member

I think you can do that using the built-in ad manager, using the ‘insert after n paragraph’ option ?

simchris
tagDiv Member

I think a more recent post stated that they would be including that in a very soon upcoming version; I think the priority at the moment has been
a) PHP 7.2 test/update code
b) updates/enhancements to the TD Composer plugin
c) bug fixes from the major update to recent version of Newspaper
d) additional prep for big changes coming to WP in WP5.

I believe AMP support is in the mix, according to some of the TagDiv theme folk support posts on the topic. 🙂

Keeping in mind that AMP support doesn’t fix existing content/html issues (e.g., inline HTML), https issues, or push for upcoming http/2 support as a metric on the usability/best practices audit in Chrome. Using the AMP plugin *now* is a good learning curve on basic fixes needed for baseline AMP compliance, regardless of solutions used.

( I don’t work here. Just a webdev dinosaur ! (rrr!) )

simchris
tagDiv Member

This error will show up when installing or changing themes unless using a maintence mode plugin. You can mark fixed in search console and ignore

simchris
tagDiv Member

Also try disabling any lazy load animation

simchris
tagDiv Member

Looks like your caching plugin

simchris
tagDiv Member

So, you’re saying the ‘preview’ button doesn’t work on the post edit page ?

simchris
tagDiv Member

The bundled version of Revolution Slider included with theme doesn’t need a purchase code.

simchris
tagDiv Member

Yes, i have been managing my own linux servers since 1996… php 5.6x is secure, as much as 7.2. 7.1 just patched this week. Still, if theme and plugins tested for 7.1 but not 7.2, then you will have errors until the theme and plugins are uodated. So, either use 7.1 or get errors. Up to you.

Theme is not adverised as compatible with 7.2.

Viewing 25 posts - 1,051 through 1,075 (of 9,335 total)