You’ve got unbalanced and improperly placed closing parenthesis. There shouldn’t be the closing parenthesis after the ‘stylesheet’. Because the closing parenthesis is there, the PHP processor thought that was the end of the function’s parameters. Which caused the comma character after that to cause the error. Watch the balancing of your parenthesis (and quotes) as … Read more
Basically, you’re not properly using array_push(). array_push() modifies the original/input array which is passed by reference to the function and it returns the new number of elements in the array. So with add_post_meta( $groupItem->ID, $meta, array_push( $user_ids, 26 ) ), you’re actually setting the meta value to the number of items in $user_ids and not … Read more
Well, just change this: el( ColorPalette, { value: props.attributes.paletteData[0], onChange: updatePalette, } ) to this: el( ‘div’, {}, props.attributes.paletteData.map( function ( value, i ) { return el( ColorPalette, { ‘value’: value, onChange: updatePalette, key: ‘color-‘ + i, // required //… } ); } ) ) I.e. Pass an array of elements as the third parameter: … Read more
Please try using acf/save_post action that will hook in after ACF data has been saved. add_action(‘acf/save_post’, ‘check_values’); function check_values($post_id){ if(get_field(‘status’, $post_id ) == “closed”) { sendSMS(); } }
Whether you use do_action() or do_action_ref_array(), accessing the parameters from the hook callback is just the same for both the functions. But the primary difference between them lies in the way we provide the parameters to the functions: With do_action(), we simply pass each parameter individually: do_action( ‘some_hook’, 1, 2, 3, ‘etc’ ); // i.e. … Read more
Is the archive.php correct template for that? archive.php is the most common file to load any kind of archive posts. But anytime the user loads a category archive page, WordPress template system looks for files in this order: category-slug.php → category-id.php → category.php → archive.php → index.php If you want to create a specific template … Read more
It’s probable that your site was hacked. And that will take some manual (‘by-hand’) investigation. Lots of googles on how to clean a hacked site. But, in general change all site/hosting credentials to strong passwords: hosting, ftp, database, WP users look for WP admin level users that shouldn’t be there look at every file for … Read more
You can use register_activation_hook(). Add this to your plugin, tested and works. register_activation_hook(__FILE__, ‘redirect_after_activation’); function redirect_after_activation() { add_option(‘redirect_after_activation_option’, true); } add_action(‘admin_init’, ‘activation_redirect’); function activation_redirect() { if (get_option(‘redirect_after_activation_option’, false)) { delete_option(‘redirect_after_activation_option’); exit(wp_redirect(admin_url( ‘wp-admin/admin.php?page=axl_ads’ ))); } }
Because until relatively recently WordPress supported PHP 5.2+, but that constant was only added in PHP 5.4. Given that wp_json_encode is meant to encapsulate and account for the differing behaviour of json_encode across multiple PHP versions, it doesn’t make sense to deliberatly change its behaviour for PHP 5.4+ Now that WordPress has raised its minimum … Read more
Putting aside the legal issues, and focusing on a function for displaying the current year, the problem is actually pretty straightforward: The theme developer gave you the wrong code. get_the_date( ‘Y’ ) gets the year of the publication date of the current post. This is not what you asked for. date( ‘Y’ ) is a … Read more