Maintenance mode and HUGE CRASH

Rename the plugin and see if you can access your admin area.

Once in revert to the original format and test, if all is ok go ahead and upgrade to the latest version. Don’t forget to deactivate the plugins first and most important of all do a backup.

i did attempt to rename the folder of the plugin and it did not work

@zgani — folders don’t use extensions… I think you are suggesting renaming the php files where the initial poster is saying they renamed a folder containing the plugin.

Don’t rename the folder — use FTP and delete that folder on the remote server (you have a copy locally anyway). Renaming the folder only changes what is listed — the file(s) is/are still load (assuming they still use .php or recognized file types) and if the code in the file is the problem, it still is a problem.

If you delete the plugin folder (or file if just a single file) from the remote folder, it shouldn’t list at all in your plugins, nor will anything be executed.

You can always upload it again. Any settings options you may have set remain in your database.

this is what im getting after i renamed the folder as well as deleted it

https://www.maclaarte.org/wordpress/

so there isnt a way to get the articles over from the old site and categories because it will also copy over the setting and plugins?

IT’s not copying…

You cannot just move the WordPress folder… all the URLs used in your site reference the location of things relative to the root of the WordPress installation location. So, if you’ve installed in / and then move everything to /myblog/

Things break.

If you export out the data tables (I use phpMyAdmin to do this and export an .sql file) and backup your theme folder and plugin folder, you can remove the current install and reinstall to wherever you want (let’s say you are going from / to /myblog/ and your domain is example.com)

But you’ll have to open the exported .sql file and find and replace all instances of https://example.com/ with https://example.com/myblog/ to make everything work properly.

Using phpMyAdmin, you’ll drop all the tables of the new wp install and import the modified .sql file

Then add your theme & plugins folder to your remote server using FTP, placing the theme folder inside the /myblog/wp-content/themes/ and the plugins folder inside /wp-content/

All the posts and pages and plugins from your old site will be in the new one.

That’s how I move a WordPress site. There are ways to do it otherwise, but this works best for me because I can adjust all references to the incorrect URL from the Find and Replace dialog. BTW, I use code view of DW CS3 to modify my .sql file, having added that extension (.sql) to DW’s Edit Preferences > File Types list.

But none of that deals with a plugin that is breaking things… if you do all of the above, be sure not to upload that problematic plugin to the new install.

Don’t rename the folder — use FTP and delete that folder on the remote server

you are quite wrong about that – renaming a plugin folder deactivates the plugin

I think we’re both correct, depending on the state of the plugin…

I did a fresh install of wp, then used FTP to rename the Akismet plugin folder to “Bob” and in my plugins admin page, Akismet is still listed.

And, I was able to activate it without issue.

How is that disabled? I can see that IF a plugin is

• active

and you change the name of the folder, that would be the case, but I always deactivate them before move to a new install or upgrading an old one.

My point was more that when you DELETE a folder, you KNOW it’s not there to run. And anything inside of that folder is gone, too.

You can always upload the plugin again. Just my two.