My first time coming to Centos Panel.
I started moving my websites from cyberpanel. However, bringing the old website's data over is difficult. Specifically I uploaded the SQL and the Plulic hml. Then I changed the DB_NAME, DB_PASSWORD, DB_HOST values but the website didn't work.
I see the old DB_HOST is localhost:3306 is there any problem?
I also tried a fresh install of Wordpress and the site works.
Related
So, I mucked things up pretty good. I've researched this topic, but none of the solutions I found work or quite fit my situation.
Let me explain. I had somehow managed to get a local install of WordPress using Xampp onto my Win10 PC. I remember it was a struggle then and that was a week ago. Problem is that I forgot my admin password and I couldn't figure out a way around it. So...
I did a database drop in phpmysql and recreated the wp table.
I copied the wp_config.php file into a safe place.
I deleted the wordpress folder in c:/xampp/htdocs.
I downloaded a fresh copy of WordPress and extracted it to c:/xampp/htdocs/wordpress.
I copied the old wp_config.php file into the newly re-created folder.
I ran WordPress install and got to the screen where it says it's installed and here's your user name.
I clicked on the link to the Login screen.
That's when I got the message -- Error establishing a database connection.
I'm not sure how that's possible considering it was just connected and created all the tables in the database.
Here's what's in my wp_config.php file, though I'm not sure what could be wrong with it since it was working fine a second ago (:{):
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'wp');
/** MySQL database username */
define('DB_USER', 'root');
/** MySQL database password */
define('DB_PASSWORD', '');
/** MySQL hostname */
define('DB_HOST', 'localhost');
I'm sure someone can tell me where I went wrong and hopefully how to fix it. I'm fine with starting over again. I just want to get it installed so I can learn the inner-workings. ;P
Thanks in advance. I look forward to learning from you all.
Jen
FYI, I ended up uninstalling Xampp and re-installing it in order to resolve this.
I made wp website on my testing domain. I would like now to move it to local mamp server.
I have tried using updraftplus plugin, but it didn't work (website is constantly refreshing, sort of being in a loop).
Now I want to move it manually. I have downloaded whole website through ftp and I also exported db.
I made new dbd with same name on my mamp server/phpadmin. In wp-cofig the database, username, password are the same as in my testing page. however local site can't connect to db that I have imported (I have used the same name for database on local machine).
I have read several instructions how to do this, but now I'm lost.
Any help is really appreciated.
Try this solution:link
Did you use the same table prefix as you used in previous one.
and Don't Forget to Change your previous base URL to new local URL in each and every place in your SQL file.
find wp_options in database and change site url and home url from your testing domain to localhost
i am looking into upgrading my magento community from 1.6.2 to 1.7.0.2.
First i will do this on my test server, but there are some errors during updating in magento connect, so i have to upload some files my self ...
but when i going to put these data into the live environment, can i just simply copy my data from the ftp to the live website?
Or are there also some new/changed settings in the database?
And if yes on the last question, which lines are changed?
I was able to successfully upgrade Magento from 1.6.1 to 1.7.using Connect Manager.
Here are the steps I had foung and followed
Go to yourdomain. com/magento/downloader/ (of course, make this
match your installation’s path.
Because I had installed Magento using tar.gz package provided with a skin I wanted to use, Magento Connect didn’t have all the
extensions listed for upgrading. I had to type
“connect20.magentocommerce.com/community/Mage_All_Latest” in the
“Install New Extensions / Paste extension key to install”
If you run into an error along the lines of “CONNECT ERROR: Package ‘Mage_All_Latest’ is invalid” repeated several times, once
for each package, it is because the files already exist, and you
have to remove a line of code in order for it to over-write data.
After everything has updated, you will probably have some errors. Make sure you clean the cache and session directories (delete
everything in /var/cache and /var/session)
If you receive a “500 Internal Server Error” it is more than likely because of file and folder permissions. It took .5 sec to
reset all of the permissions to what they needed to be.
If you receive a “Service Temporarily Unavailable The server is temporarily unable to service your request” error on a Magento
formatted header, it is probably because the store is set to offline
mode to prevent visitors from screwing up the installation process.
To fix this, delete the“maintenance.flag” file found in the root of
your magento installation directory.
Everything should be ready!
Avoid upload core library changes via ftp.
The fastest and more secure way is to patch your application using the diff files
patch -p0 -f < 1.6.2.0-1.7.0.0.diff
Then when you first visit your site Magento will automatically upgrade your db
best way to update is get a fresh mage zip 1.7.1 or whatever, and connect it to your current DB. When you go to index - the new install will update your DB to the latest MAge DB. This way you dont have to use connect etc. The mage zip has its own sql updates.
Make sure you put your current theme into the new install etc, and test it 1st on localhost etc.
I was given a dotnetnuke v4.9.5.5 database (sql-express about 300MB) and I am trying to get it up and running on a different server. I have tried:
Installing the 4.9 version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page...)
installing the 5.x version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page... again..)
All of which fail. I cannot find any support on this topic at all. What is the correct way to go about this?
EDIT: wrong info please close..
Here is a good blog on the topic HOW TO: Move a DotNetNuke installation .
The basics are:
Copy all the files and the database, the two are closely tied together.
Update the connection string in the web.config.
Update the portal alias' in the PortalAlias table.
If you don't have the rest of the site files, it may be very difficult. While the database will contain most of the site content, you may be missing some important pieces like skin files, module files, and content files.
So, the first thing you should do is see if you can get the files zipped up and sent to you. If so, it should be fairly easy to get the site up and running. You may have to update the ConnectionStrings in the web.config but otherwise it should run as it.
If you can't get the original files, you could try installing version 4.9.5 of DotNetNuke and replacing the supplied database with the database you were given. You'll need to post the error messages you get if it doesn't work out or consult someone with solid DotNetNuke experience.
I hosted one DotNetNUke Application to my production server, and locally it works perfectly. But, when browsing it redirects to the error page.
How do I set the default.aspx as my application default page? I am getting the error as below:
DotNetNuke Error
--------------------------------------------------------------------------------
Windows Vista
Return to Site
Can anyone can help me, please? Will be appreciated.
UPDATE:
Hi, I changed the Path in the PortalAlias table to the server url and default.aspx as the starting page, but it displays the error.aspx as default page.
Please help me resolve this problem..
So, the application works perfectly locally, but not when you put it on the server. Is that correct?
Make sure that your portal alias is valid. If the site is hosted at
http://www.mysite.com
then www.mysite.com needs to be listed in the PortalAlias table
If you open that table in SQL Mgmt Studio, you'll probably see an entry attaching the portal to your local DotNetNuke folder (ie. localhost). Just add a new entry that points to the same PortalID, but with the correct URL for your production server.
Assuming your DNN installation is at "mysite.com", if you navigate to
http://www.mysite.com/default.aspx
do you still get the error page? If so is any error listed?
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have to correct machine key and connection strings. This is my last resort something is really strange procedure.