Wordpress not recognizing SQL database - sql

I used a third party for hosting and before I knew what I was doing, I created an entire WordPress website (via the host's WP panel) before getting my domain name. I now have my domain and I’m trying to get all the pages/etc transferred over to that domain’s WP. But the new WP Admin panel is not showing any of the old content.
What I’ve done so far:
Uploaded all the files (wp_admin, wp_content, wp_includes) to the new domain folder
Updated the wp_config file to reflect the new address
Exported the original SQL file and went through and changed all instances of my old domain to my new one
Uploaded the new SQL file via FTP
I don’t know what else to do :( no matter what, I can never get the files/pages/ anything to show on the new WP admin panel.

Related

Wordpress Database & WP Migrate

I built a WordPress website in localhost MAMP. Upon completing the site, I wanted to upload it to the actual hosting site using FTP. I uploaded all the content but DB. I used a WordPress plugin called 'WP Migrate' to export the database. Then I uploaded exported file to phpMyAdmin.
But the site did not work after uploading onto my site using FTP. I then begin to work again locally, using my local host. There is a feature to find & replace DB values in 'WP Migrate'. I replaced existing local site name with actual web site name. This stopped working my local website also.
I am not trying to figure the live site, but figure the local host site right now, that way I can perform a transfer. I believe it has to do with the DB somehow but not sure where or how to edit it.
Basically it is the same issue that this person is having as well, but the question wasn't answered: https://wordpress.org/support/topic/undo-find-replace/
Nathan Rojas
If it's after you updated your site name, you can easily change it back by logging into the myPhpAdmin of your local site and choosing the MySQL database you are using. under the wp_options table, you'll see a field called siteurl and home. Update those fields to what you had prior and it'll come back. ;)

DNN legacy migration yields "object reference not set to an instance of an object"

This question has been asked before and I've spent two days chewing through it all, to no avail. I've worked in and around DNN since the very early days (anyone remember the IBuySpy portal from 20 years ago?), and I've migrated more than a dozen sites, all without issue. But in this case, I'm getting the old "object reference not set to..." The EventLog indicates an error in InitializePage but not much more to go on. The logs in the DNN _default folder are for some reason not populating; will check this.
The specifics: DNN 5.03.01 site, has worked fine for a client for years. Needs to be moved to a new server. Different domain name for testing, then we'll redirect the live domain name. Site has a default portal at Portals/0 (no longer used); client's portal is at Portals/1. DB is on same box, MS SQL Server.
What I did: created a Portal Alias in the old, live site to reflect the "test" domain name. Copied all file system content. Duped schema to new DB (same version of MS SQL Server), used Schema Compare to make sure it worked, added all data, used Data Compare to make sure it was all there. Logged into new DB using SMSS; works fine. On the new/test DB, disabled all entries in the WebServers table. Verified new portal alias exists, referencing Portals/1. Verified domain name is live with correct new IP. Set up new site on IIS using that IP, referencing Portals/1. Edited connectionstrings and appsettings entries in Web.config, using the credentials that worked with SMSS. Ran the new site by entering the new/test domain name. I also set the permissions broadly on the DNN folder.
Got: [new domain name]/Default.aspx?error=Object+reference+not+set+to+an+instance+of+an+object.&content=0
So I'm getting to the DNN folder on the new server, but it seems something's not right with PortalSettings (guessing here). Maybe it's going to Portal 0 (the defunct one). This shouldn't happen if I create the new PortalAlias before migrating.
Possible complicating factor: The new server contains another complete instance of DNN which handles the live version (a copy) of the Portals/0 portal on the old machine.
Anybody have any thoughts? Something I overlooked? How can I make absolutely certain I'm hitting the database?
In the older versions of DNN there was a PortalSetting value for DefaultPortalAlias. If that was set to something different it is possible you could see similar behavior.
Also, that version of DNN does not log entries to the /portals/_default/logs directory

Prestashop migration procedure

I have a client who wants to move their hosting provider and we have successfully cloned exact copy of original server to the new hosting provider's server. We want to use different domain name staging.copiedsite.com to creating staging environment to check everything works fine, then we want to flicker it back to original DNS (www.actualsite.com). My question is, how do you configure the site to work with staging domain name? I am going to basically find all database record that says "www.actualsite.com" and replace it with "staging.copiedsite.com". Is that all it needs? Is there any configuration text file that I need to edit? Thanks.
You shall change the domain in BackOffice > Preferences > SEO & URLs. This will update configuration in database and your .htaccess file (For some obscure reason you might have to save this page two times so that the .htaccess file is overwritten).
Also some CMS pages and modules can use absolute URLs so changing all those values by querying the database is a good idea.
Basically that's all you need.

Redirect forum address phpBB3

I've created a forum using phpBB3,
The address I got is : http://<FORUM NAME>.com/phpBB3
I would like to change it to http://<FORUM NAME>.com (without the phpBB3)
Is it possible to create another forum addressed to the second URL I mentioned, that uses the same SQL database as the first forum?
The /phpbb3 part of the URL refers to the directory on the server that your forum is installed in. If you move all of the folders and files out of the phpbb3 directory into your websites root directory (usually either htdocs or public_html) then the URL will then become http://<FORUM NAME>.com This is best done via FTP and not your hosts file manager to help prevent corruption of any files.
Only do this if you don't already have pages at http://<FORUM_NAME>.com otherwise you will overwrite anything already there that share any file names.
If you do move everything, once finished log into your phpBB admin control panel and under 'Server configuration -> Server settings' make sure 'Force server URL settings' is set to 'No' and all the internal links on your board will adapt themselves to the new URL.
IMPORTANT! Before you do ANYTHING make sure you download a backup of the files and the database, then if anything goes wrong you can easily put things back again.

After moving my Drupal 7 site to another host, modules are appeared without download

I'm sorry for such a complex subject. My problem is.
I tried to move my Drupal 7 site from one server to another.
I uploaded a fresh install to my new site.
I backed up my old database and imported to my new site.
I uploaded settings.php file to my new site.
When i entered to my new site's module part, All the 3rd party modules i installed in my old site, exist in my new site without any loss :)
But when i check the folders
/sites/all/modules
/sites/default
/modules
I couldn't find any file regarding to this modules.
Modules exist in my new site when i check my admin panel, I can create content by using this modules, But i can't see their files by using file manager etc.
Thank you
Because you didn't disable the modules before moving your deployment, I think they're still marked in your database, same for registration of content types. As the modules don't actually exist, you won't get their functionality.
Replacing the modules under /sites/all/modules or /sites/default/modules should leave them working as before.