Alex Cicovic
Alex Cicovic
Notes from #766: - https://github.com/Parsely/wp-parsely/pull/766#discussion_r848546763
All internal `Parsely->construct_parsely_metadata()` calls were removed in #833.
In my tests, just installing and activating the AMP plugin doesn't surface a fatal error for me.
Information from @thompsonjoshua that may come in handy: > Most recently, a customer said that the error went away when they disabled javascript tracking in wp-parsely.
Just to get back to this, I recently worked with the AMP plugin and noticed no issues. @thompsonjoshua, do you remember having any newer reports regarding this? I'm thinking of...
> > Migrations from another CMS seems like a rare case when compared to the regular case of someone just adding this plugin. > > This [migrations from other CMSes]...
@arhine, @thompsonjoshua, @LauraKalnicky, any feedback on this? Are things as they should, or is there something to improve here?
Hello, I can confirm that per our default settings code, `force_https_canonicals` is set to `false`: https://github.com/Parsely/wp-parsely/blob/b83be77db84dba709808a306bc67b77e6556f2b5/src/class-parsely.php#L112 And no, nothing stops us to set this to `true` for new installs, or...
Hello and thanks to everyone for the participation! Until we get further movement regarding this, I'll flag this issue as awaiting for feedback.
I agree that this looks like a good candidate for the PCH. We need an API implementation for this though, which is outside of the scope of the PCH. As...