Edit your dbase via mysql phpmyadmin or plugin

Note – renaming theme folder will likely cause you to have to re-enable the theme from WordPress if you also rename the theme in the style sheet (the advanced method in addition to changing folder name). So, make sure you have backups of everything including all your settings from theme panel which you should already have backed up after cleaning.

The idea is
a) hide WP version
b) hide theme name by folder and style.css reading (style sheet is public, so ‘name’ is in there for bots to find)
c) perhaps even change the version in the style sheet to something like 44.6.66 vs 4.6.1 or whatever

so if your folder and style sheet say ‘newspooper’ vs ‘newspaper’ and different version number, and you block XMLRPC (known attack vector); you have a little bit of safety from bots ‘trolling the web’ for vulnerable versions.

In fact when I check my site running newsmag using this methodology, the “what theme are they using” site says “site not running wordpress…” — so a ‘win’ there.

Food for thought for those not wanting to upgrade. I can’t provide any other help than as noted, as I don’t work here — but ideas for those of you on older versions.

This may help while waiting for reply from TagDiv on specific file to remove — however theme may not work with some edits:
https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/

One option if not ready to upgrade, after cleaning boxes and dbase
a) rename theme folder to something else (newspooper)
b) add function in the functions.php to remove versions/XMLRPC in the post data.

remove_action('wp_head', 'rsd_link');
remove_action('wp_head', 'wlwmanifest_link');
remove_action('wp_head', 'wp_generator');
add_filter('xmlrpc_enabled', '__return_false');

disable xml-rpc in your htaccess file (if using Apache hosting)
# Block WordPress xmlrpc.php requests
<Files xmlrpc.php>
order deny,allow
deny from all
allow from 123.123.123.123
</Files>

( also if using Yoast Seo, I will trick them a little by changing the 1000 number to 900 which forcibly changes the sitemaps ! ) (nyah hah ha !)

Often you can accelerate the process by resubmitting your sitemap in the search console 🙂

If you want to see URL in SERPS (which is redundant), vs breadcrumb links, you would need to actually disable breadcrumbs on the theme. Google will pick those up if on the page regardless of any meta data.

Sure, if you want to pay me. I don’t work here, I was just pointing you at the location of where to find things — if you download the ‘all files’ zip from your ThemeForest account, there are files right there listing the changes. Enjoy!

See the changelog files in the all files download zip from Themeforest.

@MTUK
So the embeds are actually in the RSS when you look at the feed?

This thread was about issues taking RSS feed into Instant Articles.

If your issue is unrelated to RSS feeds, likely want to start your own topic!

As a general note, we’re not having any issues here with any of our cron scheduling with the TagDiv themes. Sorry not helping, just a note.

You can hire somebody through their hire people service. Look for links bottom of tf website

Its in your account on themeforest under downloads

that is probably part of your other theme so goes away when you disable theme … try going to twenty sixteen theme to see same behavior. If that is from a plugin, it might be a conflict so you need to turn debug on.

Oembeds with iframes dont normally appear in rss feeds. Theme does not control rss feeds. You can make your own custom feed and include whatever you want using custom fields or rewrite options.

WooCommerce did a notable update this month. Might have a bug.

After updating I usually do this
a) clear transients with WP-Optimize plugin
b) resave permalinks

I have an issue with the last version of WooCommerce where the coupon setting won’t let me pick a single item to exclude … supposedly fixed in new version, but have not yet updated (doing that on Saturday).

Woo keeps updating with stuff, but then fixing bug, but then introducing new bugs that break plugins and other stuff. Annoying.

That was probably just “I know how you feel….” comment there, sorry 🙂

Clear it?

https://premium.wpmudev.org/blog/understand-caching-in-wordpress-part-1-the-basics/

see if your hosting platform using cache plugin (e.g., GoDaddy); see if you have a caching plugin installed/active (good to know WHAT plugins you’re running); clear your browser cache.

You can also try
a) clear transients with free WP-Optimize plugin (I use it literally every day!)
b) resave permalinks

But, see the article link to understand what caching is.

Yes. This is how WordPress works – it ‘clears’ the active widgets when changing themes. It’s not theme related.

Usually it will move the items to bottom of appearance > widgets as ‘deactivated’ and you can drag stuff back into working widget boxes.

WordPress does this, as otherwise site would crash trying to do queries for non-existant theme code for a widget from theme running on different theme.

Welcome to WordPress! 🙂

I think there is a plugin, I’ve not tried it, which allows you to save the ‘state’ of widgets, so you can go between themes and keep widgets as is (maybe it’s ‘theme switcher’ ?). Not sure. But you can go to WordPress.org and look at plugin repo to check that.

( I don’t work here – just some advice. )

Probably useful to send the error logs showing WHAT the actual error is, to TagDiv by email.

We don’t have this issue on any of our sites, so dunno.

You might ensure you have your site set as https in the WP admin settings and/or in your wp-config.php file.

Likely useful to use console in Chrome to see what the actual error *is* and share that here?

( I don’t work here. )

Usually a caching issue. If the old theme no longer activated, how else could that happen?

You need to sign up for the update notification on Themeforest in your account, where you bought the theme. “WordPress” can’t update you as it’s not in theme repository on WordPress.org.

DUPLICATOR plugin is best way; I’ve used this last year when I wanted to change the name of a site from really long URL to shorter site name; was awesome as it not only moved all the dbase stuff properly, settings, etc., but images, folders, permissions, and went in and changed the site name throughout everywhere. Really brilliant thing there.

The WP export/import doens’t work on large sites and/or oooold sites that started with WP 1.5 like ours did (!). You can try export of the MySQL dbase, then setup blank site at new location and import the old dbase to move all the content properly, then FTP image from one location to another (takes forever).

Alternately, good hosting companies that use Plesk or Cpanel have ‘site move/migrate’ scripts to move entire site from one hosting company to another — which your host could do for you.

Open the changelog in the ‘all files’ download to see which files have been edited.

However, I’m sure TagDiv will be able to share just which files to replace.

https://enable-cors.org/server_nginx.html

https://stackoverflow.com/questions/27955233/nginx-config-for-cors-add-header-directive-is-not-allowed

etc.

Google:
https://www.google.com/search?q=how+to+add+CORS+rule+on+nginx&oq=how+to+add+CORS+rule+on+nginx&aqs=chrome..69i57.5311j0j7&sourceid=chrome&ie=UTF-8

Yoast has a support forum on WordPress.org for the free version; for the pro/paid version you have direct support with 24-48 hour replies direct from Yoast co. They have a github page to submit verifiable and reproducable bugs; and this is why they often have many ‘dot updates’ after a new full version (so it’s wise to WAIT when they do v 5 for 5.0.3 or whatever; this is very common with them). Also good to keep prior versions to roll back if mission critical as with *all* plugins.