Minneyar

Sorry I was away for the weekend.

Browsers tested: Firefox and Chrome.
Both browsers do not produce any sort of console log related to this plugin (which is odd). The only thing of notice is a deprecation message of tinymce api which I assume is not caused by your plugin or is not fixed by 1.5.x, eigher way does not change the fact that 1.4.13 or previous still works perfectly and 1.5.x does not.
There is no error logged from php eigher according to my admin.
PHP7 is used
I can confirm the plugin does work v1.5.x with a fresh installation of wordpress, so I am assuming it has to collide with another plugin. My best guess is still AdvancedCustomFields, which we use for content creation (instead of the default content field). This leads to multiple TinyMCE instances on one page.

As of today, AMP by Automattic indeed had an update, which fixed our issues as far as we can tell. (checked 10 random error pages from over 200 which now validate correctly)
I suggest updating the plugin and reevaluate. It also seemed to fix another error we had with a different plugin. Eigher they really did improve quite a bit or the previous version was simply faulty.

new version is 0.5.1

• This reply was modified 7 years, 3 months ago by Minneyar.

Can relate to that, we see amp-img errors as well.

“Implicit layout “CONTAINER” is not supported by amp-img”

on
<amp-img src="//store-images.microsoft.com/image/apps.61842.13510798885702164.e9576b67-b999-4fc6-92c7-ba871310ece5.07c0b0c0-6a7c-47c6-a7b8-ca0b8fb0d379?w=180&h=180&q=60" alt="VectorWatch" class="amp-wp-inline-596b2fead25f53bfb962508b58f9b49f"></amp-img>

we use version 4.0.15 of the plugin, which is the latest version to date.

I would appreciate, if this great plugin would gain AMP support!
At the moment, we have a high prio filter on the_content, which reg replaces the short code whith “” on amp pages.

i second this feature request. for tracking or statistics it is necessary, to change the link of a particular appbox (not in general, i know that’s in the settings). would be great to simply add the link as a parameter in shortcode.

@alukin: could you provide your code snippet in the meantime? that would be much appreciated!

• This reply was modified 7 years, 3 months ago by Minneyar.
• This reply was modified 7 years, 3 months ago by Minneyar.

might have been related, though not sure if it was the token or the app id. I was also active on github in another thread and found my own way out of this by deleting data from the database after running into a deadlock for 2 weeks on our production system.
I would revise my initial rating to 3 stars as I find it a bit harsh in retrospect, though I’m not sure how to do so.

glad to hear all went well. we got a reply on github, seems there is someone working in this issue.

I deleted 3, thought “instant-articles-option-fb-app” did it I suppose.
Search for “instant-” in phpmyadmin or similar, there are about 6 or so entries.
I would not touch “instant-articles-wizard-url”, but any of the following should only “reset” the settings:
instant-articles-option-fb-page
instant-articles-option-styles
instant-articles-option-ads
instant-articles-option-analytics
instant-articles-option-publishing
instant-articles-option-fb-app
and instant-articles-current-state

when you delete those settings, just clear the option value (blank)
(ps: of course every thing you do is at your own risk, make a backup!)

• This reply was modified 8 years, 2 months ago by Minneyar.
• This reply was modified 8 years, 2 months ago by Minneyar.

seems to be a bug when your settings are not correct that the settings page dies.
cleared the options from wp_options table and voilà. not funny though.
https://github.com/Automattic/facebook-instant-articles-wp/issues/471

• This reply was modified 8 years, 2 months ago by Minneyar.

we encounter the same problem, any suggestions how to get around this?

Hi nosilver4u,
thanks for the fast response!
Not quite what I was hoping for, but I guess it is doable.
As the site in question has multiple authors and external writers, the proposed way with keywords is a bit hard to enforce. Still, it is a solution so thank you for pointing that out!
I would still love an opt-out feature though.

kind regards

here is a link where you can look at the given bug: LINK

The Metadescription had to be set manually on every post, the SEO analysis said we got 0 words and was always orange at best and the score could not be recalculated because the tools window is a white page.

we fixed all this anyway by simply reverting to 2.3.5.
I guess we will wait for another month before giving it a new shot.

Yes I belive you are totally correct, doing nothing would have been fatal.
But as (paying) user of more than one plugin (for features and development support) those big leaps you mentioned were more than once per plugin, lasted way longer than expected and forced me more than once to downgrade to an older version. That is something I was not forced to do before the switch to premium nor with any other plugin I know and used so far.

Specifically, I have not blamed commercialization but stated since then, there were a lot of problems with updates. So to clarify: The quality of the yoast plugin updates took a big hit. Paying for it makes no difference other than leaving a bitter taste to it.

can confirm that. cannot update my seo score for example because this page is empty. getting no error so far, had no time for now to check the php logs.