Support

Account

Register Login

Forum Replies Created

  • This topic now veering off to the south a bit. It probably should be closed. The initial issue; namely, that Yoast SEO completely borked after their update when ACF (and many other plugins) were used, seems to have now been fixed with Yoast’s latest update.

    Also, thanks for the reference to “content analysis.” that plugin seems to have been developed even before the Yoast foul up in order to get Yoast (when it worked) to recognize key words which were used and “injected” (thus not in the “main stream” content for Yoast to count) by the ACF plugin.

    It’s only purpose is to “enhance” Yoast not be alternative to it so doesn’t fit what I asked in the original thread post. Now that Yoast is back working again (seemingly) it’s good to know that there is something that makes them useful together.

  • I should say here in this thread too, that the latest Yoast SEO update, pushed out several months after the crash I wrote about, has – as far as I can tell – finally solved the incompatibility.

    I can find no explanation of the problem from the company – or even acknowledgement that they even were aware of any incompatibility.

  • Yes, thanks. Most all should know that Yoast SEO critique is fluff and not in any way binding on google or the like.

    However, Yoast SEO does in fact make all kinds of non-fluff additions to the <head of every page and for some does take over the entire sitemap which IS very important to Google.

    Additionally, it apparently has the ability to screw up other innocent by-standing plug-ins as well.

    The convenience is perhaps what irk’s people most, but not the most important.

  • Thanks John – I will. Despite what appears to be a complete lack of willingness of the Yoast team to solve problems THAT THEY CREATE, I’d still like to avoid the hassle of figuring out all that header info and typing it myself. Although, from now on we all need to keep an eye on what YOAST actually does to the sitemap that Google crawls.

  • Addition – However I must say, I’ve never had a peep out of the ACF people either, despite having made an inquiry. So, it appears that nobody gives a crap about this incompatibility issue.

  • Actually… since I opened this thread I’ve completely removed the defective Yoast SEO plugin – then I went through wordpress to obtain the old version 2.x of the plug in and install it which went back to working as it did.

    However, subsequent to that, I’ve heard people tell me that the 2.x version of Yoast was updated because it was defective and had vulnerabilities – good grief. I’ve still got it installed and actually updated to Yoast 3.7 when it came out several weeks ago now. Nothing had changed! IT WAS STILL DEFECTIVE AND BORKED ALL OVER THE PLACE if I had ACF turned on. If I turned ACF off Yoast worked; BUT, as I said before, pretty much YOAST is fluff and I can program the stuff in the head of the templates. ACF is not because I’ve got hundreds of posts which rely on the custom fields. ACF wins!

    IN ADDITION: After a few weeks of troubleshooting Yoast, I began to notice that my Google referrals started dropping off dramatically and I found that the Yoast SEO 3.7 was screwing up the sitemap sent to Google. So, I’ve also had to turn off the Yoast breadcrumb function and install another program to handle creating the sitemap – which has fixed the Google recognition problem.

    A drawback of continuing to use the old version of Yoast is that it continually nags me to update and shows that there is one outdated plugin. Yoast apparently doesn’t give a crap about the free plugin anymore, and I’m guessing his ego doesn’t let him even consider that it might be his problem and not ACF, so he hasn’t had any bug fixes rolled out for over two weeks now!

    Until there is a version 3.8 out I won’t bother with him, and even then ACF will still win if he doesn’t fix his defective programming.

  • Perhaps I might have titled: Yoast SEO update incompatible with ACF. Frankly, I don’t know what has borked – clearly Yoast’s new programming has highlighted the issue.

    Also, it is NOT only the ACF fields that Yoast doesn’t have a clue of – it’s the entire post (years worth). Were working, now not. And not over the entire usership – only those who have ACF installed.

    I’m sure that Google does its own thing – however, if you read all the flack going on in their forums – people now state that Google doesn’t recognize their home page (perhaps an entirely different issue but who can tell).

    So, I think it behooves us all to try and assist in resolving issues. Not being a developer, about the only thing I can do is to report my findings, which is what I am trying to do. None of the other plugins that I’m using seem to be causing the issue – only ACF. It may not (probably isn’t) anything ACF is doing – unless they are using some function name localized (accidentally?) to the same thing the Yoast people are now using?? Or aren’t resetting some kind of index pointer???

    I would have hoped by now that Yoast’ites would have made direct contact with ACF to discuss the issue – it doesn’t look like they have. In fact it’s going on 4 weeks now since there’s been an update and they’re still getting stung hard by large amounts of “1” ratings. Both of these plugins are used by an incredible number of the community – it’s disheartening to have this happen to two such icons.

Viewing 7 posts - 1 through 7 (of 7 total)