xelan54

Thanks for the reply. I appreciate your response.

This was an conflict with the Jetpack Boost “optimize critical CSS” option.

It’s binary. Turn this off, and EFB works fine. Turn it on and it fails.

Voila!

Thank you very much, @westonruter.

Here’s the output, @westonruter. Thanks for all your work on my behalf.

Notice: is_amp_endpoint() was called prematurely.
Hook stack: init, show_admin_bar
Backtrace: #0  AMP_Doing_Endpoint_Check_Wrong_Debugging\{closure}(is_amp_endpoint) called at [/var/www/html/wp-includes/class-wp-hook.php:289]
#1  WP_Hook->apply_filters(, Array ([0] => is_amp_endpoint,[1] => is_amp_endpoint() was called before the parse_query hook was called.,[2] => 0.4.2)) called at [/var/www/html/wp-includes/class-wp-hook.php:311]
#2  WP_Hook->do_action(Array ([0] => is_amp_endpoint,[1] => is_amp_endpoint() was called before the parse_query hook was called.,[2] => 0.4.2)) called at [/var/www/html/wp-includes/plugin.php:478]
#3  do_action(doing_it_wrong_run, is_amp_endpoint, is_amp_endpoint() was called before the parse_query hook was called., 0.4.2) called at [/var/www/html/wp-includes/functions.php:5131]
#4  _doing_it_wrong(is_amp_endpoint, is_amp_endpoint() was called before the parse_query hook was called., 0.4.2) called at [/var/www/html/wp-content/plugins/amp/includes/amp-helper-functions.php:589]
#5  is_amp_endpoint() called at [/var/www/html/wp-content/plugins/jetpack/3rd-party/class.jetpack-amp-support.php:103]
#6  Jetpack_AMP_Support::is_amp_request() called at [/var/www/html/wp-content/plugins/jetpack/3rd-party/class.jetpack-amp-support.php:67]
#7  Jetpack_AMP_Support::show_admin_bar(1) called at [/var/www/html/wp-includes/class-wp-hook.php:287]
#8  WP_Hook->apply_filters(1, Array ([0] => 1)) called at [/var/www/html/wp-includes/plugin.php:206]
#9  apply_filters(show_admin_bar, 1) called at [/var/www/html/wp-includes/admin-bar.php:1224]
#10 is_admin_bar_showing() called at [/var/www/html/wp-content/plugins/all-in-one-seo-pack/admin/aioseop_module_manager.php:170]
#11 All_in_One_SEO_Pack_Module_Manager->do_load_module(feature_manager, Array ([0] => sitemap,[1] => opengraph,[2] => robots,[3] => file_editor,[4] => importer_exporter,[5] => bad_robots,[6] => performance,[7] => video_sitemap,[8] => image_seo)) called at [/var/www/html/wp-content/plugins/all-in-one-seo-pack/admin/aioseop_module_manager.php:95]
#12 All_in_One_SEO_Pack_Module_Manager->__construct(Array ([0] => sitemap,[1] => opengraph,[2] => robots,[3] => file_editor,[4] => importer_exporter,[5] => bad_robots,[6] => performance,[7] => video_sitemap,[8] => image_seo)) called at [/var/www/html/wp-content/plugins/all-in-one-seo-pack/inc/aioseop_functions.php:42]
#13 aioseop_load_modules() called at [/var/www/html/wp-includes/class-wp-hook.php:287]
#14 WP_Hook->apply_filters(, Array ([0] => )) called at [/var/www/html/wp-includes/class-wp-hook.php:311]
#15 WP_Hook->do_action(Array ([0] => )) called at [/var/www/html/wp-includes/plugin.php:478]
#16 do_action(init) called at [/var/www/html/wp-settings.php:540]
#17 require_once(/var/www/html/wp-settings.php) called at [/var/www/html/wp-config.php:89]
#18 require_once(/var/www/html/wp-config.php) called at [/var/www/html/wp-load.php:37]
#19 require_once(/var/www/html/wp-load.php) called at [/var/www/html/wp-blog-header.php:13]
#20 require(/var/www/html/wp-blog-header.php) called at [/var/www/html/index.php:17]

