settings api sub menu and data not populating

I don’t know anything about the WeDevs thing, but I do kinda know the Settings API itself. That being said I have a shot in the dark answer. In your wedevs_plugin_page() function, do the methods on the $settings_api object need a parameter for which settings section to display? Like $settings_api->show_navigation(‘wedevs_basic’);? Or maybe the object instantiation … Read more

Theme Customize API Panel Concept

Fields always go in sections. Sections go in panels. $wp_customize->add_panel( ‘newsletter_panel’, array( ‘title’ => __( ‘Newsletter’, ‘twentytwelve’ ), ‘priority’ => 41, ) ); $wp_customize->add_section( ‘newsletter’, array( ‘title’ => __( ‘Newsletter’, ‘twentytwelve’ ), ‘priority’ => 41, ‘panel’ => ‘newsletter_panel’ ) ); That will put a “Newsletter” section inside a “Newsletter” panel. All the fields should still … Read more

not getting API setting saved confirmation message after update on option page

You need the settings_errors(); function somewhere on your settings page: function display_acme_options_page() { settings_errors(); echo ‘<h2>Acme Options</h2>’; echo ‘<form method=”post” action=”options.php”>’; do_settings_sections( ‘acme-options-page’ ); settings_fields( ‘acme-settings’ ); submit_button(); echo ‘</form>’; }

update_option_$option action not working as expected

Looks like update_option_{$option} will only fire on updated options, ie, not brand-new ones. Reading the code for update_option(), I see this: /** This filter is documented in wp-includes/option.php */ if ( apply_filters( “default_option_{$option}”, false, $option, false ) === $old_value ) { // Default setting for new options is ‘yes’. if ( null === $autoload ) … Read more

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)