Use useSettings() since useSetting() is deprecated. Then, you can specify a further path with custom or theme to state what data you’d like to get: // User-created presets. useSettings(‘typography.fontSizes.custom’); // Theme-defined presets. useSettings(‘typography.fontSizes.theme’); See this WordPress Playground for a working example.
It appears to be an attempt to use a known vulnerability in the tagDiv Composer plugin (used in a couple of tagDiv themes. Read the linked article for more details. Note: If you think your WordPress site has been hacked, start here: https://wordpress.org/documentation/article/faq-my-site-was-hacked/ If you’re using the tagDiv plugin or theme, make sure it’s all … Read more
It looks like your header.php is using wp_title(”), which is deprecated and may not return anything in some cases. Also, the way it’s structured, it’s not properly appending the site title. Try replacing your <title> tag with the following code: <title><?php bloginfo(‘name’); ?><?php wp_title(‘|’, true, ‘left’); ?></title> Or, if you’re using a newer version of … Read more
When using wp_register_script(), the script is only registered but not enqueued, meaning it should not be loaded on the frontend unless explicitly enqueued with wp_enqueue_script(). public function frontend_scripts(): void { wp_register_script( ‘swiper-slider-script’, plugin_dir_url(__FILE__) . ‘assets/lib/js/swiper/swiper-bundle.min.js’, [], ‘1.0.0’, true ); // Enqueue script only when necessary if (is_page(‘your-page-slug’)) { wp_enqueue_script(‘swiper-slider-script’); } } add_action(‘elementor/frontend/after_register_scripts’, [$this, ‘frontend_scripts’]);
The official documentation for wp_untrash_post documents a filter for setting the status that it will use: https://developer.wordpress.org/reference/functions/wp_untrash_post/ This filter can be used to return pending instead as the status. If that’s not an option though, you could set the post status to pending after calling wp_untrash_post, it doesn’t have to happen in a single function … Read more
Just use $user->set_role( ‘learner_member’ ); instead of both lines where you are removing and adding the role. Link to the docs.
Better try something like this: add_action( ‘register_new_user’, ‘send_admin_registration_email’, 99, 1 ); function send_admin_registration_email( $user_id ) { $user_info = get_userdata( $user_id ); $first_name = $user_info->first_name; $last_name = $user_info->last_name; $user_login = $user_info->user_login; $subject=”Family Medicine Residency Site Registration”; $message=”<p><b>Name:</b> ” . esc_html( $first_name ) . ‘ ‘ . esc_html( $last_name ) . ‘</p>’; $message .= ‘<p><b>Username:</b> ‘ . … Read more
You can run 2 wp_query, get the ids and pass those as the post__in parameter to a 3rd wp_query. Not efficient but will do the job. Or you can use a subquery and do it all with just one wp_query. Something like the following: add_filter( ‘posts_where’, ‘myprefix_posts_where’, 10, 2 ); new WP_Query([ ‘post_status’ => ‘publish’, … Read more
Enable debug in wp-config.php and read the debug_log: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ The problem is probably an incompatible plugin or a theme incompatible with the newest version of WordPress.
Your code looks fine at first glance, but the Plugin Checker is complaining about the dynamic argument in register_setting(). This usually happens when register_setting() receives an argument that is not a direct function reference or a string literal. function inseco_sanitize_textarea($input) { return wp_kses_post($input); } register_setting( ‘inseco_settings_group’, ‘inseco_code_after_page’, array( ‘type’ => ‘string’, ‘sanitize_callback’ => ‘inseco_sanitize_textarea’, // … Read more