Search Results for 'update'

I trust tagdiv team and there is no doubt that Newspaper is in fact the best theme available in many ways. I also believe that td composer is a great addition and will be very helpful in the long tun. However, I feel compelled to say that starting version 8, this forum has seen many users reporting issues, caused apparently due to td composer (some issues obviously due to improper installation procedures). In any case, knowing the nature of any such major update, I skipped updating 8 and waited for 8.1.

Updating did not cause any major issue in my case although it did wipe out all my sidebar widgets. I had to spend some time to make them work again. To those who have not yet updated to 8 or 8.1, I would suggest note down all your settings like widgets and stuff before upgrading.

The other thing I faced is, my social counters stopped working on facebook although I upgraded the social counter plugin also. I deleted cache, etc. but it didn’t work. My Post fb likes had started disappearing before I upgraded to 8.1 so I wouldn’t count the upgrade responsible for it but after upgrading, my fb Page likes also became 0. In order to verify the issue was not with facebook, I used Jetpack facebook Likes plugin and my Page likes came back. So I suspect there is some issue with the plugin, either tdc or social counter that caused the Page Likes to become 0. This forced me to deactivate tdc although it did not solve the problem then. I must add that after some time when I tried with another computer, the fb Likes reappeared even using td social counter, so the issue may have been caused by some traces of cache or whatever on the first computer but the main point to be noted is, the Page likes did disappear. Hope that can be looked into. For the time being I have switched to Jetpack fb counter but hope to switch back to td social counter soon. I guess I will wait for the next tdc update. I am wiring all this with the hope that it will help users and developers resolve whatever issues may be there.

• This reply was modified 9 years by Mayapur Voice.

This happened to me as well when stretching the row and adding background color. Must be a bug in the latest update.

See the them docs on how to upgrade. v8 is entirely new version, with many many changes, so be sure to review the help/info before doing so.

How did you try to update/upgrade?

Best way is via FTP, so that you can make backup first, and then roll back if you have problems with new version.

You can keep using Visual Composer – it’s not ‘gone.’

The TDComposer is a more lightweight, faster, more secure solution for those who only use the pagebuilder for home page, business info pages, etc. and don’t use it on posts, where there is already wide variety of custom post layouts.

For our sites, it’s a perfect fit, as we don’t custom build ‘posts,’ only ‘pages’ and so it’s much faster, and less prone to all the weird system issues we’ve had with VC.

Nothing to correct in the sense of “it’s bad….” — if you have found a bug and can identify how you experienced it, where and why, and what steps taken to debug that, they will definitely address it for the next update to TDC — which is still fairly young, and still being developed.

TDC is *not* a 1:1 replacement for VC. Two totally different things.

If you like VC, keep using it. If you don’t want to switch to TDC, you don’t have to.

Thanks, Catalin.

Okay from that I can see:
– I cannot copy header.php to the child theme and overwrite it.
– I cannot copy loop_single_1.php (etc) files to the child theme and overwrite it.
– I can overwrite single_template_1.php (etc) files from my child theme.

If this is correct, then every time I update the theme I’ll have to make the changes in the respective files for FB comments to work. Let me know if I have got it right.

In the themes that have been updated well I use the business template, but in this case that gives error is the default theme

I went back to the previous version when I discovered this, and I had to create my front page from scratch because of the last update. Is it safe to update VC now and still keep my block as it is?

Make sure you update the plugins AND the theme together; delete old folder, don’t ‘overwrite’ old ones.

Clear transients with WP-Optimize plugin

Resave permalinks

Works for me doing that.

(also: make sure you’re using PHP 5.6 or higher; as older versions will not work well with most current WP updates, plugins, code, etc. — and older versions are ‘end of life’ now, esp 5.2/5.3).

• This reply was modified 9 years by simchris.

1) make sure you properly installed the new theme and related plugins — you need to delete old folders, not simply over-write them; but make backups via FTP first — as ever
2) after update,
– run WP-Optimize plugin to clear transients
– resave permalinks to clear micro transients
3) make sure you clear/reset any caching plugins prior to update/upgrade and afterwards; if not using caching plugin, the 1 and 2 above should help.

