designative
Forum Replies Created
-
This is what I mean by the icon being broken (check the screenshot attached): look at the square next to the Mastodon label inside the sharing button.
As for conflict with the theme, I’m using the Twenty-Twenty Theme, which is the standard theme from WordPress itself… I would assume you would test new functionality with — at least — the default theme from WordPress
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Publicize and MastodonHi, there! In the latest update of your plugin, we got the “share to mastodon” button. The sharing functionality seems to work fine, but the Mastodon Icon is broken.
I’ve cleared the cache, I’ve regenerated the CSS with Jetpack boost, tried access AMP versions of pages to see if it makes any difference, and still the Mastodon icon is still missing.
Hi, there! In the latest update of your plugin, we get the “share to mastodon” button. The sharing functionality seems to be working fine, but the Mastodon Icon is broken.
I’ve cleared the cache, I’ve regenerated the CSS with Jetpack boost, tried access AMP versions of pages to see if it makes any difference, and still the Mastodon icon is still missing.
Forum: Plugins
In reply to: [AMP] Comment on Amp PageI know this thread has been marked as resolved, but I’m wondering if this issue is back:
– I’ve recently switched to the wordpress default theme (Twenty Twenty) with no customisations at all;
– I had Jetpack comments enabled by default for all posts;
– Every post that I convert to blocks (or if I start a new one in block edit mode) returns an AMP error (pointing to the jetpack comment block);
– If I disable commenting for the post, AMP works just fine.I had other issues also with the Cookies & Consent Banner (also for Jetpack) that also breaks in AMP. Any updates on the AMP compatibility with Jetpack?
I’m using the AMP plugin (https://wordpress.org/plugins/amp/) and I’m getting a a few errors showing up in multiple pages in validation index:
– Invalid attribute on https://jetpack.wordpress.com/jetpack-comment/
– Invalid script: …/wp-content/plugins/jetpack/_inc/build/widgets/eu-cookie-law/eu-cookie-law.min.js- This reply was modified 5 years, 11 months ago by designative.
Forum: Plugins
In reply to: [Stackable - Page Builder Gutenberg Blocks] AMP?I’m getting some validation errors from the AMP plugin:
“Arbitrary JavaScript is not allowed in AMP. You cannot use JS <script> tags unless they are for loading AMP components (which the AMP plugin will add for you automatically). In order for a page to be served as AMP, the invalid JS code must be removed from the page. Learn more about how AMP works. As an alternative to using custom JS, please consider using a pre-built AMP functionality, including actions and events (as opposed to JS event handler attributes like onclick) and the amp-bind component; you may also add custom JS if encapsulated in the amp-script.
If you remove the invalid markup then it will not block this page from being served as AMP. Note that you need to check what impact the removal of the invalid markup has on the page to see if the result is acceptable. If you keep the invalid markup, then the page will not be served as AMP.Error code
DISALLOWED_TAG
Invalid markup
<script … >Element attributes
src …/wp-content/plugins/stackable-ultimate-gutenberg-blocks/dist/frontend_blocks.js
Element name
script
Parent element
headSo I thought, but even my wordpress dashboard (which is not cached by Cloudflare) was responding with “cannot connect to database”.
Forum: Themes and Templates
In reply to: [Hueman] Customisations reset every time wordpress autoupdatesI’ll try that, thanks!
In the meantime, I found some other information that I hope it is useful:
– In the “site health status” saying I have one critical issue “A plugin has prevented updates by disabling wp_version_check()”
– it also says “your site could not complete a loopback request: The loopback request returned an unexpected http status code, 403, it was not possible to determine if this will prevent features from working as expected.”I’ve done all of the above (except changin the .htacces rules, since I can’t find it) and my site is still down with the 500 internal server error! Even other sites in my subfolders are also down now!
What should I do?