Instead of using a hook to store the defaults, you can write the logic straight into get_theme_options – if the value is false, there are no options saved yet: public static function get_theme_options() { $options = get_option( ‘theme_options’ ); if ( $options === false ) { $options = [ ‘key’ => ‘default_value’, ]; add_option( ‘theme_options’, … Read more
You need a way of managing your settings. You can use whatever methods of management as you see fit. However, I’ve came up with a fairly “simple” Settings PHP Class, which you can use to retrieve your Plugin’s Settings as an Object with Properties. The Object is your Plugin’s Settings. The Properties of the Object … Read more
Probably the problem is caused by 4. WordPress stores some data as serialized arrays. When you change the domains this data gets corrupted – read http://php.net/manual/en/function.serialize.php (Anatomy of a serialize()’ed value part will explain you everything). How to resolve it? Use https://wordpress.org/plugins/wp-migrate-db/ It will convert data correctly.
While WP is a little weak about working with forms in general, there are some loose conventions that can help keep things organized. For POST forms there is a dedicated wp-admin/admin-post.php endpoint, which meant for just that and works similarly to better known admin-ajax.php. Unless you have good reasons to organize it otherwise I would … Read more
The problem is your value=”” attribute, for example <textarea value=”<iframe>”> is invalid HTML, and the browser will do its best to try and fix the markup. That’s why you’re getting strange results So instead, remove the value attribute. You’ll also want to escape with esc_textarea to prevent malicious code breaking out of the text area
Better to avoid such a thing. The settings API has two “faces”, one the UI, and the other is handling the form submission. The form submission is handled on a different URL than the UI (/wp-admin/options.php) and therefor your “user action” depended code will not run and the handling of storing the setting in the … Read more
Plugin can read options on init event or just in code (during loading). All plugins are loaded before theme load. So, using init action can be too late. Filter pre_option_fve_disable_css doesn’t change value of the option. Instead, you have to use option_fve_disable_css filter. But again, it can be also too late. You should check the … Read more
You’re not actually querying the database twice, if that’s what you’re worried about. Regardless, as you’ll see from the documentation, get_option() has a second argument you can use to define a default value for if the option hasn’t been set: $option = get_option( ‘option_name’, [] );
OK, so you put your form in manu page callback and the code that is processing that form is also in that same function. And you register your manu pages on admin_menu hook. All of that means that when you process your form and change the value of your option, the menu is already registered. … Read more
That clearly is a plugin field of “Advanced Custom Fields”. The function: the_field(); is one of the utility functions of the plugin. The purpose of “Advanced Custom Fields” is to enable users with less coding-knowledge to add custom fields to a theme/template. So, in order to reverse engineer the whole thing, you propably need to … Read more