"Unable to create Directory" on wordpress running on XAMPP - wordpress

In these days i am experiencing an annoying error. I am trying to add plugins and themes on my wordpress site, which is handled by XAMPP running APACHE webserver and obviously MySql database. Everytime that i try to install a plugin (woocommerce in this case) i get the output below:
So I tried to change permissions on all the wordpress directories (I am on windows 10), but that has not solved the issue yet. I find it pretty strange.
Actually woocommerce folders are stored anyway in the File System:
I am not able to use the plugin from the site, anyway. I definitely need someone's help.

Just need to change folder permission and follow the below step:
Change folder permissions on the wp-content directory to 775 and try to upload it again.
If it fails, change the permissions to 777 and try to upload it again.
If it still fails then do steps 1 and 2 for the “wp-content/uploads” directory too and try to upload it again.

Related

How can I fix wp all in one migration permissions error?wordp

I have been using wp all in one migrate to import my staging site into my local environment(XAMPP). after importing the staging, there was an issue that cause me to delete the local files for the particular site all together and start over. However now after creating a new wordpress site in my local environment and dowloading the plugin again, the plugin gives an error saying to Please make sure that storage directory C:\xampp\htdocs\website-name\wp-content\plugins\all-in-one-wp-migration\storage has read and write permissions.
I've tried the following with no success:
followed the instruction suggested by the plugin which were to
change the permissions of the file by right clicking into
"properties"... all of the users have full control.
used ls -al in git bash to confirm that my username shows as the owner of all the files.
changed the user and group name from 'daemon' to my username in httpd.conf
added define('FS_METHOD', 'direct'); to wp-config.php
deleted and reinstalled the plugin as well as the entire database.
so far I keep getting the same error. I also checked other local wordpress sites I have and they all seem to have the same issue now. Any suggestions?

Getting critical error when installing Wordpress

My hoster forced me to upgrade my Wordpress site because it was fairly old. I decided to upgrade to PHP 8.1. It caused issues with the website, so I figured I'd rebuild the whole website since it's a simple website. I deleted all the existing files and uploaded the 5.8.2 WordPress install files. Then I changed all the permissions to 0755. I created a fresh database for the install.
At first, the setup would appear. I would go through the install, but when I clicked install after entering all the database info, I got "There has been a critical error on this website." I recreated the .htaccess file to the default and tried again. Now I get this error just hitting the domain, no more setup screens. The site does redirect to the /wp-admin/setup-config.php file. I don't have a wp-config.php file in the directory, just the sample one. I tried creating a wp-config.php with the correct info, but same error. I also tried adding the debug options, increasing PHP memory, etc. Same error. I don't get any error logs.
Does anyone now how to get an error log or can help with ideas on how to create a fresh WordPress site? I did change the PHP versions to older ones, but that didn't work either.
You need to take a backup of your file ,then fallow the fallowing instruction.
Rename your plugin one by one and refresh the website.
this issue due to the unsupported plugin ,that is installed in your wordpress website.
1- Make a backup copy of the files and from the old database
2- After that, download these files on your PC
3- Install WordPress again
4- Replace the wp-content file with the old one
5- Clean the new database and import the old database through phpMyAdmin
I solved that problem installing an older version of Xampp, with previous version of php, MySQL and Apache. I give up version 8.1.1
XAMPP 7.4.27 / PHP 7.4.27
https://www.apachefriends.org/download.html
There was something wrong on the hosting side. The source of the issue was indeed that WordPress could not write to the config file. Even the hoster was unable to delete the files. We ended up deleting the entire root directory and starting from scratch. Now it's all good.
The lesson learned is that one of the sources of the "There has been a critical error on this website." error is that WordPress is unable to write/edit files. It's also why it could not write an error log. WordPress could have been more descriptive here.

Not Acceptable?

