Is the Wordpress /wp-admin folder generic? - php

Can you replace the /wp-admin directory of a Wordpress installation with another one without issues?
This question is very open, but my current context is that I'm transferring a Wordpress site from one server to another. I've just come to download the site via FTP, and the /wp-admin folder has disappeared. (I probably did something wrong, but I did not knowingly delete the folder). I have a development version of the site, and am wondering if it will cause problems to just use the /wp-admin from that.
Has anyone come up against a similar thing before, and does anybody know if this folder is generic?

You need to replace the folder with one of the same version. See http://codex.wordpress.org/WordPress_Versions
There are, of course, updates and bug fixes along the way in many, but not all, versions, and a copy of wp-admin of a version not the same as the rest of the install will break things.
Check the file version.php in wp-includes to find the version of your WordPress install. ( version.php is not in wp-admin). And file modification dates are not a reliable way to check versions.)
See https://wordpress.org/download/release-archive/ for all versions.

As long as no modifications to the core of WordPress have been done, you should be fine, but make sure that the wp-admin folder you're uploading belongs to the same WordPress version your website is running. You should face no issues at all.

Firstly, if you did have a Dreamweaver then try to search a word 'wp-admin' in Entire Website Folder in the search's Dreamweaver option.
Secondly, change all text that contain a word 'wp-admin'.
Third, change the folder's name.
Then test your wordpress, if there are errors so try to solve it or post a comment.

Related

wordpress update_core.php, themes.php and plugins.php error

Initially i thought it might be a plugin conflict, so i renamed the plugins directory to plugins-temp and created a new empty directory "plugins" to reinstall them one by one to see which one caused the problem. However, the error still occurred even with an empty plugins directory. After that I thought that it might be a theme issue, so i tried to change the theme from wp-admin, and i noticed that that page also returns an error so I changed the custom theme to "twentysixteen" in the database. However, the themes page still returns an error and the plugins page wasn't working either. Poking around the wp-admin page i also found that the updates page on the dashboard was returning an error. I assume it is a database conflict but i cannot reset the entire database. What values could i reset in the database that would reset the settings on those pages? In addition, I also updated to the latest version of wordpress(4.8.2).
Any advice is greatly appreciated!
In your situation it is very hard to pinpoint what's wrong with your website but you can try narrow down the source of the error.
Possible causes:
There might be a corrupted file somewhere in your WordPress core or broken theme or badly coded plugin that mess up your database.
Backup first:
Nevertheless try backing up all your WordPress files including the database before doing anything else.
Reinstall:
Once you have your backup delete whatever files you have and reinstall your site bit by bit to troubleshoot the issue. This will also ensure you have a clean WordPress core files.
Install a fresh copy of WordPress with default theme and database installed.
Once done upload your theme and activate it and make sure the site is showing up just fine.
Followed by upload folders and plugins. Reactivate the plugins and check the site again.
Lastly replace your database file and check the site, if there is no error that means the error should be somewhere in your core or the templates. If there are errors then the errors most likely originated from your database.

Where I should store the Wordpress site in Xampp (linux)

I never use Wordpress but I usually use Xampp (Linux) to work.
So, I installed Wordpress and it works fine, if I enter with my browser to http://localhost/wordpress/ I can see the WP page.
I got from a friend his WordPress site files and stored them in /opt/lampp/htdocs like any regular web site, but when I try accessing http://localhost/folder_name/ I get the Index of folder_name and not the actual site.
I noticed that /opt/lampp/apps/ has a "WP" folder, and inside it - an htdocs folder like xampp have.
Where's the correct place to store the WP project ?
Is it /opt/lampp/apps/wp/htdocs or opt/lampp/htdocs/ ?
How can I get the WP site working and not get the index of / page?
You want to put the root of your WordPress installation in the same location you would put anything you want to be able to access at http://localhost. From what you're saying, it sounds like that is /opt/lampp/htdocs/
The Problem
WordPress runs just about everything through a database, including it's siteurl and home directory values. If you don't have a database at all, nothing is going to work. You'll find more on this problem Here.
The Hard Fix
You could try Migrating your friend's WP install to your XAMPP server, but you'll need their database for that to work. You could then use a tool like Wordpress Database Reset, which will get you back to basically a fresh install, just with any themes and plug-ins your friend's install included.
The Easy Fix
Since it sounds like you want a fresh install with a custom theme or plug-in from your friend, you can just start with a fresh install, and then add any themes and plug-in's in. Installing WordPress is fairly simple since they have a web-based installer to help you get everything set up. Check out this guide. Once you've got the basic site set up you can import any themes and plug-ins you want from your friend's WordPress installation.
I hope this helps!
I have read your problem folder path correct is opt/lampp/htdocs/
you need to make all services enable for server.

