svaults

Thanks for the reply @mikes41720.

In the other thread with this topic, someone mentioned they reached out to SEMRush who said this is a legitimate error and that the other tools just haven’t been updated in a while. That is to say: Google does expect the name field and that there would be a penalty.

Why are breadcrumbs even forced by the Yoast plugin?

We’re considering just migrating to a different SEO plugin without this issue but that is a pain in itself. Can the devs not provide an option to add the name field to the breadcrumbs or remove them completely?

Thank you. Looking at the output for that file, I can see why it would be flagged. Is there a reason why this file is publicly accessible? Is it even necessary?

I can ask the server admins to whitelist this file or prevent reading with .htaccess but I think the solution is to remove those files or to make them inaccessible with the plugin itself.

Please let me know what you think?

You could also help by offering a refund for this year to Pro owners as a way of taking responsibility for the consequences your buggy updates have caused to thousands of developers and site owners.

• This reply was modified 4 years, 6 months ago by svaults.

Layout/css bugs still ongoing.. You can help with replacing your QA team.

The issue is not just the breaking changes of a new version.

It’s the bugs introduced with the new version. It’s bugs that you don’t discover until days later when you’ve already added more content and a simple “rollback” won’t work.

It’s unacceptable for a plugin like this.

The issue is not just the breaking changes of a new version.

It’s the bugs introduced with the new version. It’s bugs that you don’t discover until days later when you’ve already added more content and a simple “rollback” won’t work.

It’s unacceptable for a plugin like this.

Yep. Confirmed bugs with the latest releases. Broke a ton of sites, still broken days later. I hope they make a major change over there.

This was the best page builder plugin to come to WordPress and they went and ruined it along with the reputation of a ton of good developers all over the world.

Yep. Confirmed bugs with the latest releases. Broke a ton of sites, still broken days later. I hope they make a major change over there.

This was the best page builder plugin to come to WordPress and they went and ruined it along with the reputation of a ton of good developers all over the world.

Yep. Confirmed bugs with the latest releases. Broke a ton of sites, still broken days later. I hope they make a major change over there.

This was the best page builder plugin to come to WordPress and they went and ruined it along with the reputation of a ton of good developers all over the world.

Yep. Confirmed bugs with the latest releases. Broke a ton of sites, still broken days later. I hope they make a major change over there.

This was the best page builder plugin to come to WordPress and they went and ruined it along with the reputation of a ton of good developers all over the world.

Yep. Confirmed bugs with the latest releases. Broke a ton of sites, still broken days later. I hope they make a major change over there.

This was the best page builder plugin to come to WordPress and they went and ruined it along with the reputation of a ton of good developers all over the world.

Confirmed bugs with the latest releases.

Yeah this is truly incredible – how can you take a great plugin and end up trashing it by breaking so many revenue-generating, mission-critical websites.

And then no solution for several days.. still none. I can’t trust Elementor anymore.

This bug has also been reported in Github. After two days, still no fix.

By the way, the original bug has existed since at least April 25, 2019. It was reported then by my client but I didn’t have a maintenance contract to look into it until recently.

Thanks