macgeekgab
Forum Replies Created
-
Forum: Plugins
In reply to: [AMP] Using in-house/custom Analytics causes JavaScript ErrorsThanks @westonruter.
I think this behavior is intentional to AMP (at least from my research this morning).
If you specify a
typethen it presumes you’re using a vendor definition and, when you’re using a vendor definition, the transport should be defined by the analytics vendor and not overridden by the publisher.It would be possible, for example, for a vendor to only support GET requests, and then a publisher attempts to override that with a transport method that uses POST request and now thing are broken, hence the error. (Honestly I think it should be a warning and not an error, but, hey, the internet exists for opinions, right? 🙂
With
typeabsent, it knows you’re not using a vendor definition andtransportis an acceptable thing to define.Forum: Plugins
In reply to: [AMP] Using in-house/custom Analytics causes JavaScript ErrorsFor example, this code works 100% fine, and tracks 100% fine, except the plugin is adding that
typefield (as above) which throws the error.{ "triggers": { "trackPageview": { "on": "visible", "request": "pageview" } }, "transport": { "beacon": false, "xhrpost": false, "image": true }, "requests": { "base": "https://site.com/path/to/analytics/pixel.gif&rnd=${random}", "pageview": "${base}" } }Forum: Plugins
In reply to: [W3 Total Cache] Invalid AMP with Minify enabledFor anyone driving by, we solved this simply went to Dashboard > Performance > Minify > Advanced > Never minify the following pages and put /amp/ in there. That seems to have done it.
Forum: Plugins
In reply to: [W3 Total Cache] Moving CSS to HTTP Body causes Facebook og:image issuesAhh, gotchya. THanks, @vmarko – I posted here thinking it was the right place, and thinking others may have a similar issue.
Out of curiosity, how large are your CSS? A better way to ask that question: how many lines down is it before the Facebook Debugger shows your OG tags? Ours were in the ~4500 range.
Forum: Plugins
In reply to: [W3 Total Cache] Moving CSS to HTTP Body causes Facebook og:image issuesThanks, @vmarko – I’m confused as to what other plugin would be causing this problem? Can you help clarify for us what issue you think we should be investigating?
From looking at the OG Debugger, it seems pretty clear that Facebook is just stopping its parsing at a certain point, and since we have ~47K of CSS, it’s not going past that to get to the META OG tags. I’m not sure what other plugin would be at play here, but obviously I could be misinterpreting something?
Thanks!
(P.S. We are paid Pro members, if that helps! 🙂
Forum: Plugins
In reply to: [W3 Total Cache] Moving CSS to HTTP Body causes Facebook og:image issuesHi @vmarko! Thanks for this. HTML Minify didn’t seem to affect this in my testing. The only thing that seemed to matter was the “Eliminate render-blocking CSS by moving it to HTTP body”, unfortunately.
I looked at the Facebook debugger with all the permutations I could manage, and I’m pretty sure this was the only one that worked,
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack’s Photon Breaks RSSThanks, @jeherve. That’ll do it! 🙂
Forum: Fixing WordPress
In reply to: Can I bypass Jetpack Photon for a specific field?@jeherve Ahh, perfect. Thank you! Either the page ID or
is_feedconditional would be brilliant for us. Thanks so much. We’ll get to work!Forum: Fixing WordPress
In reply to: Can I bypass Jetpack Photon for a specific field?@jeherve Ahh, perfect. Either the page ID or
is_feedconditional would be brilliant for us. Thanks so much. We’ll get to work!- This reply was modified 6 years, 1 month ago by macgeekgab.
Forum: Fixing WordPress
In reply to: Can I bypass Jetpack Photon for a specific field?Thanks @sterndata – They told me to come and ask here. 😉 https://ww.wp.xz.cn/support/topic/jetpacks-photon-breaks-rss/#post-12755784
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack’s Photon Breaks RSSThanks for your help!
I re-enabled site accelerator and I think you might have gotten us down the right path. Because… the images in /feed/ also have the parameters after them:
src="https://i1.wp.com/www.macobserver.com/wp-content/uploads/2019/03/workfeatured-spotify.png?resize=1200%2C630&ssl=1"…but it validates, whereas our /feed/everything/ does NOT. And now I think I know why. We are *also* using the media:content for our images, and it seems the namespace for that does not support URLs with parameters. But… I can remove that and work around it. (we use custom fields and custom post types, hence the need for custom RSS creation).
However… we’re also podcasters, and this image is required atop every single podcast feed:
<image> <title>Mac Geek Gab</title> <link>https://www.macobserver.com/show/mac-geek-gab</link> <url>https://i0.wp.com/www.macobserver.com/wp-content/uploads/2020/03/macgeekgab_logo_sans_Finder-600px.png?fit=600%2C600&ssl=1</url> <width>144</width> <height>144</height> <description>Mac Geek Gab Podcast</description> </image>Unfortunately, having those parameters in the <url> breaks every podcast validator in existence, and we can’t have that. So… same problem, different place. Is there a way to invoke an image without having Site Accelerator affect it?
So… we’ve had to turn off Site Accelerator for now. If you’d like to setup a specific time to check it out, I’m happy to do that for you, but we can’t leave it like this, unfortunately.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack’s Photon Breaks RSSThanks for helping!
The site is https://www.macobserver.com/ and our RSS is https://www.macobserver.com/feed/everything — But we have Photon disabled right now because it breaks our RSS.
Happy to do whatever we can to show you what’s going on. Just let me know what you need and we’ll take it from there.
Forum: Plugins
In reply to: [Publish To Apple News] Paid for / Support on this pluginI believe this error appears when you have an in the HTML of the post. There are other support requests that say this is fixed, though my testing is in line with yours: it’s still broken at some level.
Hopefully a fix is forthcoming.
Thanks for this clarification. Just to be clear, if we’re already running self-hosted Matomo and running the WP-Matomo (WP-Piwik) plugin, there’s no benefit in moving to the Matomo Analytics plugin, correct?
Forum: Plugins
In reply to: [Publish To Apple News] [& nbsp ;] still breaking api on submitWe’re definitely still seeing this here, as well. Would love a fix, and are happy to provide any details we need.