Sharon

FYI rolling back to PHP version 7.4 solved the fatal error. When I did that, an update to Yoast made the individual property pages disappear (404). So I had to roll Yoast back to version 22.0

Hi Scott – I didn’t notice before but this issue was already added to this forum (Failure going from PHP 7.4 to PHP 8.1). To fix, you have to edit 5 PHP files and replace another entirely. I will instead try to set the PHP version back to 7.4 for the site and see if that works.

Here is solution to this problem:

Disable Proxy Pictures (set to Yes) in Settings. Wait some time after changing setting.

For those who are affected, I heard back from a FlowFlow author today via email:

Hello, since management “genius” Musk came into power and killed free READ-ONLY access to Twitter API, to get a Twitter wall on your website, you must pay Twitter $100 monthly https://developer.twitter.com/en/products/twitter-api

Most of our target audience is small business WordPress website owners, and 98% of them won’t pay $100 per month just to embed a Twitter wall. So we’re considering dropping its support entirely. Other feed types are operable for sure.

We understand your frustration, that’s a shameful case, but it is what it is.

Hi – The same problem has reappeared this morning with Twitter feed:

App received next error message for this feed:

You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product

This seems to have been fixed – thank you!

This problem is discussed here on the Twitter Developers Forum which may be of help:

https://twittercommunity.com/t/453-you-currently-have-access-to-twitter-api-v2-endpoints-and-limited-v1-1-endpoints-only/193292

Hi – Is there any update on this issue with the Twitter feed? I saw there was an update for the plugin and I upgraded, but I still see the same error message.

Thank you for your response and for the link to the docs. I look forward to the upcoming release re: removing title attribute from buttons. So the ‘Very low contrast error’ code that WAVE flags as an error is here:

Accessibility by WAH

It looks like it is white on white background which I don’t totally understand but I think WAVE thinks this is white on white. It doesn’t flag any of the other text.

Thank you – that worked. I also changed the color of the “required” star from red to black as WAVE issued a warning about that as well.

Hello – Thanks for your reply. I’m not sure the code author knows about this bug so I just emailed him at [email protected]. Someone else noticed this about 2 years ago so commented out the code but I can’t do that as I want the functionality. =>
https://www.ads-software.com/support/topic/empty-buttons-causing-accessibility-errors/

Thank you for the update

This is happening on all the websites I host that are using your plugin, all different themes:

https://janmounsey-advocacy.com/
https://longspoolcenter.com/
https://pva-inc.com/contact/
https://sped-advocate.com/
https://yogafordailyliving.net/
https://chickadeewebdesign.com/clients/

OK, sorry, where do I put that code? Or setting?

Hopefully the developers are working on making it compatible with WordPress 5.5.