Home › Forums › Add-ons › Options Page › WPML and ACF Options › Reply To: WPML and ACF Options
Or you can also create a regular page called “translations” where you might put all strings in as acf textfields. Then you’ll be able to translate it as usual pages and it’s a bit simpler than creating a whole cpt for a single page 🙂
I usually create three pages when dealing with WPML and ACF; Header, Footer and Global translations. These three act as replacement for having three options-pages with ACF. The upside is that they’re all collected in pages for easy access and you don’t need to create a cpt. The downside is that it’s not really semantically correct since they are not really being used as pages.
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!
Are you building WordPress sites with ACF and @BeaverBuilder, and wanted to use your ACF Blocks in both the block editor and Beaver Builder?— Advanced Custom Fields (@wp_acf) May 10, 2023
The BB team recently added support for using ACF Blocks in Beaver Builder. Check it out 👇https://t.co/UalEIa5aQi
© 2023 Advanced Custom Fields.