We have a Wordpress multisite 4.2.2 RPM installation on CentOS 6.6 and in the network plugins panel, the add plugin button and the plugins updates are not showing up (100% sure some plugins are not up to date).
The odd thing is when heading to /wp-admin/network/plugin-install.php, it says we haven't sufficient permissions to access the page. Note that we have a superadmin account.
So far, we tried to comment the config line define( 'DISALLOW_FILE_MODS', true ); and changing all the salt in the config ... no luck.
We tested our server connection to api.wordpress.org:443 and planet.wordpress.org:443 without any problem.
Also note that we have a second WP installation on the same server (not multisite) which is working as intended.
Any clue is welcome, thanks !
We find out it was a problem with the config.
We needed to keep define('AUTOMATIC_UPDATER_DISABLED', true); and we commented define( 'DISALLOW_FILE_MODS', true );.
But DISALLOW_FILE_MODS need to be set as false, not just commented otherwise default value is true i guess.
Related
WordPress in its own directory using Composer
Troubleshooting Elementor Infinite Loading Screen
Inspired by roots/bedrock, I started a project to install WordPress to its own subdirectory using Composer. Plugins and Themes are installed from WPackagist, separately from the core WordPress files, also using Composer.
I ran into an issue with Elementor, which was stupid simple to fix. However, when I was in the process of fixing it, my Stack Overflow query, 'wordpress composer “elementor” -visual', returned nothing interesting. So I set out to write a quick troubleshooting guide for my own oversight. I have been obsessed with using Composer for WordPress dependencies lately, so I'm excited to write about it.
Anyway, after setting up the WordPress core and plugins using Composer, and setting up my database credentials in wp-config, I can login to the dashboard just fine.
Here's the Issue
In the dashboard, I see an issue immediately; the Elementor icon is missing, showing a generic gear instead. Here is the first clue that Elementor cannot find its own assets.
Furthermore, when I try to create a new page in Elementor, I see only an infinite, white Loading screen. Additionally, the "Edit with Elementor" button is missing when creating new posts and pages.
Initial Debugging Methods
Turn on PHP debugging in wp-config.php -> Revealed nothing enlightening.
Remove all other plugins besides Elementor -> No changes.
Turn on Safe Mode in Elementor > Tools -> Revealed nothing enlightening.
What next?
I will tell you how I fixed this issue.
Developer Console Insights
To finally resolve this issue, I opened the developer console (CTRL+SHIFT+I) and inspected some of the 404 links in the Network tab. An issue was immediately apparent: the filepath was incorrect. My project's folder is called "subdir-wp-elementor", not "subdir-wordpress".
Here is what Elementor was trying (and failing) to load:
http://localhost/subdir-wordpress/app/plugins/elementor/assets/js/editor-modules.min.js?ver=2.9.12
Resolution: Update CONTENT_URL in wp-config
I realized that I had forgotten to update the CONTENT_URL definition in wp-config.php
My SITE_URL was http://localhost/subdir-wp-elementor/, but here was my CONTENT_URL:
// ========================
// Custom Content Directory
// ========================
define( 'WP_CONTENT_DIR', dirname( __FILE__ ) . '/app' );
define( 'WP_CONTENT_URL', 'http://' . $_SERVER['HTTP_HOST'] . '/subdir-wordpress/app' );
Setting the correct CONTENT_URL to the below allowed Elementor to properly load.
define( 'WP_CONTENT_URL', 'http://' . $_SERVER['HTTP_HOST'] . '/subdir-wp-elementor/app' );
I wanted to Upgrade the Wordpress installation, I clicked on the Upgrade to latest version link from my WP ADMIN panel and post that it has asked me to give FTP details for the Update for which FTP details were entered and Upgrade started. After few minutes I got Below ERROR and Now WP ADMIN is not loading. I tried to clear browser cache and cookies but still not working. Please Help in resolving the issue.
There has been a critical error on your website. Please check your site admin email inbox for instructions.
Learn more about debugging in WordPress.
I have further tried to debug and added below code in wp-config but i am not getting any errors on the page neither in the path /wp-content/debug.log file
is there.
// 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 );
Reference : https://wordpress.org/support/topic/wordpress-upgrade-failed-wp-admin-panel-not-working/
Dear users, please use manual update if you can’t update automatically.
See here:
Updating WordPress
You can do it with cpanel:
Simple copy wp-content & wp-config.php to a directory out of public_html (for example, create a folder by name “backupold” and put files in it)
Download latest version
https://wordpress.org/latest.tar.gz
Upload it in your wordpress directory (output file will be in public_html/wordpress for example)
Copy (backuped contents) “wp-content” folder & “wp-config.php” file to “wordpress” folder & replace
Move all files and folders from “wordpress” folder to your site directory (by default, public_html) & replace.
Now enjoy!
Warning: do a backup before, and do as i sayenter code here
Version -
WordPress 4.7.12 running Twenty Seventeen theme with Plesk Onyx has Web Windows Hosting Application
Error
When I login into Dashboard and select "Update" option for upgrading WordPress installation to 5.1, it loads for some time and then shows an error message:
The page cannot be displayed because an internal server error has
occurred.
There's no other text except for this.
Wha I've tried so far
I attempted to enable logging by adding the following three attributes into the wp-config file, but no debug file gets generated into the wp-content folder. I checked IIS logs, but couldn't see logs file updating.
define('WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );
Deactivated all plugins - Problem persists
Please suggest options to fix this or get more details.
I think that that's what error logs are for.
Try to create .user.ini or php.ini files in the same directory contains
error_log = phperrors.log
(absolute path is preferred)
And, then run your script again and then check for the same file.
Thanks
I've got a WordPress installation of a friend which was recently hacked. I fixed many malicious files, but no admin user is allowed to install new plugins or even update installed plugins or the whole WordPress system.
I already tried to us
define('WP_MEMORY_LIMIT', '256M');
in config file, but it didn't work.
Any ideas what I could try?
Thank you!
If found the solution.
Someone added the following lines into wp-config.php:
define('DISALLOW_FILE_EDIT',true);
define('DISALLOW_FILE_MODS',true);
define( 'AUTOMATIC_UPDATER_DISABLED', true);
Setting those to false solved my problem.
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.