I got lucky. I only had to disable the second plugin in the UI.

It’s always “the other guy“. ??

We should probably just send the AIO SEO folks the link to this discussion and let you get some sleep, @westonruter.

Thank you very much for the effort.

Unfortunately, no joy in my case.

…and the error appears more frequently in Microsoft Edge (macOS) than in “real” Google Chrome. If that’s any help.

…and I appreciate it.

I think it’s this widget: https://jetpack.com/support/extra-sidebar-widgets/cookies-consent-banner/.

Remove it and all’s well. Makes sense to me because I first noticed the issue when using that widget and Jetpack won’t run when Amp is enabled.

The fatal flaw in the WordPress ecosystem: it’s always the other plugin’s fault.

Until your recent update, something else was “doing it wrong” and everything was fine.

Well, from the perspective of every other plugin, this one IS the problematic one.

And…it breaks Jetpack. It’s binary: turn on AMP and no Jetpack dashboard. Turn it off, and all’s well.

Q1: No, I don’t think so.

Q2:

+------------------------------------------+----------+------------------------------+------------+
| name                                     | status   | update                       | version    |
+------------------------------------------+----------+------------------------------+------------+
| akismet                                  | active   | none                         | 4.1.4      |
| all-in-one-seo-pack                      | active   | none                         | 3.4.2      |
| amp                                      | inactive | none                         | 1.5.2      |
| classic-editor                           | active   | none                         | 1.5        |
| clicky-analytics                         | active   | none                         | 1.6.1      |
| contact-form-7                           | active   | none                         | 5.1.7      |
| easy-fancybox                            | active   | none                         | 1.8.18     |
| enlighter                                | active   | none                         | 3.11.0     |
| invisible-recaptcha                      | active   | none                         | 1.2.3      |
| iq-block-country                         | active   | none                         | 1.2.7      |
| jetpack                                  | active   | none                         | 8.4.1      |
| gallery-by-supsystic                     | active   | none                         | 1.14.6     |
| redirection                              | active   | none                         | 4.7.1      |
| wpcf7-redirect                           | active   | none                         | 1.3.5      |
| sqrl-login                               | active   | none                         | 2.1.0      |
| updraftplus                              | active   | version higher than expected | 2.16.23.24 |
| vaultpress                               | active   | none                         | 2.1.1      |
| wordfence                                | active   | none                         | 7.4.6      |
| wordpress-popular-posts                  | active   | none                         | 5.1.0      |
| wp-optimize                              | active   | none                         | 3.0.19     |
| auto-terms-of-service-and-privacy-policy | active   | none                         | 2.3.2      |
| wpb-twitlinks                            | active   | none                         |            |
| wp-mail-smtp                             | active   | none                         | 1.9.0      |
+------------------------------------------+----------+------------------------------+------------+

Q3: How’s this for broken? ??

• This reply was modified 4 years, 7 months ago by xelan54.

Sorry, I’m not deactivating a plugin that has worked reliably for me for years, especially when it’s binary that when a Jetpack feature (I am unsure of which one) is on, comments disappear; when it’s off, they work fine. Plus, I’ve already deactivated ALL my plugins except for Jetpack, entered a comment and watched it disappear.

While I’d expect other plugins to point fingers, I’m surprised that the Jetpack devs (who have delivered so much value to WordPress) do it.

Hello,

Here’s a link to the plugins installed on my blog.

But this isn’t the problem; Jetpack is. I disabled all plugins but the disappearing comments continued to disappear. Then, I started disabling Jetpack features — and I think it was Photon that, once disabled, fixed the problem.

Thx.

Thanks, nlmosler.

I’d tried this and it doesn’t work when used in either the styles.css of the child theme or in the edited CSS provided by Jetpack.

I don’t want to modify the base theme but I cannot understand why it’s so impossible to find a way to override a span in the theme.

I’m beginning to wonder if there’s a bug in twentysixteen, given that it’s newly released.

I scheduled two posts that didn’t publicize — even through previous ones had.

The site is https://www.zixi.com.

Now that the posts have been published, when I edit the publicize settings, I can see my text and the short link, but it wasn’t shared with Twitter, LinkedIn and/or Facebook.

Would appreciate any suggestions.