The real need for the WP_Filesystem is to be able to set the correct file owner/group permissions when writing new files. Reading or overwriting existing files does not change these permissions so the WP_Filesystem is not technically needed for that (though you can use it for that too.) The reason is it is a potential … Read more
There is no need to use the WP filesystem API if you are trying to access directories to which the web server has full access. It is needed mainly only when you want to write to directories which have limited access like the plugin directory. From that point of view the two snippets are the … Read more
They don’t have a special name, they are just theme / template files. If you want to read more about them in general, see template files in the codex. The template hierarchy is also something you’ll need to know about, it explains what file gets chosen when.
Seems like you have several misconceptions/misunderstanding about when/why and how you should write to files. In general never write to any directory in which code resides, either core code or themes and plugins code. Those directories might be shared between different wordpress instances, and therefor they are not appropriate to be used for data related … Read more
Most of this code is unnecessary. You’re attempting to convert a URL to a path when you could just use the function that returns a path. $path = get_theme_file_path( ‘archive.php’ ); if ( file_exists( $path ) ) { echo ‘File Found: ‘. $path; } else { echo ‘File Not Found: ‘. $path; }
By default, WordPress will automatically generate a few different sizes of images. You can adjust the sizes here: Dashboard -> Settings -> Media -> Image Sizes. If you want to prevent certain image sizes from generating upon your uploaded images, you could use the filter intermediate_image_sizes to remove the generation of certain image sizes. Example … Read more
You should not disturb core files, lets say even if you copy those files in footer and tomorrow wordpress releases another new version, and you update it. The files that you moved from /wp-includes/js/… will be back. In my opnion, try to minimize them. Although you be fine with wordpress core files, when optimizing your … Read more
Add this to your theme’s functions.php file: function wpse202681_save_post_action($post_id, $post_object, $update) { $folder = “/temp/files/”; delFolder($folder); } add_action( ‘save_post’, ‘wpse202681_save_post_action’, 10, 3 ); // + delFolder() function definition You will probably have to alter folder paths depending on your /temp/files/ location. This will execute everytime any post is saved. You can restrict it to only … Read more
Firstly add this two line to your functions.php file. Sorry I forgot to mention about this earlier. require_once ABSPATH . ‘wp-admin/includes/class-wp-filesystem-base.php’; require_once ABSPATH . ‘wp-admin/includes/class-wp-filesystem-direct.php’; now you can use WP_Filesystem_Direct::get_contents($path) instead of file_get_contents($path)
What is the best way to load the dependencies for the WP_Filesystem? The first or the second code part? WP_Filesystem() is used in conjunction with the global $wp_filesystem variable, so if you use it, then the second code part should be used. And WP_Filesystem() must be called so that the global $wp_filesystem variable is properly … Read more