If you are using WooCommerce, you likely would need to find a plugin for that, since WC is separate from the main core functions of WP, or the theme itself which is more focused on the content, and not user/customer features.

(I don’t work here, just feedback having used WooCommerce for several years now – there are lots of extension/plugins for stuff like that — as you need to have a more focused way to manage who can login and then use same account to buy stuff later, or send ‘buy’ or ‘recommended’ stuff to friends and track that, etc.)

Probably have to google that, ironically. Google shows amp version of pages in serps but may show a redirect link for its cached version of page.

May want to also double check your amp endpoints actually have the canonical link to the non amp page.

• This reply was modified 8 years by simchris.

Update plugins, resave permalinks, clear cache

WordPress has ‘oembed’ to allow posts from one site to embed in others, just like with a video or tweet.

There are functions and plugins you can use to stop/disable this ability — nothing to do with the theme, but core feature of WordPress itself.

False positive. Search the forum for ‘vaultpress’ to see past posts on this topic.

Likely want to remove the javascript if you didn’t add it; then check your site with securi scanner for possible malware, change all your passwords, and make sure you have updated WP for the latest security flaw patched this week!

Also consider ‘hardening’ your website per the topic in the official WordPress docs on wordpress.org

You can easily add a GDPR privacy statement to your site, and numerous plugins to show a visitor a cookie message, which presumably you’re already doing for European visitors. You already have options to remove Google fonts, so very little to deal with really.

Also WordPress core added features to export ‘personal data’ in core updates this past month.

• This reply was modified 8 years by simchris.

Did you check your robots.txt file, and also resave your permalinks, then actually try going to the page yourself from the /amp/ endpoint ?

If you can’t reach it yourself in web browser, Google can’t either.

( I don’t work here. )

Probably need to share examples of WHAT errors you’re having.

Also useful to use Chrome Console view (F12) to view actual issues with your site, as seen by Google.

Best bet is delete old plugin versions via ftp, then manually install from the all files download, unzip and upload clean versions via ftp.

Tip… view your page source in browser, see what open graph data actually there. Also good to always add manual excerpt.

You can update the plugin without updating the theme. Download the ‘all files’ and look in the various folders for the different plugins and related content included with the theme.

Be sure to keep backups of everything via FTP before updating anything, so that you can ‘roll back’ if something breaks.

Also see the docs on how to update theme. Good idea to make backups of all your custom settings, dbase, etc., if you have not already done so.

• This reply was modified 8 years by simchris.

Yoast has been very buggy with past couple of updates; they just pushed new update today 6.29.18 for their latest (sigh) bug fixes.

Usually found in the readme file in the file download. Save it to your hard drive, unzip, and the changes usually noted there 🙂

Hm. I think we might have removed the item from the actual menu template on our sites. Removing that won’t turn off the search function, just remove from the theme. We use sidebars for iPad and desktop, and moved the search box there instead.

You’d still need to use function to remove overall search functions, as that has nothing to do with the theme.

I will be quiet and let TagDiv folk reply on how to remove the search element from the main menu; I thought they’d added a toggle for that! (doh)

• This reply was modified 8 years by simchris.

I think you can disable the search item in the menu from the theme panel.

Theme does not control ‘core’ WP functions however, like search. You would need either a separate plugin for that, or custom function added to your functions file (or custom plugin for your functions to survive theme updates).

e.g.,

function wpb_filter_query( $query, $error = true ) {
if ( is_search() ) {
$query->is_search = false;
$query->query_vars[s] = false;
$query->query[s] = false;
if ( $error == true )
$query->is_404 = true;
}
}
add_action( 'parse_query', 'wpb_filter_query' );
add_filter( 'get_search_form', create_function( '$a', "return null;" ) );
function remove_search_widget() {
unregister_widget('WP_Widget_Search');

add_action( 'widgets_init', 'remove_search_widget' );

I stopped using WPBakery 3 years ago, myself; back when TDC and the VC ‘shim’ were in beta; so….. ‘hella yeah’ would be my reply 😉

Note they are not 1:1 things; if you have been using WPB and move to TDC, not all shortcodes the same, or some extensions; so you might have to redo some things on homepage to use the TDC … in my case, the original ‘shim’ came about as I was one of the folks on our old web server getting CPU spikes going from “3” to “78” (!) with WPB. Won’t use it here ever again, personally.

• This reply was modified 8 years by simchris.

Theme is responsive. What are you referring to that is not?
Responsive means that elements load at different sizes based on viewport.

You can test this by dragging ‘in’ the edge of web browser and see how the page resizes and moves elements to fit.

Main thing is to make choices on number of queries, such as not having five different size modules on every page; and try to limit home page to clever layouts maybe only using three different module types.

Also, optimize your site for common issues of overloads by using a plugin like limit login attempts to stop bots trying to guess passwords via your login form, block XMLRPC, and see the security hardening page on wordpress.org to help stop certain things from access.

Heh … welll….. tech support folk vary in actual knowledge, sadly. I only knew about this as I helped a client couple years back setup his website, and every time I went to update a page with changes it would not show up, and had to go into the GoDaddy panel to clear the aggressive caching.

Their tech support site is way better than it was 5 years ago, so good to bookmark that for a lot of common “what the heck” questions — especially if their tech support person is clueless. 🙂

that message ‘This plugin is not allowed on our system due to performance, security, or compatibility concerns. Please contact support with any questions’ is from your hosting provider; as the ‘theme’ doesn’t control plugin setup other than it’s own internal plugins, not third party plugins from wordpress.org.

‘our system’ is the important note — the theme has nothing to do with ‘your system’ — that is the hosting provider.

Google is also your friend for doing simple searches
“using WP Super Cache with GoDaddy hosting”

Managed WordPress Help
Note: This article applies to all Managed WordPress Basic, Deluxe, Ultimate, and Developer accounts. Plugins are not blacklisted for Pro accounts (available in U.S.A. and Canada only).
https://www.godaddy.com/help/blacklisted-plugins-8964

Caching — Your Managed WordPress account already has caching built into it.
However, if your site is slow, try these suggestions:

Check common performance issues on your website.
Contact customer support. If your site is still slow, we want to know why and how we can help.

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

disable the lazy load animation on the page as first step

maybe try a more standard approach, then retest your pages

http://www.wpbeginner.com/wp-tutorials/how-to-optimize-your-wordpress-robots-txt-for-seo/

https://support.google.com/webmasters/answer/6062596?hl=en

and of course: TEST YOUR ROBOTS.TXT FOR GOOGLE:
https://support.google.com/webmasters/answer/6062598

“Not allowed by WordPress” — means what exactly? Do you mean hosted as a WordPress VIP, or what “WP System” do you mean – *exactly* ?

Are you saying your web hosting service does not support it?

If your hosting is saying not allowed, best to reach out to them and ask WHAT caching is allowed; for example they may be running opcache and varnish and you may not need a caching plugin.

Or, you may have a budget account that doesn’t allow certain plugins at all due to consuming too much system resources.

Folks might be better able to assist if you give a wee bit more info 🙂

( I don’t work here; just webdev dinosaur since 1995 )

Which plugin are you using?
Often if using a plugin, it can be useful to resave permalinks, then check the link in the plugin to see if the sitemap actually works or not. (e.g., Yoast SEO, All in One SEO, or simple sitemap plugin).

Sometimes turning the plugin or sitemap option off, then back on will start working. Also see the support forum for the plugin you’re using, if the above suggestions don’t work.