How to access php project from localhost (Apache)

I know this question may first appear to be a duplicate of others, but I'm asking this because I have WordPress installed in my /var/www/html directory. I was learning WordPress a couple of years ago before creating a website and never used it again.
Well, I'm creating a php project using PhpStorm and testing in my browser. I'm following a tutorial so I can configure my databse (phpmyadmin), and the instructor keeps going to his localhost, which displays the directory structure as seen here:
Since I have WordPress on my localhost, navigating to that takes me to my WordPress installation, which is not what I want to access.
I would rather ask this question on here before I potentially break my Apache configuration, so how can I access this project? Do I need to remove WordPress completely? It would be nice to keep it for future testing since I'm slowly getting into making plugins.
What are your suggestions? I can't really say much as far as "what have you tried?" since I don't know where to begin.
Running in Chrome within my PhpStorm IDE takes me to localhost:63342/projectName/respectivePhpFileName.php, but I can't access it outside of the IDE yet.
Any help would be appreciated.
Just move your Wordpress outside your htdocs folder...I think he is using something like XAMPP so in that way is very easy to do it, because the folder without an index will be detected as a directory not a Wordpress URL (correct me if I'm wrong). So if that doesn't works, just go to your htdocs (/var/www/html or opt/lampp/htdocs in Linux) directory (or where your wordpress is stored) and move it to other folder (like My documents) where you can backup it, and that's it, you can create that folder and keep following that tutorial.

Will a new WordPress install on my subdomain overwrite everything on the domain?

I have a website (http://neabors.com) hosted at BlueHost, and I have created the subdomain, news.neabors.com (it's not published yet). The original site is a social network, and the news subdomain is going to be, well...news. I want a completely different theme/plugin setup, so I thought I should install WordPress separately on the subdomain.
Well, I get to the installation guide, and I'm supposed to check this box:
I'm not going any further because I don't want to break my site. I've put too much work and money into this thing.
I understand how to edit my wp-config.php file by adding
define( 'WP_ALLOW_MULTISITE', true );
and I'm aware that I may need to edit my .htaccess file.
My main question is what should I do, install Multisite on my single WordPress installation, or am I misinterpreting what that warning is saying and it's ok to make a fresh install on the subdomain?
Thanks for your help.
Create a subdomain from cPanel (Which I think you've already done). While creating a subdomain, you'll be able to choose a directory (That also you might've already done).
Now you can go ahead and install WordPress on your subdomain, you don't need to worry! While installing WordPress, you can choose the directory, and obviously you'll choose a new directory.

How to restore a Wordpress into which another web app was installed

So I created a database in cPanel to install SMF into for my WordPress website, but I accidentally made my home URL the place to host the forums. It overwrote my entire website. I can't access any of the pages anymore without it redirecting me to my SMF forum. I deleted the database that the forum was connected to and it's just giving me an error now if I try to go to my website. Is there anyone that can point me in the right direction here?
I guess you'd have to try and restore the files on the top level, most importantly index.php and .htaccess.
When that is done, you'll have to hope that SMF didn't overwrite any important Wordpress directories. If it didn't, your install should work again.
index.php and any other files in the top directory you should be able to copy from a raw Wordpress install.
The only exception is the .htaccess file which contains the routes for pretty URLs (if you use those - if you don't, skip this paragraph). This file has been generated specially for your install. To re-create it, you should be able to access your wp-admin directory already, and update the permalink structure.

Categories