I installed the plugin W3 total cache but It crashed my website, so I had to delete it. The problem is that my site is still running. But I think I didn't delet it properly. I just renamed the folder of the plugin in the wp-content.
Another thing I did, I deleted the three files from the ftp : db.php, advanced-cache.php and object-cache.php
I didn't follow the instruction for delete the plugin and I didn't unchecked all options, disable and delete the plugin.
Is there any consequences and can I correct that?
Please help!
Usually renaming the folder does deactivate plugins as the folder is no longer detected. Some plugins however create files and database tables which will remain after this so you should always follow the recommended deactivation/uninstallation suggested by the developer. You can find a reply from the developer to a question similar to yours here - https://wordpress.org/support/topic/impossible-to-uninstall-completely/
Related
My wordpress site was working fine , but wordpress update it to V 5.4 and after that my website is not working , not even i can access my admin dashboard.
I tried all these step to solve this
MANUAL INSTLLATION (RECOMMENDED)
Download the WP Safe Mode plugin and unzip it, you’ll now have a
wp-safe-mode folder.
Connect to your server (for example via FTP) and go to your website
folder.
Add this line to your wp-config.php file:
if( !defined('WPMU_PLUGIN_DIR') ) define( 'WPMU_PLUGIN_DIR',
dirname(__FILE__).'/wp-content/wp-safe-mode' ); //WP Safe Mode
Create the folder named wp-safe-mode inside your wp-contents folder.
Uploade the file wp-safe-mode/bootstrap/wp-safe-mode-loader.php into
the newly created wp-safe-mode folder.
Upload the entire wp-safe-mode folder to your plugins folder in
wp-content/plugins.
If your site is broken and you cannot install plugins or access the dashboard, you can modify the loader file temporarily to gain access by following these additional steps:
Open the plugin file wp-safe-mode-loader.php and change this line:
public $safe_mode_on = false;
to
public $safe_mode_on = true;
Upload the modified wp-safe-mode-loader.php file to the
wp-contents/plugins/wp-safe-mode folder.
Visit your site, deactivate plugins etc.
Undo the changes you just made to wp-safe-mode-loader.php when you
want to disable safe mode.
But nothing works for me. Can you please suggest something so i can fix my problem
Theme Conflict Troubleshoot:
To perform this, you just activate a default theme, like Twenty Nineteen. Unfortunately, because your site is showing an error, you will need to perform the troubleshoot with either your web host’s file manager (like cPanel’s Filemanager), or use FTP or sFTP (it’s like secure version of FTP.) It’s important to note that in switching themes, you won’t lose your chosen theme’s settings. To do this, you rename your active theme’s folder by adding DISABLE or OFF to the end of the folder’s name. For example, if you’re using Twenty Eighteen and the folder is ‘twentyeighteen’, you would name it ‘twentyeighteenDISABLE’ or ‘twentyeighteenOLD’ . Go back to the front of your site and refresh.
The objective is to check whether the mistake leaves. In the event that it doesn’t, it is anything but a subject issue. Try to rename the organizer back to its unique name when you’re finished investigating.
Plugin Conflict Troubleshoot
If it’s not the theme, it might be a plugin issue. In a way, troubleshooting is similar. However, it’s much easier to rename the plugin folder to ‘pluginsOFF’. Visit the site, and log-in. This will turn off all of the plugins. Please note that it won’t remove the original settings of those plugins, as they will be there when you reactivate them later on.
Once the plugins are off, go back and rename the folder back to ‘plugins’. Go to your WordPress admin area and reactivate each, one-by-one, until you get the screen that says “There has been a critical error on your website”. The plugin that you just reactivated, is the problem.
You can either disable the plugin that caused the problem or remove it or roll it back to the previous version using the rollback plugin and wait until the developer releases a new version of the plugin.
I noticed this new wordpress version I'm running has a "Endurance Cache" option at the bottom of the "Settings > General" page.
That is caching all of the changes I'm doing on css. So whenever I update something the changes don't reflect on the browser instantaneously.
I'm wondering if that's wordpress native or if I can remove it.
I'm using wordpress 4.8.1.
My other website that has an older wordpress version doesn't have it.
It's not listed as an installed plugin. So that I don't think it is.
I'm using thesis theme.
thanks
It is a plugin installed by hostgator. They install two plugins "Endurance Browser Cache" and "Endurance Page Cache."
You can disable the Endurance Page Cache plugin by going to "Plugins" > "Must-Use" then locating the "Endurance Page Cache" plugin and clicking "disable."
The other plugin called "Endurance Browser Cache" does not have a disable button.
I hope this works for you. I do not know if hostgator will remove these plugins for you.
Here is the easiest solution I found for it:
Log into your Cpanel and click on Files.
Choose your domain/subdomain and click on the WP-Content.
Click on the "mu-plugins".
Rename the File "endurance-page-cache.php" to "endurance-page-cache.php.old"
Create a blank file there and name it "endurance-page-cache.php"
That's it, problem solved. And if you ever in the future want to activate it again, simply delete the blank file that you created and remove the word "old" from the original file name.
I found the issue. It's a plugin installed by hostgator.
Unfortunately it's not listed in the wordpress plugins area.
So I needed to request them to remove it.
To get rid of Endurance Page Cache or whatever other mu-plugin that you don't need, you can now use Mu Manager.
After activation Go to Plugins => Must Use, and deactivate the unneeded mu-plugins that you don't need. It will be like deactivating standard plugins.
Of course, you should know which mu-plugin are not needed. In the case of Endurance Page Cache, I think you never need it if you have a proper caching plugin.
If you prefer to use FTP it will be not enough to rename the mu-plugin, because it will run the same. You need to delete it or replace the extension .php with something else.
This caching plugin was installed most probably by your hosting provider. A brief and quick solution to the problem:
Instal WP File Manager Plugin:
https://en-gb.wordpress.org/plugins/wp-file-manager/
Go to the plugin settings and head over to htdocs/WP Content/mu-plugins
Find the file "endurance-page-cache.php" and either rename it for temporal deactivation or delete it altogether if you want to get
rid of this plugin.
If this was the only file in the folder mu-plugins, you may as well delete the folder mu-plugins. "MU" stands for "Must Use". Sometimes a hosting provider or a developer might install their custom code for a site project as an mu-plugin so it doesn't get uninstalled by their customer.
Uninstall WP File Manager Plugin as it's not needed anymore. Better look on how to access your site files using C-panel if provided by your hosting provider or via FTP (like Filezilla) rather than a plugin.
Get a proper caching plugin. (Give Cachify plugin a go - it is free).
I can't figure out why my wp site is stuck in maintenance mode. I made no update and there's no .maintenance file. I can't even access to admin.
Has anyone encountered similar issue?
Try renaming the plugins/ folder to _plugins/ and see if you can access your website, if you can, rename the plugins folder to plugins/. Try disabling every plugin and re-enabling the plugin until your site breaks again to find the culprit.
If you can't access your website after renaming the plugins folder, disable your theme (by renaming the folder).
These are the common troubleshooting steps, if you provide more details, I will be able to help you more :/
Finally got it, it was a domain redirection error. The url pointed to a folder with a default index.html.
If anyone is still having this problem in 2017, I fixed it by going to my /wp-content/endurance-page-cache and deleting two files called _index.html and a_index.html (to be safe, I would download these first so that if this ISN'T the issue you can still recover them). This is what my domain was redirecting to.
Before I figured it out, I deactivated the WP Maintenance Mode plugin, looked through the directory for a .maintenance file (which I didn't find even after showing hidden files), and completely deleted the plugin. So hopefully if anyone is having this issue, this will work for you!
I'd like to add a installation of a Wordpress site to version control. After researching a little bit, I found some files/folders that should be ignore, like sitemap.xml and cache folders.
Every single one of them say I shouldn't ignore wp-content/plugins/, which is a reasonable advice at first. The question is: How should I deal with plugins that alter the database?
I can see two scenarios:
If the plugin has to add some tables on installation, this trigger would be lost since it would already be "installed" after uploading the files to the server.
If I must access the installation screen on production, then there's no reason to version control these files.
I would suggest to take a look at this great presentation. It's the most complete I saw yet.
http://stevegrunwell.github.io/wordpress-git
You should have your plugins directory in there too since you do want to track plugin files. As for the database, that's another subject completely. Take a look at the development of VersionPress, it should be out at the end of the year.
I've been trying to uninstall a magento plugin I've recently installed to reinstall it using Magento Connect. The log said that the plugin uninstalled successfully and if I go to the admin panel, the plugin's no longer there but when I went back to Magento Connect, the plugin is still listed there so I can't reinstall. Why is this happening?
Based on the answers, what I've tried so far are:
Clear cache through Admin Panel
Removed wordpress entry in core_resource
I've made sure wordpress xml in etc/modules is removed
I've made sure Fishpig folder in app/code/community is removed
Cleared cache in var/cache
Cleared cache in downloader/cache
Checked if there's xml for wordpress in var/package (there was none)
Reindexed magento
And none of this worked. The wordpress extension was still listed as installed in Magento Connect. I've been trying to uninstall repeatedly but it just won't go away even though the log said that the uninstall process completed. I've also tried reinstalling and upgrading. No success.
to remove the extension:
remove all the modules files, includeing the file which enables the module:
app/etc/modules/COMPANY_MODULE.xml
also make sure the entry is gone from the database by removing the correct entry in table:
core_resource
then refresh the magento cache
It should then disappear from connect.
Which module have you installed? Can you give me name so I can give you solution if possible for me. If module add new own tables in db then dont delete any module file otherwise may be magento crash. Its better way to uninstall from magento connect manages.
Clear the .cache folder in the downloader directory, in addition there is also another area where an xml can be present in var/package/
The package files are from magento connect so delete from here and have another check!
delete all files in var/cache/ and double check you are actually working in the right folder! if you have another caching system then clear it.
To delete the extension from Magento Connect (I believe you have already uninstalled it from Magento) you will need to delete the file var/package/Fishpig_Wordpress_Integration_{{version}}.xml
Thank you very much for all your help and time. I really appreciate it. I've managed to solve the problem. It's apparently a problem with permissions. I didn't realize soon enough that the permission for all folders had to be 777. I had most folders set to 777 except for 2 files on my etc folder (local and locals.xml) because of security issues. But after getting a go signal changing said permissions, I managed to uninstall the plugin and reinstall it. Now the Wordpress is fully integrated in the website with no problems and I've also returned the permissions for local and locals.xml back to it's original. Thanks again a lot for all your time.