That’s what I do anyway. 🙂

KNOWN SECURITY ISSUES:
* Newspaper 6.7.1
* Newspaper 7.0
* WordPress prior to 4.7

MAKE A SECURITY PRACTICE POLICY CHECKLIST FOR YOUR SITE(S):
Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or hire a company to do it for you.

• This reply was modified 9 years by simchris.

Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or higher a company to do it for you.

Another good discussion on this topic, including a lengthy warning from WP Engine Hosting, is including in the thread titled Security Risk.

One user of the Newspaper theme received the following message:

At WP Engine we take security very seriously and make every effort to keep our customers aware of any potential issues. We are reaching out to you today because we identified your site(s) are utilizing the “Newspaper” premium theme.

We have been notified by Sucuri about a recent increase in exploits that specifically target outdated versions of this theme. They operate by injecting unwanted ads into the page’s links, directing visitors away from the intended site. You can read more about the specifics of the exploit here:

https://blog.sucuri.net/2017/06/unwanted-shorte-st-ads-in-unpatched-newspaper-theme.html

Due to the potential severity of this exploit, we strongly recommend that everyone using a version older than 6.7.2 update to the latest version. You can update this through the wp-admin dashboard, but if you have a customized version of the theme, you may want to consult with your developer to ensure your site does not encounter issues when updating. Please make sure to run a backup of your database first; which you can learn how to do here in an article: http://wpengine.com/support/restore/ or here in an interactive walkthrough: https://my.wpengine.com/dashboard/?walkthrough_id=2278

If your site does appear to be displaying the symptoms, the fix is quite easy to remove the exploited code. You will need to remove that code from the Newspaper theme panel’s “header ad” block in WordPress admin interface under Newspaper > Theme panel > ADS > YOUR HEADER AD. You can also replace it with your original ad code, and your site should return to normal. Be sure to update the theme in conjunction with making this change, as it will prevent any further compromises.

Update: I was using the wrong Facebook ID. Issue is now resolved.

For those of us on customized platforms, it’s not just simple to upgrade to the newest version. With our security policy, we usually only get hit when hacks use specifically whitelisted admin files such as admin-ajax.php which this hack does.

I’m not 100% certain as my change has been only live for a hour, but if you disable the td_ajax_update_panel action that the exploit uses, you can prevent the exploit from occurring. This is a stop-gap measure as this will also prevent you from updating any theme settings from the panel, so make sure you have them where you like them if you do this.

You can upgrade to the version 7.1x which is advisable if not wanting to go to 8x.

Also good to setup a security policy internally — you should be checking update changelog/readmes for *all* plugins/themes you use and for WordPress core — as the TagDiv theme security notice for 6.7x was included way back in April 2016:

Version 6.7.2 – April 27th, 2016
fix: social counter facebook issue with new API keys
fix: security issue

a minor issue with 7.0 was fixed with 7.1 for those early adopters who rushed to install 7.0

Version 7.1 – May 20th, 2016
fix: panel got stuck while saving in specific cases, mostly related to categories
fix: Related articles filter was not working with the settings from the panel if you choose related by tags and the post had no tags set.
fix: contributor users cannot change the post template now, this is more in line with WordPress
fix: Security issues
fix: back to top on ie9
fix: missing woocommerce add to cart on mobiles

==============
Everything on the web requires periodic checkups; it’s not static like old websites with static shtml files or similar. WordPress, plugins, PHP, MySQL, WooCommerce, etc., all need to be *checked* when updates are done — new features, no need to upgrade unless you read the help info first; for security patches, these should *always* be done when originally notified!

I don’t work here — but our ‘security practice policy’ internally forces us to CHECK when new updates come out to see WHY they were updated, in case of security issue(s).

Recommended you consider the same, or higher a company to do it for you.

Hi Chris, I update again to post erro if I disable td composer

My website: http://www.tutods.net

After update to 8.1 is required active tagdiv composer, if not active my homepage is appear with error.
Please help me :/