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.
Im on a mac running Sierra 10.12.2 and apache 2.4.23
I set up a localhost environment and a virtualhost for the domain cumsa.mx and installed wordpress on it. Without getting too into detail now, some changes were made on Git that modified the wp permalinks, and hence the .htaccess file through wp.
I went to my main httpd.conf file and told it to load the module mod_rewrite as suggested by a colleague since that was necessary to be able to modify the htaccess file. Regardless of that, activating this module results in my local environment for cumsa.mx to become "Forbidden".
Can anyone think of any idea why this wouldbe the case or which permissions I need to modify and how? Thanks!
i am using WordPress 3.6.1 and I have strange problem today. First I have to tell that my current website was copied from old website, both the WP files and database.
So in the current website, I try to install new plugin, but it returns error:
Downloading install package from http://downloads.wordpress.org/plugin/xml-sitemap-xml-sitemapcouk.zip…
Download failed. Could not open handle for fopen() to /home/k5841724/public_html/wp-content/uploads/xml-sitemap-xml-sitemapcouk.tmp
Then all my plugins are dissapered (Akismet, Hello Dolly, etc), and I can't install any plugin. Nothing wrong with my permission, /wp-content, /wp-includes, /wpcontent/uploads all are set to 755. Any idea what is the solution for this issue? Thanks.
addition note:
all my plugins folder (Akismet, etc) still there inside wp-content/plugins folder, but not appear in WP Dashboard.
You should check permissions for folder wp-content/uploads
I think wordpress can't write to this folder. Set for this folder permission 777 and try again.
I have experienced the same error with plugin installation.
In my case it was very informative to change WP_DEBUG to true in my wp-config.php file.
After doing so I have noticed the error message, telling me that open function is disabled due to security reasons.
Try changing your php.ini settings so that disable_functions doesn't contain fopen
I already tried doing the php.ini memory=20MB solution but it did not work. I uploaded it under the wp-admin/ folder.
I'm not really sure what else to try. Help?
The memory bump doesn't go into an .htaccess file in wp-admin. It goes into the .htaccess in web root. Use FTP to find and delete the .htaccess file you put in wp-admin.
Then forget about .htaccess files and try adding the line below near the top of your wp-config.php file, a few lines after the opening <?php
define('WP_MEMORY_LIMIT', '64M');
Renaming plugin directory temporary solved the problem for me
This problem occurs because your php dont't have any xml or has a deprecated version xml, so if you manually instal or update your xml, the problem will be solve.
If you using Ubuntu, try execute this code in your terminal:
sudo apt-get install php-xml
After this you need to restart apache so it takes effect, for this execute the command:
sudo service apache2 restart
Go to setting -> permalink and then select any common setting after that save it.
Reload the website. Everything will be fine.
Then reset it to previous common setting so that it will not effect for URL.
A 500 error is an Internal Server Error, which sometimes can be a hosting configuration problem, but in WordPress it is often a fatal PHP error.
First, just remove that php.ini file - some web hosts do not allow you to modify the PHP settings, so let's take that out of the mix first.
If it is a server error, temporarily rename your .htaccess file to something else (to take it out of the mix as well). Also, check for an error_log file in your filesystem, or the Error Logs in your hosting control panel.
If that doesn't tell you anything, it is likely a PHP issue. Turn on WordPress Debugging by adding the following code to your wp-config.php file:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
#ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
Make sure you comment out the line that says:
define( 'WP_DEBUG', true );
Now, when you refresh the page and get the error, WordPress will write any PHP errors to wp-content/debug.log. Check that log for a fatal PHP error - it will tell you which file is causing the error, often a theme or plugin file.
Once you know the cause, rename that theme or plugin to temporarily remove it from WordPress. That should restore normal functionality.
Another important fix for the internal server error is to try and upload a fresh version of wp-admin and wp-includes to your site.
This step should be a last resort, but if you’ve used the above solutions and still cannot find one that works, it’s worth a try. Backup your site, and download a fresh version of WordPress from the main site.
Extract the files from the ZIP file, and open the extracted folder. Open your site’s root directory in an FTP client, and upload the wp-admin and wp-includes from your fresh version of WordPress to your site’s directory, overwriting the older versions.
Refresh the client, and refresh your site. If the error is gone, it was likely caused by a corrupted core file. If you still see the error, you may have no other option than to contact your host. Check it out for more WordPress internal server error fixes.
I uploaded a freshly downloaded copy of Wordpress 4.2.2 here: http://www.onedayonemillion.com/test/ and all I get is a blank page.
There are no .htaccess or wp-config.php files in the root directory.
No database has been connected yet.
I tried the same in another directory (/dev/) and it did the same.
I have no plugins installed or activated.
This is a fresh copy.
I added an phpinfo file here: http://www.onedayonemillion.com/test/info.php
Why can't I even get the install page to show up?
I didn't understand why there is no wp-config.php in the directory, it would be good you post what is in the directory. Anyway, you can check items like (sometimes it is just that):
some files with no ending "?>" ending the file;
any require_once methods calling non-existing files
(you said no, but) wp-config has wrong or non-set definitions (user, database)
check permissions/ownership to the folder
Well, I know it can be lame, but I had problem with definition in WPLANG define,
so I put an
echo "<br> there is no error until here";
through the files untill I find that was missing a comma at the definition. If the phrase is displayed, your installation files untill that point are working out.
Your phpinfo says the display_errors is off.
modify your php.ini with this line:
display_errors = on
you should restart the server after modification.
you can only track the error only if the error reporting is on in the server