|
ICLE
|
August 20, 2018 at 10:35 am
https://iclega-attend.org/clean-up-custom-field-dropdown/
How do I clean up the garbage in the “custom drop down list”. Looks like lots of stuff got into it from trying out new plugins…
|
|
Josh
|
August 20, 2018 at 10:43 am
Hi,
You’ll find a well-written guide on that subject here:
https://wpsites.net/wordpress-admin/2-ways-to-delete-custom-fields-from-post-meta-tables/
|
|
ICLE
|
August 20, 2018 at 12:03 pm
Thanks!
|
|
ICLE
|
August 20, 2018 at 12:28 pm
The plug in appears to remove data but the dropdown remains with the same custom values in it.
https://iclega-attend.org/dropdown-still-has-custom-values-it-it/
|
|
Josh
|
August 20, 2018 at 1:25 pm
Hi,
This is a bit outside of the scope of Event Espresso plugin support, but here goes:
The WordPress custom field meta box pulls the dropdown select options from your site’s _postmeta table. So if you go into phpmyadmin and look in the _postmeta table, then look at values for the meta_key column, you’ll find them there.
|
|
ICLE
|
August 21, 2018 at 6:51 am
At first I did not see a _postmeta table.
There was a “page 2” in the phpMyAdmin table list and I found it there.
That was a UX fail on phpMyAdmin’s part.
Thanks.
|
|
ICLE
|
August 21, 2018 at 9:40 am
Hi, I just about have this under control but I think there is a small conflict with another EE plugin. There is a dropdown item in the custom fields called “ee_wpuser_integration_settings”. I am using this plugin. Should I be concerned about clearing those values out of the database to clean up the dropdown menu?
Here is a link with a screenscrape…
https://iclega-attend.org/custom-field-dropdown-cleanup-task/
Thanks again, I appreciate you going above and beyond what is considered support. I am not totally aware of the weirdness that plugins seem to bring to dropdown values and the like because I am not as familiar with WordPress as I would like.
|
|
Josh
|
August 21, 2018 at 9:45 am
If you’re using the WP User integration add-on I would advise to not delete that meta key. It’s actually used to store options on a per-event-basis.
|
|
ICLE
|
August 21, 2018 at 10:46 am
Oh that is very ugly. Data architecture matters.
I will not touch it. How do I find out where other randomly appearing values come from which find their way into that custom field dropdown?
|
|
Josh
|
August 21, 2018 at 10:52 am
It will help to understand they are not randomly appearing. Something added them with values to the _postmeta table to store data. You can view the _postmeta table in the database and check the meta_value for the row first. The value might shed some light about what was saved. Then you can also check the post_id for the row, then go to edit the post in the WP admin to get some context about the post and why there’s post meta values saved for that post.
|
