I’ve created a new Options Page using the ACF menu and linked a new field group to it. The field group contains a repeater field with text fields inside. We have two identical environments.

On the development environment, after setting everything up and populating the fields with data, the GraphQL IDE successfully retrieves and displays the correct data. However, after exporting the WordPress settings from the development environment to staging, the following issue occurs:

In the GraphQL IDE on the staging environment, all fields are visible in the Query Composer, but no data is returned.

To troubleshoot, I created a test example directly on the staging environment by linking a new field group to the Options Page. Unfortunately, GraphQL still does not return any data.

In options page editor data are visible and it seems that GraphQL correctly recognizes the fields and the Options Page itself but does not retrieve the populated data.

Could you please assist me in resolving this issue?

This worked very well for me everywhere on the website.
I added a simple button with text on my website, the text comes from my options page.
i can see it on both Languages (fully translated) on all pages except pages that contain this button in a listing (Jet-Engine).
The button return no text only on Hebrew Pages (my sub language) as if it is NULL.
The text Do show up on the same page in the English language.

I am unsure what to do.

But I’m trying to show an image field from ACF options page unsuccessfully. Have tried so many combinations of parameters, but image won’t show.

Most of the plugin I have used to create option pages haven’t been updated since a lot of time… It was great to find this tool, which works well with WP 5.7.

Adding option page (s), optionally with tabs, has never been easier and the plugin is very well finished and sufficient for most needs.
The option to create multiple option pages and define the position of each one in the WordPress menu is very useful.

If you need to add some simple options for a theme that is not based on a full framework that include the ability to create option pages (ie. Metabox.io) : try this one !

Big big thanks to the dev !

But I was wondering… If I would like to really create a standalone WordPress plugin I would need the options page to be coded within a real .php file.

My question: Is there a way to export the PHP code so I can paste it in a .php file (and I don’t mean the current php export because that’s something else).

Or maybe there’s a way to see the created code so I can copy paste?

I love your plugin so much to make my own plugins witch but I would like to share the created standalone plugins with others without having them installing ACF and so on…

I want the option page in the admin menu to be shown under a custom post type as in the sub menu. I tried several things under “Edit option page” > “Position” and “Parent slug” but can’t get it working.

post_type=vacatures

I hope anybody could help me out.

Thanks

I’m able to do that with WP regular custom post type… – E.g.:

'menu_icon' => 'data:image/svg+xml;base64,' . base64_encode('<svg width="20" height="20" viewBox="0 0 2048 1792" xmlns="https://www.w3.org/2000/svg"><path fill="black" d="M256 1024h1728q26 0 45 19t19 45v448h-256v-256h-1536v256h-256v-1216q0-26 19-45t45-19h128q26 0 45 19t19 45v704zm576-320q0-106-75-181t-181-75-181 75-75 181 75 181 181 75 181-75 75-181zm1216 256v-64q0-159-112.5-271.5t-271.5-112.5h-704q-26 0-45 19t-19 45v384h1152z"/></svg>')

Is it ossible to have something similar with the icon_url param?

I’ve created an CMB2 option page with some text input fields, as i usually do. Everything works fine, but I’ve noticed that I can’t delete the input fields contents. Once a text string is written and saved, if then I delete it (leaving the input text field blank) and save again, the previous store data come up again, and the frontend do not change.

Again, surely I’m missing something

I was wondering whether you could improve the plugin by removing the options page (options-general.php?page=radio-buttons-for-taxonomies) and instead add a field to each taxonomy (edit-tags.php?taxonomy=foobar) to toggle the radio buttons.

This would help reduce the amount of options pages/menu items a medium sized WordPress project backend has.

Every plugin should remove it’s options when it gets uninstall so the setting Completely remove options on plugin removal would not be needed.

What do you think? Thanks!