The idea is this: I have 2 dedicated servers (an old one and new one), I have to transfer a magento website from old server to new server via Plesk. Transferring is fine and the website works on a new server with a temporary domain (tempdomain.com) for testing purposes, however I do have this issue:
When I try to log on to admin area of a clone:
tempdomain.com/admin
I get redirected to
realdomain/admin
How do I log on to the cloned version (tempdomain.com)? I assume I have to edit some file, but I can't find which, since there are thousands, string searching through them is futile.
UPDATE: the new website has it's own (cloned) database
The table you are looking for is core_config_data. I am assuming the new tempdomain.com has its own database.
This link tells you what to do.
Related
This is for a client so I won't share exact domains but the problem is as follows..
I took over development of a website from a prior developer.
The hosting is Hostgator Business.
The primary domain is primary.com.
There is an addon domain addon.com.
The primary domain document root is /home1/username/public_html.
The addon's document root is /home1/username/addon.com.
www.addon.com had a WordPress installation which the developer had edited instead of using plugins to achieve his goals. The site also needed a complete redesign so I felt it logical to simply wipe the installation and replace it.
So, I deleted all of the WordPress files and uploaded a new copy of WordPress from wordpress.org/latest.tar.gz
Prior to deleting the old installation, the domain loaded files from it's document root perfectly.
After uploading the new installation instead of resolving to addon.com it is instead resolving to primary.com/addon.com
I've never seen this happen before so I'm lost.
There's no errors in any available logs.
All file permissions are correct.. I've triple-checked.
I've tried deleting all files and creating simple index.php and index.html files to see if it would access them ... it doesn't.
This happens in each browser I use on Windows and Linux.
I don't understand it because all I did was swap out the old WP install for a new one.
I went and re-uploaded the old WordPress installation so everything is 100% how it was but it is still going to primary.com/addon.com instead of addon.com.
Has anyone faced this issue before? I usually use Bluehost but even when I've used Hostgator in the past I've never seen this happen.
I double-checked the addon domain settings as well as anything else I could think of and everything appears normal.
I even deleted the addon domain and re-added it with the document root of /home1/username/addon.com and it still goes to primary.com/addon.com in the browser.
I submitted a ticket with Hostgator but they have not replied yet.
I'm sorry if this is long. This is my first time asking for help on here and I wanted to be sure I included everything I could.
Hostgator finally got back to me.
The previous developer had used the one-click WordPress install.
Apparently once someone uses a one-click install the only way it works is if you keep using the one-click install/you cannot do it manually any more.
From all the servers and sites I've setup this makes no sense and is a problem with Hostgator. Support did not really tell me anything other than "you have to use the one click install since the prior developer did". Great service.
Hope this saves someone some hassle.
From this it sounds like you were moving a WordPress site from the primary domain to an add on domain.
Simply moving the files from the primary to the add on domain will not make it work on the add on domain because in the database and throughout the coding of the WordPress site it would all be configured and coded for the primary domain.
It sounds like you would need to update the site home and site url from the primary to the add on domain url.
http://support.hostgator.com/articles/specialized-help/technical/wordpress/wordpress-home-fix
Also I would be suggest using a search and replace type plugin to go through all the internal coding to update the urls and links to the add on domain.
There is more information here as well http://codex.wordpress.org/Moving_WordPress
A policy change forced me to have to change our domain name for ckan, someone had a bright idea to use the domain name for a different landing site and then redirect off to the ckan sever from there.
I have updated data records in the database to reflect the amended url in the resource tables. (resource, resource_revision , resource_view)
it was https://www.blah.....
the new url is http://hub.blah......
Some resources re now downloadable at the new domain, the pages show the correct domain name and links and buttons work correctly.
Some resources on the page show the old url and link to the old url where there is no document accessible. The document is present at the new url. I can see the records for the resource in the database reflect the new url in the database.
The previewers of the dataset are all showing the data as I would expect on those that have the correct url but not working on the pages where the url is incorrect on the screen.
New uploads are showing correctly on pages and correctly in the database.
I have restarted solr, nginx, apache and a reboot of the web server and the database server.
It looks like the pages that are out of date are cached but I cant find a way to refresh them and force the several hundred pages to re-query the database to get the correct information.
I see the same issue when the page is accessed externally and internally to my corporate network.
Anyone any more ideas?
My best guess would be that the URLs are wrong in the solr index, try to rebuild the whole solr index with this paster command (run in virtualenv):
paster --plugin=ckan search-index rebuild -c production.ini
Adapt to your config file accordingly.
after a bit of a headache and a good nights sleep I added
the following to production.ini
ckan.datastore.sqlalchemy.pool_size=10
ckan.datastore.sqlalchemy.max_overflow=20
this worked for me
I am trying to transfer my website with jomsocial from one server to another.
www.iremember.gr
Previous server steps:
Backup all the files from public_html folder.
Backup the DB from php my admin.
New server steps:
Install joomla, entered the prefix in DB of the previous DB prefix.
Deleted all files from public html and extract the backup from the previous server.
Export the DB from the previous server, to the new one.
Changed the configuration.php file with the new user/dbname/password.
Now when i try to enter the new server at this IP address
93.174.121.23/~niremco/
and i login ok.
It loads the main page
but when i try to enter a profile i get a 404 Error.
Although when i try to see the profile
http://93.174.121.23/~niremco/index.php?option=com_community&view=profile&userid=109
i can see it.
But not from the correct link that i had in the previous server
http://93.174.121.23/~niremco/team-iremember/profile
Any idea why this happens?
You probably haven't copied the .htaccess file from the old website, you will need to copy it from the old Joomla website to the new one. This typically happens because the .htaccess file is considered to be a hidden file and as such does not get copied over automatically.
First of all, installing a clean Joomla first is totally unnecessary. As for why you are getting the 404 error pages, this is because you probably have URL rewrite enabled in global configuration, while there is not a proper .htaccess file sitting in your new server.
With proper I mean either no .htaccess at all, or one that was setup for your old hosting. I rather tend to think the second.
To test that your moved correctly your site, disable url rewrite from global configuration.
If you would want to test with url rewrites enabled, then I would suggest to edit the hosts file in your computer and point your domain to the ip address of the new server.
Google Search: How to edit my hosts file - choose the resource for your OS.
So I've gotten myself into a bit of a pickle and need assistance from StackOverflow Gods.
We're trying to transfer a Magento site from one server (Godaddy) to another (Private Virtual Server) for the purpose of becoming a test site.
I'm not familiar with Magento (my first mistake) but I researched migration, and I ran across an article that said all you need to transfer is the database, theme files, catalog files and skin files.
So that's just what we did. We setup a fresh install, added the files and the site (http://boulderfootandankle.com/apv-test/) looks like it's got some formatting errors. We figured we could fix those after adding the database.
As soon as we connected the database through the local.xml file, the theme changed to a generic one (I imagine a fallback) and we were locked out of the admin.
I tried a number of the solutions offered for this very problem, which included:
Clearing the var/cache and var/session folders.
Altering the core config data values for the unsecure and secure web base urls.
Deleting the unsecure and secure web base urls and cookie values form the database.
Changing the sessions save CDATA from "files" to "db"
Changing the install date to the original
Altering the varien file
...and nothing seems to work.
At this point, I'm just wondering if doing a fresh transfer of the site from one server to another, instead of transferring specific files into a fresh install, would work
Did you use the same encryption key as the previous installation? The encryption key is set in the local.xml file and needs to be the same on both extensions. When you did a fresh install it would have given you a new encryption key and this could be why you are unable to login.
just my quick list for transferring sites...
1. run files backup and mysql dump (from source)
2. Copy local.xml (from Target)
3. Restore backup and mysql dump (to Target)
4. Restore local.xml(from step 2 to Target)
5. Correct base_url (in Target)
The only time I have ever had a problem with this is when I run things locally for dev in that case there is varien specific check that monks with admin login(but, sounds like you know this).
https://magento.stackexchange.com/questions/26071/magento-1-9-can-t-login-to-admin-panel
I am on 1.14 and the posters suggestion essentially is the same fix I found. Of course the responder is totally correct on the horror of this solution but, since this is a test site as long as you leave yourself the right notes you should be able to undo this when you move to production.
So i have a client, who has a disc of an entire site. Root server files, all the way to /httphome/ files...
However, it looks like it was created using Joomla. Now, i know my HTMl and CSS but have never used a CMS like Joomla.
To get this site up and running, am i going to have to install Joomla on my clients server, and then upload the files?
i am going to assume its not that easy.... anyone got any insight into this process and what im looking at?
thanks
Keep in mind that Joomla content resides in a MySql database.
You need the following:
Database export
Create a DB on you MySQL server
Upload the files
Edit configuration.php to work with you db and also set your path there
Also, some components might need some more setup, as some of them have their own cfg files.
To get this site up and running (if the file is really the entire site) should be as simple as setting up a web server and pointing it to the directory with the index in it. Joomla should already be in that file. Let me know if i can elaborate on the process.
Since you are new to Joomla, you might want to try loading the disc contents up on your localhost first. Personally, when I'm trying something new, I hate for my first attempts to be somewhat public - I always feel a little safer if I do the first install someplace local where I'm the only person who can see it.
Best of luck with your project! If you run into any problems, or if you want to confirm that the site is definitely Joomla, let us know and we will get you sorted out.
Do you have the related database? The files that make up Joomla are useless without the database. You could install Joomla and upload your files over the top, but any database changes made by any installed extensions wouldn't be made to that install. You'd also be missing all of the actual site content without the database.
If you do have the database, then all you need to do is import the database in you your mySQL, then upload the files you have on the disc and edit configuration.php file with the new database user and password.