o6asan
Forum Replies Created
-
Hi @marqas,
I apologize for my delay and express my thanks for your hard work.
The plugin newer versions work very well without customizing.Hi Varun (@contact-banker).
It should have deleted it automatically, until you have chosen an option of not deleting it from the Mail Bank Settings.
Really? But I had the experience I wrote.
Anyway, I found “mail-bank-version-number” on each child site and the parent site didn’t have “mail-bank-version-number”. After deleting the option and re-installing the plugin it works very well.
Thank you so much for your nice plugin and help.
@jeherve Thank you so much.
I read https://github.com/Automattic/jetpack/pull/7710 .
But I cannot understand it very well at my PHP knowledge level. Anyway the plugin works well about this issue.I appreciate your hard work again and close this topic.
@jeherve I haven’t had the error since I updated to Version 5.3 at 0:40 on Sep.7 UTC. So I agree with you. I appreciate your hard work.
By the way, what did cause this issue exactly? I would like to hear it for my knowledge.
Thank you for your quick reply, @marqas.
Not all posts have insert or delete tags. So I may say I am facing it on just some post. But the issue always appears as a post has those tags.
Use Custom AMP Editor for those posts, just copy the HTML from the content editor and paste it in Custom AMP Editor and removed that tag.
Thanks, it worked. However, it’s a little troublesome for me. So, I expect you and yor engineers will resolve this.
Thanks, @marqas.
I can create a ticket, but I don’t need date tags actually.
Why does the plugin do
<ins datetime="2017-05-01T16:36:29+00:00"> </ins>
into<instime>
instead of changing<ins datetime="2017-05-01T16:36:29+00:00"> </ins>
into<ins> </ins>
?If the plugin generated
<ins> </ins>
, Google Search Console wouldn’t complain about it.I add supplementary explanation.
WordPress’s insert tag is<ins datetime="2017-05-01T16:36:29+00:00"> </ins>
.The plugin changes this into
<instime>
.So, Google Search Console gives an error about them: “Prohibited or invalid use of HTML Tag (Critical)”
Hi @marqas.
I changed
<video src="/wp-content/uploads/2016_03_30_1445.mp4" controls="" class="alignleft"></video>
into<video src="/wp-content/uploads/2016_03_30_1445.mp4" controls=""></video>
, and the video appeared on the AMP page.Thank you!!!
Thanks, @frenchomatic.
But your suggestion made nothing change.
Thanks, @marqas.
$sanitizer = new AMPFORWP_Content( $comment_content, array(), apply_filters( 'ampforwp_content_sanitizers', array( 'AMP_Img_Sanitizer' => array(), 'AMP_Video_Sanitizer' => array() ) ) );
and
<video src="/wp-content/uploads/2016_03_30_1445.mp4" controls="" class="alignleft"></video>
give
<amp-video src="/wp-content/uploads/2016_03_30_1445.mp4" controls="" class="alignleft" height="400" layout="fixed-height"></amp-video>
and the error has gone.But, I cannot see the video on the AMP page.
I have again, too.
> I’ll let you know when I have good news!
I’ll expect that, too.
@eatonz
Today, I updated PHP to 7.1.4 which includes the fixes of https://bugs.php.net/bug.php?id=74213. I already have Jetpack4.8.2 which merged #6565. Under them, I don’t have the error anymore.@jeherve
Thanks for the hard work of Jetpack team.> Do you use OPCache on your server?
Yes, I do.
;zend_extension=php_opcache.dll
opcache.enable=0
opcache.enable_cli=0
If I did the above, the error has gone.
But, I do agree with Eaton about OPCache.
No.
Now I use PHP7.0.16.
They say Jetpack 4.6 has PHP 7.1 compatibility, but I don’t think it’s 100%.Though one of WordPress.com engineers added my ticket(=3056104-t) to https://github.com/Automattic/jetpack/issues/4346#issuecomment-281750590, there is no new information for the moment.
The engineer of WordPress.com suggested me a test. But I couldn’t accept it because of my server environment. If you can, we might be able to find something.
- This reply was modified 7 years, 9 months ago by o6asan.