I've just created a third level wordpress installation, I have added the line:
define( 'FS_METHOD', 'direct' );
in the wp-config file, but that's what i receive back when I try to open the site:
enter image description here
what am I doing wrong?
Related
My WordPress website https://poaa.ca/ is not loading and I'm facing a critical error issue for the last two days. I tried many tricks to fix the issue like disabled plugins, themes, and show errors. I added this code to my config file, but still errors not showing. What can I do? Your help will be appreciated.
define( 'WP_DEBUG', true )
define( 'WP_DEBUG_LOG', true )
define( 'WP_DEBUG_DISPLAY', false )
#ini_set( 'display_errors', 0 )
Did you try to Revert to a Default Theme. Remove theme and upload WordPress Twenty Twenty theme.
Increase PHP memory limit up to 128M - 1G.
Update PHP version.
One of these options will solve your problem.
To fix the issue,
Open your website Cpanel - File Manager
Inserted this code in your wp-config.php file to create a Debug Log.
`// 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 );`
it will log all errors, notices, and warnings to a file called debug.log in the wp-content directory. It will also hide the errors so they do not interrupt page generation.
Go to the Debug Log file, download, and open the file using a code editor.
If the error is from the post file, download this post file
Replace the file in the directory as shown in your Debug Log file.
Refresh your website, and enjoy.
Don't forget to go back to step and remove the code you added to Wp_config file
I get this error message when I try to put a comment on my site: The site is experiencing technical difficulties.
The error message shows up when a user tries to add a comment at my site www.ibdpage or when they try to register.
To track this down I have tried to look at the log file, but I can't get the log file to get written.
I put the lines in wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', '/public_html/ibdpage/wp-content/debug.log' );
define( 'WP_DEBUG_DISPLAY', false );
Also, the ibdpage.com site is a subdomain of my site napervillegi.com. It is one level deep in the file hierarchy. I have tried both using true or the path to the debug.log file as the argument to define('WP_DEBUG_LOG',...) and it failed both ways.
Meantime, what do I need to do to find out why the error log is not being generated?
define( 'WP_DEBUG', false );
Its already in wp.config.php file
You just need to change it like
define( 'WP_DEBUG', true );
If still you are not able to see the error while adding comments
then add this below line in theme at the top of functions.php file at
ini_set('display_errors', 1);
Hope it will work
Thanks
Start with the simpler:
define( 'WP_DEBUG_LOG', true );
If that is still giving you the "site is experiencing technical difficulties" error, temporarily rename your .htaccess file to ensure there are no strange rewrites causing an issue. This should at least get the logs being written to /wp-content/debug.log inside of this WordPress install.
Regarding the full path however:
define( 'WP_DEBUG_LOG', '/public_html/ibdpage/wp-content/debug.log' );
When accessing the filesystem, even though /public_html/ might be the highest you can go in the file structure of your cPanel account, often you need the full path, which would be something like this:
define( 'WP_DEBUG_LOG', '/home/accountname/public_html/ibdpage/wp-content/debug.log' );
Look for Home Directory in your cPanel or File Manager to discover the correct path.
I'm a WP noob but have to fix some bugs on an existing wp site. I don't want to do that on the live environment, so I try to mirror it in docker (apache, php, mysql...all with similar versions like on the live environment).
I copied all php from their ftp
migrated the mysql data
When I access this local site I get a 302 redirect to the live site
At the beginning of wp-config.php I added
define( 'WP_HOME', 'http://localhost:8180' );
define( 'WP_SITEURL', 'http://localhost:8180' );
But still the same.
Any ideas?
Here is the full wp-config.php as asked in the comments
<?php
/** changing the site url (https://codex.wordpress.org/Changing_The_Site_URL) */
define( 'WP_HOME', 'http://localhost:8180' );
define( 'WP_SITEURL', 'http://localhost:8180' );
define('AUTOMATIC_UPDATER_DISABLED',true);
define('DB_NAME', 'replaced');
define('DB_USER', 'replaced');
define('DB_PASSWORD', 'replaced');
define('DB_HOST', 'db:3306');
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');
define('AUTH_KEY', 'replaced');
define('SECURE_AUTH_KEY', 'replaced');
define('LOGGED_IN_KEY', 'replaced');
define('NONCE_KEY', 'replaced');
define('AUTH_SALT', 'replaced');
define('SECURE_AUTH_SALT', 'replaced');
define('LOGGED_IN_SALT', 'replaced');
define('NONCE_SALT', 'replaced');
$table_prefix = 'wp_';
define('WPLANG', 'de_DE');
define('WP_DEBUG', true);
if ( !defined('ABSPATH') ) define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
/* fixes safe_mode problems */
define('WP_TEMP_DIR', ABSPATH . 'wp-content/');
Update
I followed the running code using xdebug. The redirect went to the live site because of the database entry (options table) '_transient_pll_languages_list'. It cached the url to the live site.
As it's called transient I simply removed it. Now I still have the redirect (now 301) but to my local site. So now I have a feedback loop.
I guess I will search and remove all 'transient' entries next.
Is there a simpler way to remove all cached data from the db?
I had the same requirement myself to develop an existing WordPress site locally, so I made this repository: https://github.com/lumonald/existing-wordpress-development-docker
You can disable any caching plugins in the .env file, and it automatically finds/replaces the URL in the database for you.
It takes care of wp-config.php in the background for you, however if you need to edit this you can add it as a volume to the WordPress container within docker-compose.yml
Bare in mind this uses the latest version of WordPress, but this can be changed in the docker-compose.yml file, as can the MySQL version if needed.
I haven't used docker, but according to me the following code is missing the folder name.
define( 'WP_HOME', 'http://localhost:8180' );
define( 'WP_SITEURL', 'http://localhost:8180' );
It should be something like
define( 'WP_HOME', 'http://localhost:8180/foldername/' );
define( 'WP_SITEURL', 'http://localhost:8180/foldername/' );
Or else you can directly change the URL in the wp_options table, change the siteurl and home to your actual URL. Also, try clearing the cache folder or disable the cache plugin if it exists.
I hope this solves your issue.
Regards
I don't know exactly what the problem was but after deactivating the SEO Plugin the problem went away. The site still worked after the SEO Plugin was activated again.
So it was some kind of plugin cache problem I guess.
Am trying to build a test environment for a WordPress project using xamp.
Apache is listening on localhost:8080
MySQL is 3306 root with no password
Changes did in wp-config
Dbname is wp-db
Dbhost is locallhost:8080
Dbuser is root
WordPress root folder is in c:/xamp/htdocs/wordpress
Before changing the dbhost from local host to localhost:8080 I was getting a "error establishing connection to database" now am jus getting a full white screen.
Please advise. A million thanks in advance.
White screens are usually PHP errors. Try Debug and see what PHP errors you are getting. You may simply have an error in wp-config.php or are missing a core WordPress file or folder.
Add
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
in wp-config.php and the debug.log file will be in wp-content.
Add this line
define( 'WP_DEBUG_DISPLAY', true);
to wp-config.php to log and dump them to the browser.
See https://codex.wordpress.org/WP_DEBUG
You may have introduced a PHP syntax error when you were changing your wp-config.php - check the xampp PHP logs (edit see #markratledge's answer for more details on tracking down the error). After that, you were closer to the right setup when you saw the "error establishing connection to database" message, so in wp-config.php
Change the DB_HOST back to localhost (no port, as it seemed to work before)
Set your DB_USER to (eg) wpdbuser
Set your DB_PASSWORD to (eg) password (choose something more secure if the database is accessible externally)
If you haven't already, create your empty database by running the following in MySQL (WordPress won't create the database for you, you need to do that):
CREATE DATABASE `wp-db` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
Also in MySQL, create the user with the details you specified in wp-config.php:
create user 'wpdbuser'#'localhost' identified by 'password';
Finally, make sure your dedicated database user can create the WordPress tables:
grant all privileges on wp-db.* to wpdbuser#localhost;
I updated a clients Wordpress to 3.5.2 and now cannot login via wp-admin.
The login form appears but once I hit the Log In button I am just redirect to a blank page with a single . on it. Same happens if I enter the wrong password.
I have checked out the Login Trouble Codex and tried replacing the wp-login.php file and disabling all plugins to no affect. I get the same issue occuring.
Front of the site seems fine.
What appreas in debug:
Warning: Cannot modify header information - headers already sent by (output started at /home/stretton/public_html/fo/wp-content/themes/freya/lib/widgets/banners-125.php:13) in /home/stretton/public_html/fo/wp-login.php on line 369
Warning: Cannot modify header information - headers already sent by (output started at /home/stretton/public_html/fo/wp-content/themes/freya/lib/widgets/banners-125.php:13) in /home/stretton/public_html/fo/wp-login.php on line 381
EDIT: I have also tried:
Renaming my theme to defualt it to the twentytwelve theme
Renaming the plugins directory
Removing the widgets directory
Replacing WP-Admin with from a fresh download
No luck with these either
Rename the active theme and force a revert to twentytwelve. Theme issues can still sometimes cause admin errors. But once the theme reverts, you should be able to get into admin, even if the front end is white-screened.
To figure out what's causing the white screen on the front end (or, if needed, the backend, too) use Debug. See https://codex.wordpress.org/WP_DEBUG
Add to wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
and the debug.log file will be in wp-content. And/or, add this line
define( 'WP_DEBUG_DISPLAY', true);
to dump them to the browser, too.