Always best to download the ‘all files’ as it includes the CHANGELOG so you know what actually changed with any major or minor update.
Theme uses built-in WP search functions; however there are plugins like ‘better search’ which provide enhanced search tools you could add to the site.
Likely because they are encouraging new first time users with v8 onward to use TD Composer and it’s part of the theme package; while VC is external bundled product and not ‘part of the theme’ and so is now ‘optional’ product.
Sounds like DNS error but checkup shows okay
https://mxtoolbox.com/SuperTool.aspx?action=https%3a%2f%2fbitcoinwarrior.net%2f&run=toolpage
Might be your own ISP.
Normal debug would be turn all extra post options OFF like related post, more from author, fly out, sidebar widgets; disable plugins; check server ERROR LOG for bad plugins.
Check system status in theme panel. You do need to have more RAM allocated to WP, longer timeout settings for php, etc.
You also need to setup your site/hosting properly for WordPress with things like GZIP/deflate, expiration headers, etc., which have nothing to do with the theme
https://gtmetrix.com/reports/bitcoinwarrior.net/O7Zrep1j
Need to fix bad requests, like
https://i0.wp.com/bitcoinwarrior.net/wp-content/uploads/2015/02/220x180.jpg?w=696&ssl=1
Always good to read changelog prior to install any major theme update.
I find it easier to edit the main files and keep track of changes; then reapply to new theme update if needed; less messy than working with child theme which might ALSO need to be updated with major theme update — which defeats purpose, in my mind anyway.
Might consider reading up on basic HTML … and how anchor links work
e.g.,
<a href="MYURL"><img src="bannerurl" /></a>
-
This reply was modified 8 years by
simchris.
Note most web hosts now provide free SSL certs to enable https/TLS secure connections; using ‘Let’s Encrypt’ — so all sites should be https now as part of the ‘https everywhere’ movement.
Chrome has started to ‘warn’ site visitors about unsafe sites not loading via https; and any online form/login will get large ‘not safe notice’ as of October 2017 —
so ‘best practices’ now would to be always plan for https everywhere as the standard.
Also useful to download theme folder (Newspaper) to your hard drive, open it and ‘explore’ what is actually in there 😉
Probably they forgot to update the screen photo in every download version 😉
Might just be the screen image; check the ‘system status’ tab 🙂
Did you do normal practice of clearing transients after update, e.g., with WP Optimize, and resaving permalinks to clear WP micro caching; clear any caching / CDN buckets, and clear browser cache before re-logging in ?
Just food for thought. Also useful to review changelog and posts about changes, as you likely could have just edited the one ajax file to modify the XSS issue and be done with it for the day.
( I don’t work here. But feel your pain ! )
For XMLRPC I actually use this in my htaccess file
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>
I think the change made was noted in another thread here couple of days back; you might have to search for that while waiting for TagDiv to respond. I believe it was only one ajax file.
Also, if you think about it, not wise to print a list of the XSS vulnerability code online in the open for hackers to see on Themeforest.
Likely good to fix all your console errors (F12/chrome) first. You have mixed content warnings, and various other things.
Also try disabling inline ads inside article.
/AMP/ and mobile plugin are two totally different things and unrelated.
The AMP plugin would serve the AMP version endpoint using template to those devices compatible with AMP, and mobile template shown to others.
You can hook the adsense ads into the amp template, using the Automattic AMP plugin; Google the topic as it’s not related to Newspaper in any way.
You generally need to edit the AMP template, or add function or plugin to hook the ad into the footer or header of the amp template via the hooks provided for that.
Food for thought anyway 🙂
Check your Google News sitemap to see WHAT is actually in there.
Check your search console for your Google News sitemap for crawl errors or errors in the sitemap you have submitted.
We’ve been a news publisher since 1981, and were one of the first sites in Google News 12 years ago. Started using WP for news portals with version 1.5.
ACF (Advanced Custom Fields) is a free plugin to make custom fields with more granular control including shortcodes and if/then usage of custom fields and formatting options. The PRO version adds more options and support, but not necessary for most things.
The Automattic AMP plugin by same folks who make WordPress allows you to ‘hook’ into the template via function, or modify the template to include whatever you want.
Both are free to use. No cost, no ‘premium’ functions, etc.
Food for thought anyway — we do it on our 15 news portals right now, all in AMP. 10 in Google News and BING News; 2 in Apple News.
Just feedback on the topic as long time AMP user and early adopter when it was first in BETA.
You can simply add a custom field using something like ACF, then load that into the footer of the AMP template. I do that to include our text-based ‘related stories’ shortcode; which gets added to footer via the normal AMP includes command for the Automattic plugin. So simple to do that kind of stuff for free if you read up on it. You can also simply edit the AMP template and add the “if field populated print it here” type of thing.
Food for thought anyway. 🙂
The Automattic AMP plugin works very well, we’ve been using it since AMP was in BETA.
It’s in the theme folder, inside wp-content, in the folder shown.
All WordPress themes live inside the /themes/ folder, not the WordPress core folders.
I use the AdRotate plugin here 🙂
This really should be a toggle on/off feature in the theme; I also find it distracting myself.
It means that it’s not on the built-in list of plugins which get automatically moved and optimized by the plugin.
if you read the docs, you can manually add that to the plugin to use them together.