My site is running but I could not log in to admin dashboard, got this error
Not Acceptable!
An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.
After googling I found out it has to do with mod_security. I tried every approach to fix it: changed my plugin folder name, tried disabling mod_security with .htaccess but the error remains the same.
Are there other alternatives that I could take?
Difficult question! To be honest, I wouldn't try to fix it. I would suggest copying files and database to a local WordPress. If everything is running on you local machine, I would delete the WordPress server version and install a new WordPress and copy the database and all the files.
If you think of the hours, you try to fix it instead of copy the whole WordPress and install a new one.
please delete you .htaccess file from the root directory and try to login into wp-admin. Once login gets successfully then regenerate the .htaccess file.
For regenerate the .htaccess file you need to follow the below steps:
Go to setting -> permalink -> change permalink into default.
And save the setting.
After save setting then change permalink into the post.
Now you can see that the .htaccess file gets generated successfully.

Fresh Wordpress install on Amazon Linux EC2...can't delete and reinstall

I just recently started by creating a EC2 instance on AWS. I used the Amazon Linux package. I changed the PHP settings to include the ability to upload files larger than 200MB. Got phpinfo.php working. Installed phpMyAdmin. Everything looked good.
Next, I installed Wordpress. It worked great. Then I tried installing a theme. Worked great. Then I started installing some plugins for that theme. Something made the site crash. I tried a few things, but since I couldn't go to the sites Wordpress Admin panel, it seemed hopeless. So I decided to start from scratch. I deleted the html directory (including wp-content) and dropped all the wordpress tables. I moved a fresh copy of Wordpress into the html directory, reconfigured the config.php file, and it recreated the Wordpress tables in the database. Seems to work great. When I try to upload a theme, it says:
Connection Information
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.
I noticed that wp-content didn't have a uploads directory, so I created one. That seemed to let me upload the theme, but it showed up as a media file. I moved it to the theme directory and that worked. But when I tried to upload a plugin, I got the same message as a above.
What happened when I deleted everything? Or rather, where was information stored that when I reinstalled Wordpress, it didn't create a uploads directory? I am fine with reinstalling Wordpress from scratch, but I don't want to reinstall the whole LAMP stack or redo the AWS instance. Any thoughts?
The issue is that your web server doesn't have the proper permissions to write to your content directory.
The WordPress Codex has some good info for proper file and directory permissions. Ideally, all files should have 644 permissions, and all directories should be 755 (no higher).
If you're still running into issues adding plugins and updating WordPress, you should heed the advice of the following (so that you don't have to enter FTP details into WordPress each time):
Any file that needs write access from WordPress should be writable by the web server. If your hosting set up requires it, that may mean those files need to be group-owned by the user account used by the web server process.

WordPress Local Install Error (XAMPP) - Page 2 is Blank

I'm trying to install WordPress for local use with XAMPP. I started off by installing and unzipping both the XAMPP and WordPress folders. I placed the XAMPP folder in my C:/ drive and my WordPress folder within the "htdocs" folder. After that, I made a new "config" file for my local server based on the "config-sample" file.
Here's where things get tricky: when I try to use the "install.php" file, I am brought to a screen that asks for credentials. I give it some generic credentials and then I submit it in order to install WordPress. However, when I submit the form, the loaded page is completely blank and the URL appears as "localhost/wordpress/wp-admin/install.php?step=2".
When I go into the database, it shows me that WordPress created all of the necessary tables, but didn't create any log-in credentials for me. I was doing some research and there were a couple pages that mentioned the need for increased PHP RAM, but I'm unsure of how to increase the RAM for local use or if it's even a problem. If anyone had an error like this happen to them, I would really appreciate some feedback as to what could be causing this problem.
I had the same exact problem, with an almost blank screen on step-2 passage.
Adding in wp-config.php these lines solved everything:
define('WP_MEMORY_LIMIT', '128M');
set_time_limit(60);
I've installed Wordpress 4.0 from a zip file on XAMPP 1.8.3 on my Win7-32bit PC.
Setting up the DB and all, I got the same "blank screen" at the step 2.
So, I went in to phpMyAdmin, and edited the "wp_users" table on my entry. I modified the user_login and the user_password (using an MD5 converter). Saved the entry and got into the localhost url for wordpress. Got into the log in, and everything seems to be working without any issues.
As a note: I installed a fresh/clean install so there were no custom themes nor plugins.
Hope that helps.

Resources