Thread Starter
vich11
(@vich11)
Where do you see it inserted? It should appear below the Keywee code in the header and it is not there.
Also, do you have any explanation for how or why it DOES work for logged in users but does not for non-logged in? This makes no sense to me.
On a related note, the opposite happens to me with the regular display ads. When I’m logged in, no display ads appear, but when not logged in all display ads load normally.
Thanks
Thread Starter
vich11
(@vich11)
Thank you. That change allowed the in-content code to render, but no matter what I try I can’t get the code that goes in the head section to render. And I still can’t figure out why it works when logged in but not when logged out. Here’s the head code if it helps:
<script type=”text/javascript”>
console.log(‘taboola test’);
window._taboola = window._taboola || [];
_taboola.push({article:’auto’});
!function (e, f, u, i) {
if (!document.getElementById(i)){
e.async = 1;
e.src = u;
e.id = i;
f.parentNode.insertBefore(e, f);
}
}(document.createElement(‘script’),
document.getElementsByTagName(‘script’)[0],
‘//cdn.taboola.com/libtrc/warp10llc/loader.js’,
‘tb_loader_script’);
if(window.performance && typeof window.performance.mark == ‘function’)
{window.performance.mark(‘tbl_ic’);}
</script>
Thread Starter
vich11
(@vich11)
Update:
The issue seems to be specifically related to Taboola code. Regardless of whether it is a div with taboola in the ID name or Taboola related javascript. I just added some other code and it worked fine.
Thread Starter
vich11
(@vich11)
Just not using it. Doing plugin cleanup.
Thread Starter
vich11
(@vich11)
I was able to successfully deactivate and remove the plugin today for some reason, so the issue is resolved.
Thanks
Thread Starter
vich11
(@vich11)
Yes, it is. I reinstalled the plugin so I wouldn’t have a permanent error message at the top of my plugins page.
Thread Starter
vich11
(@vich11)
Gotcha. Thanks again very much.
Thread Starter
vich11
(@vich11)
You are the man. That was it. For my own edification, how did that stack trace point you to that? I never would have deduced that.
Thanks very much!
Thread Starter
vich11
(@vich11)
Ah! Thanks, I will look into that ASAP and see what happens if I remove it.
Thread Starter
vich11
(@vich11)
I don’t understand the use of JS to determine 75% of images don’t have those attributes, but images used in posts do have height/width, and what’s that got to do with the AMP version of the page?
I see two items with no height/width but those are inside javascript, not actual images.
Here is an example from New Relic:
Query
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE ?=? AND wp_posts.ID NOT IN (?) AND (
wp_term_relationships.term_taxonomy_id IN (?,?,?,?,?)
) AND wp_posts.post_type = ? AND (wp_posts.post_status = ?) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT ?, ?
Database instance
vps-gamerant-cluster.cluster-czvuylgsbq58.us-east-1.rds.amazonaws.com:3306
Database name
db_dom9972
Stack trace
in mysqli_query called at /wordpress-4.9.8/wp-includes/wp-db.php (1924)
in wpdb::_do_query called at /wordpress-4.9.8/wp-includes/wp-db.php (1813)
in wpdb::query called at /wordpress-4.9.8/wp-includes/wp-db.php (2454)
in wpdb::get_col called at /wordpress-4.9.8/wp-includes/class-wp-query.php (2821)
… WP_Query::get_posts called at /wordpress-4.9.8/wp-includes/
class-wp-query.php (3230)
in WP_Query::query called at /wordpress-4.9.8/wp-includes/class-wp-query.php (3336)
…WP_Query::__construct called at /dom9972/wp-content/themes/8.9K/amp/
single.php (54)
…/dom9972/wp-content/plugins/amp/includes/templates/
class-amp-post-template.php (441)
…/dom9972/wp-content/plugins/amp/includes/templates/
class-amp-post-template.php (211)
…/dom9972/wp-content/plugins/amp/includes/templates/
class-amp-post-template.php (200)
in AMP_Post_Template::load called at /dom9972/wp-content/plugins/amp/amp.php (328)
in amp_render_post called at /dom9972/wp-content/plugins/amp/amp.php (279)
in amp_render called at /wordpress-4.9.8/wp-includes/class-wp-hook.php (286)
…P_Hook::apply_filters called at /wordpress-4.9.8/wp-includes/
class-wp-hook.php (310)
in WP_Hook::do_action called at /wordpress-4.9.8/wp-includes/plugin.php (453)
in do_action called at /wordpress-4.9.8/wp-includes/template-loader.php (12)
in require_once called at /wordpress-4.9.8/wp-blog-header.php (19)
in require called at /wordpress-4.9.8/index.php (17)
I’m not an expert on all this, so I’m not sure. You can see here the relative usage of AMP compared to the next couple of plugins: https://gamerant.com/ampusage.PNG
Thread Starter
vich11
(@vich11)
Redis object caching is now active on the site, but this doesn’t seem to be helping.
When I look at the AMP version of a page, it seems to have width and height attributes so I’m not sure what you’re referring to. For example when I look at the source of this page:
https://gamerant.com/destiny-2-get-more-seeds-of-light-super-skill-trees/amp/
Every single image has both a height and width attribute.
Yes, thanks, the message is gone. I still don’t understand why there was ever a message in the first place as my AMP template should be 100% compliant.
So the only difference is that message was hidden before and in this version it’s visible?
What I don’t get is there shouldn’t be anything in my AMP template that is not AMP compliant…. If the page validates, then what is the plugin removing?
No way to attach an image here, but this is what it said:
Warning: There is content which fails AMP validation; it will be stripped when served as AMP. Debug
Invalid elements: script
“Debug” was a link to the post page with debugging enabled.
“script” was in a grey box.
-
This reply was modified 8 years ago by vich11.
Also, I’ve made no changes to my site/AMP code. Only change was updating the plugin. Everything was valid previously. I made a backup of the previous version of the plugin I had been running, restored it to active, and I no longer get the error message. The version I was (and am again) using is 0.6.2. It was 0.7.0 which caused the error.
