In your theme you need to add_theme_support(‘post-thumbnails’); and then set up some add_image_size(); By doing this in your themes functions file you’ll get have support for the built in Feature images and any image sizes you set up images will be generated in the correct size. For more information on setting up images sizes the … Read more
It depands on property use_trailing_slashes of WP_Rewrite object, which is set based on your permalinks_structure. Please open Settings -> Permalinks. If your Custom Structure ends with / all urls will be forsed to use slash, if no – no.
Mostly it is the same, but sometimes its not. The edge case is when a core upgrade is being done. At that point the version in memory is going to be of the “old” version while the file version might be (depending where you are in the upgrade process) the new one. This is a … Read more
But I wonder, when is this file being executed? It seems to not be used anymore. The old Codex info here: https://codex.wordpress.org/Post_to_your_blog_using_email mentions this being deprecated and recommends using plugins instead. It seems to be the user’s own responsibility to run wp-mail.php to fetch posts from the mailbox, either via hook, calling the file manually … Read more
Unlike many other frameworks there isn’t much “pipeline” in WordPress. You can see the fancy illustration for the load process, but basically: URL is resolved into query variables Query runs to fetch posts and determine context Template file is determined from the context Template file is included and has complete control over output from there … Read more
Some do, a number of core functions is specifically designated pluggable and contained in pluggable.php for exactly this purpose. It is also quite a messy approach and is often regretted it’s a thing at all. The problems are loosely: the replacement works exactly once; letting extensions mess with core definitions can lead to very volatile … Read more
How to find out where the data.model is?
Isn’t requiring a file before it’s loaded by WordPress itself a symptom of bad code? [closed]
You need to add a call of wp_footer(); function. Do it before closing body tag in your footer.php file. It should look like this: <?php wp_footer(); ?> </body> </html>
I found the answer myself. I wasn’t creating the patch correctly. You have to use the “Create patch…” option in TortoiseSVN on the root folder, not the patched file itself.