Advanced custom fields plugin has it’s own set of functions to use, use them instead. Also text fields there have an option of weather to save HTML or pure text http://www.advancedcustomfields.com/docs/ They also have nice examples if you go to the documentation of the particular field type
There are a number of ways you can break this up. I think you have the right idea though to break it inside of your current loop with $i, but maybe something simple that is readable could be changing this: if ($i == 19 OR $i == 31 OR $i == 43) { ?> Into … Read more
Rather than re-post the posts, we can create a custom query for the current day’s post regardless of year. We use current_time to get the current day and month according to the site’s timezone settings, then we create a new query containing date parameters for month and day. We don’t specify a year, so it’ll … Read more
In Admin Panel go to Settings -> Permalinks -> at the lower left click on save changes to refresh all permalinks including your custom post type.
This can be achieved with a simple custom plugin with 2 actions and 2 filters. First use the post_row_actions filter to alter the edit link on the admin page to attach a custom query called final_destination with the URI of the page we are currently on. Next we can use the edit_form_advanced action to add … Read more
IMO this ia a good approach. However one thing I would focus is instead of embedding the data into the post body, you may insert custom fields in that post. This may help you sorting posts based on color, make etc or what ever your fields are.
Just replace ‘order’ => ‘DESC’ with ‘order’ => ‘ASC’.
You can use the pre_get_posts action to affect any queries, both in frontend and admin. In your case you should make sure you affect only admin queries and you can even use get_current_screen to narrow it down further. Here’s an example that would modify the query only on the regular posts page: add_action (‘pre_get_posts’, ‘wpse311946_restrict_cats’); … Read more
wp_delete_post() always triggers before_delete_post – the problem must be that you’re hooking your function conditionally (i.e. not all the time). before_delete_post only gets triggered if you’re actually deleting the post permanently, not just trashing it. If you need to listen for trashing too, use wp_trash_post.
Make a copy of press.php and rename it to home.php. The page you selected “Press” to be the designated page for your posts in the dashboard under, Settings > Reading > Posts Page: [Press] …now falls under the control of the template hierarchy as listed by Milo. First WordPress will look for the existence of … Read more