After every WordPress release appears on my admin panel, my website .htaccess file becomes chmod 444 or 777 and overwrite my htaccess settings. I try to change the chmod and edit it from ftp and from the console. But It keeps returning to chmod 444 or 777. The work-around solution is that i have to update wordpress from the administration panel, then I can change the .htaccess chmod to 644 and edit it without any problem.
Please help me resolve this issue.
Thank you,
The proper way to upgrade WP is via the admin panel....
If you download the installation and do it all manually, then you need to check the umask for your user... which applies the permissions for new files.. actually there could be other reasons why the permissions change to 444, but the real solution is to upgrade via admin panel
Solved the issue by renaming wp-admin to wp-admin_old and wp-includes to wp-includes_old . Then I uploaded latest and fresh folders from the official website: https://wordpress.org/. DO NOT FORGET TO DELETE 'wp-admin_old' & 'wp-includes_old'! Because they have a hidden backdoor that keeps changing your wordpress settings. That's why renaming them then deleting them is the only way to get rid of malware.
This probably happened due to an infection, which may have changed more than the core Wordpress files. Simply updating the wp-includes directory may not permanently solve the problem: https://wordpress.stackexchange.com/a/191570/20963
Related
I am trying to install WordPress on my parent domain in public_html directory. it gives me this every time I try to install.
I tried to delete htaccess as well, changed permissions but nothing works.
I faced same issue and my issue was resolved by changing public_html folder permission to write.
I also faced a similar issue but just edited my file permission for the .htaccess file and try reinstalling WordPress.
I ran into this issue when installing a theme and tried the two below without luck, any idea?
Change the right to 777
Modify the wp-config
Can you please try once by putting the following code into wp-config.php
define('FS_METHOD', 'direct');
Hope it will work for you. You can also read more here
Below method worked for me:
Making the webserver the owner of the wordpress folder recursively.
chown -R www-data:www-data wordpress
Here's what worked for me :
From your Wordpress dashboard go to Settings->Media and set
"Store uploads in this folder" to "wp-content/uploads"
Everything was going so well: installed XAMPP on Mac (OS 10.10.2). Installed Bitnami WordPress module. Imported existing WordPress site (this site is already live). Then imported/installed the theme I want to modify. All good up to that point.
Now I want to create a child theme. Following the instructions from Themify, which are great. BUT: I can't open the htdocs directory within the wordpress dir that was installed by the Bitnami module. No permissions.
There's a help page, but it's not helping me. Reason 1: I open FileZilla, I FTP to localhost, but the wordpress dir is nowhere to be found there. Reason 2: I try to follow their sudo chown instructions but the path is not valid for me. I tried:
$ sudo chown daemon:daemon Applications/XAMPP/xamppfiles/apps/wordpress/htdocs
... but no luck. "No such file or directory." I can find this folder in the Finder (see screencap), but I can't seem to access it from the command line. (Is that because XAMPP is in the Applications directory?)
In case it's not obvious, I am doing all this to muck around with my child theme offline. But I can't get my child theme folder into the wp-content/themes folder, because I can't FTP or access the folder directly through the Finder.
I was able to change permissions through the Mac "Get Info" panel. Doh!!
"Get Info" panel, unlocked
See screencap.
Try and put a Leading slash at the front of the directory listing so run this instead:
sudo chown daemon:daemon /Applications/XAMPP/xamppfiles/apps/wordpress/htdocs
Just go to /Applications/XAMPP/xamppfiles/htdocs/mysite/wp-content/themes/your-child theme and set permission of your child theme folder to writable to everyone.
I urgently need some advice as to why I have to change all files I want to edit to 777? I think there maybe sound thing wrong with the apache user not being the owner. I can only edit any file if I set 777 so anyone can edit it. Any help much appreciated.
cheers
You shouldn't have to. Often this comes down to the group being incorrect. My wp-content is owned by the user apache and the group apache on a standard Slackware Linux installation.
File permissions are 664 on these. For me, I do:
chown -R apache.apache wp-content
chmod -R o-w wp-content
chmod -R gu+rw wp-content
This web page on the wordpress.org website seems to be addressing your issue exactly: http://wordpress.org/support/topic/file-permissions-avoiding-777
This isn't really a thing that can be controlled from wordpress, but seems to have some relation to the way your hosting company configures its servers.
I have a local install of wordpress.
I am having a nightmare setting the the permissions right.
If it set it all to 777 it errors 500, I have i set it 644 but still the same!
What exactly are the right settings under apache2
First of all Im developing wp plugins for a long time now and Ive never seen Internal Error 500 on 777 permissions. It might be a good idea to give us more detail about your server configuration.
Giving you an answer about the permissions is kind of complicated, because it differs from server to server, but generally I use it as follows:
wp-admin 755
wp-includes 755
wp-content 755
wp-content/images 777
.htaccess 644
wp-admin/index.php 644
wp-content/themes/your-theme/files 666
wp-config.php 640
Other files 640
Since it's a local version, have your tried setting your whole wordpress folder to permission 777? What operating system are you using? I used to get this under Ubuntu. Have your tried adding a simple php file to test if the link you're using is good?
Replying your question about permission: http://codex.wordpress.org/Changing_File_Permissions#Permission_Scheme_for_WordPress and http://wordpress.org/support/topic/wordpress-file-permissions will help you.