Conversation
supportHey there! After the latest update, the below changeset created 403 errors in the wp-content/uploads folder and files could not be loaded anymore. function fep_create_htaccess_index( $path ) { if ( wp_is_writable( $path ) ) { wp_mkdir_p( $path ); if( ! file_exists( $path . '/.htaccess' ) ){ // Create the file if it doesn't exist file_put_contents( $path . '/.htaccess', "Options -Indexes\ndeny from all\n" ); } if( ! file_exists( $path . '/index.php' ) ){ // Create the file if it doesn't exist file_put_contents( $path . '/index.php', "<?php\n// Silence is golden." ); } } } https://plugins.trac.wordpress.org/changeset/2976131/front-end-pm/trunk/functions.php Removing the deny from all line from the created .htaccess file immediately fixed all issues and the website loaded as expected. I cannot be sure if this has anything to do with the shared hosting environment I am using, but wanted to bring your attention to this in case other Front End PM users/customers are facing the same issue. Thank you! Kris
Thank you for letting me know. .htaccess files are needed to prevent direct file access. But it needs inside front-end-pm folder. In version 11.4.1, it may create .htaccess file outside of this folder. If it does in your website, then you can delete .htaccess file in wp-content/uploads , leaves others as it is.
Hey, Shamim! Thank you very much for releasing a quick update. Have a great day!
Thank you for letting me know. .htaccess files are needed to prevent direct file access. But it needs inside front-end-pm folder. In version 11.4.1, it may create .htaccess file outside of this folder. If it does in your website, then you can delete .htaccess file in wp-content/uploads , leaves others as it is.
Hey, Shamim! Thank you very much for releasing a quick update. Have a great day!