Massive amount of CPSEO settings appear in Post's Custom Metadata

[elosha]

I'm running CP 1.1.2 (German locale) and just updated CP SEO to 1.0.0-beta.3.

I've noticed huge amounts of CPSEO Custom Metadata appended to my Posts. See below for the disruptive impact this has.

These seem to be CPSEO internal settings. I understand that they should not appear if CPSEO is correctly working and showing its editor.

What you can't see is another effect: When I start a new post and want to add my Custom Meta field called "epaper" that I actually want and need, it has been kicked out of the dropdown containing usual Custom Meta entries.

Additionally, I would say that it makes no sense to save all of these settings with every post, at all. Especially since some seem are actually totally unrelated to the current installation (like Recipe rich snippets). You understand, I switched to CP and CPSEO to reduce bloat ;)

[timbocode]

Hi @elosha . Sorry again for the delay in responding.

It would appear that there are 2 or 3 issues here.

1. Classic SEO is creating unnecessary post meta data. This is true. Unfortunately, this is a carry-over from Rank Math 1.0.33 on which Classic SEO is based. It is something I'm aware of and will be dealt with under issue 41 Remove redundant code / clean codebase but this won't be until after version 1.0 has been released.

2. cpseo meta data is being displayed in WP custom fields which is disruptive. Also true. I've created PR #76 which prevents the cpseo data from displaying. This is a temporary workaround until #41 can be addressed.

3. Other required meta data does not display in the Custom Fields dropdown list. Again, this is true. However, this should be resolved by #76 . It is also worth noting that the number of fields displayed in the dropdown is limited to 30 by ClassicPress / WordPress itself. This can be increased by using the postmeta_form_limit filter as described here https://developer.wordpress.org/reference/hooks/postmeta_form_limit/.

Hopefully this addresses all of the concerns you raise in this issue.