Home › Forums › Backend Issues (wp-admin) › Clean WP menu & remove old ACF slugs?
Hi,
I have taken over a web site which extensively used Advanced Custom Fields Pro along with a bespoke theme. I am now using a new theme which doesn’t require ACF. I have a very basic understanding of ACF.
There’s two issue which are causing problem which hopefully someone can advise me on. 🙂
1. The WordPress Admin menu has about a dozen links (and sub-links) to custom fields which (I guess) were created in ACF. None of these apply any longer and I can seem to be able to remove them – how can I remove these from the WP menu?
2. The previous developer created about 100 custom fields which use the same slug as those required by the new theme (“portfolio”, “case-studies”, “events”, etc) which is causing conflicts in multiple sections of the site. How do I remove the old ACF slugs, so that the new theme slugs work? I would prefer not to change the theme slugs, as the ACFs slug were good for SEO and I would also have to set-up 1000s of 301 redirects.
Can anyone give me advice?
Thanks.
Sally
Unfortunately I’m not going to be of much help. If you’ve changed themes and you are still seeing ACF fields (do you mean options pages), then whatever is being done could be done in a plugin.
You will also need to trash/delete the field groups that have been created. These are stored in the DB and will be there even after changing themes.
I can’t give much more advice on what would need to be done, it’s going to be specific to whatever the other dev did in the first place.
Thanks, John.
“If you’ve changed themes and you are still seeing ACF fields (do you mean options pages), then whatever is being done could be done in a plugin.”
No, these are ACF taxonomy links (and “empty” custom post types fly-outs) in the main WP Admin menu (down the left column of WP Admin) which have nothing to do with the new site theme or plugins. I can see from the “live” site (using ACF) what these all relate to, but there aren’t needed in the new theme site.
I understand from reading the forum that it can be very problematic removing un used ACF fields. I’d be very wary about removing anything directing in the DB. :-0 🙂
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.