I used tinymce and I guess I was not paying attention and did absolute paths on the links and images. Kicking myself now. Is there a way to set tinymce to insert relative paths automatically for the future? That would be nice. N
Here's that source view you asked for:
<p><img src="/drupal-5.7/files/ResizedPhotos/Joule_triptych_0.jpg" alt="Ambient Device's Energy Joule is being marketed in New York" height="107" width="362" /></p>
<p>The above of programs are not an excuse for not buying energy efficient lighting, new windows, high efficiency air conditioners, heat pumps and appliances that have good Energy Star ratings.</p>
<p><b><br />
Home owners, small manufacturers, schools, high rise residential buildings, nursing homes,
hospitals, hotels and other commercial facilities may be eligible for these programs. If
your utility does not offer a program, then contact your <a
href="/drupal-5.7/http:/drupal-5.7/www.naruc.org/displaycommon.cfm?an=15">State Public
Utility Commission</a> and find out when they will offer it. Just be sure to mention the
words Demand Response, Advanced Metering or Smart Meters when you speak to your utility or
State Commission.</p>
I was hoping the new thread title would be something like
Problem with image paths and links after moving server
because that's what you've got, and may attract someone who knows how to solve it.
Yes, that source code is what I expected. Well, almost. Dunno about that second one!
This is one of my reasons for hating WYSIWYG.
Basically, they are incapable of handling relative links in a meaningful way and still working on preview. But there may be a cure through input filters which should be able to rewrite and remove this pain.
Short story, I do not know any good answer to this. sorry.
I don't think it's anything to do with pathauto.
Possibly some global search&replace is neccessary. possibly someones' already written it.
I saw this problem coming from a distance, so only develop in local subdomains or alternative http ports, not subfolders. That advice is a bit late for you, I know.
I am planing to move my entire web site from one testing server to a live web site on a new hosting server.
How am I able to move a Drupal 6.0 to the new Hosting and at the same time upgrade to Drupal 6.1 release?
As dman stated, you should test the website after upgrading it. You should break this up into two different tasks, upgrading Drupal and moving Drupal. Which order you do it in doesn't really matter. In both cases you should backup the database and site before performing the task and test the website after completing the task.
Before you move Drupal make sure you turn of clean urls and clear out both the cache and session tables.
I've read through all of these 'moving entire site + DB' threads, and I have a grasp on it, but have hit a snag. I am hosting on GoDaddy, and I have a few different websites under my account. Here is a summary:
GoDaddy wouldn't let allow me to have an identical DB name for the new site, so I named it database2. I'm wondering if this is what's causing me problems. I changed settings.php to match the new db settings and base URL - but are there any other places I need to change DB references?
I have successfully moved whole Drupal sites from a host to another before, but now I'm about to move a Drupal multi-site with 8 different websites (in the /sites/ folder) to a new host. All the sites have their own DBs. Is there anything specific I need to take into consideration while doing the move? ..Besides the fact that I have to create the subdomains again.
Comments
Old thread is
http://drupal.org/node/46389
Moving site developed on XAMPP is tough
This comment responds to the above issue at http://drupal.org/node/46389#comment-760623
I used tinymce and I guess I was not paying attention and did absolute paths on the links and images. Kicking myself now. Is there a way to set tinymce to insert relative paths automatically for the future? That would be nice. N
Here's that source view you asked for:
Note: clean url's are still turned off.
I have not looked at Pathauto yet in Mysql
I was hoping the new thread
I was hoping the new thread title would be something like
Problem with image paths and links after moving server
because that's what you've got, and may attract someone who knows how to solve it.
Yes, that source code is what I expected. Well, almost. Dunno about that second one!
This is one of my reasons for hating WYSIWYG.
Basically, they are incapable of handling relative links in a meaningful way and still working on preview. But there may be a cure through input filters which should be able to rewrite and remove this pain.
Short story, I do not know any good answer to this. sorry.
I don't think it's anything to do with pathauto.
Possibly some global search&replace is neccessary. possibly someones' already written it.
I saw this problem coming from a distance, so only develop in local subdomains or alternative http ports, not subfolders. That advice is a bit late for you, I know.
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
.dan. is the New Zealand Drupal Developer working on Government Web Standards
SQL
http://www.google.com/search?q=mysql+search+replace
Did you find the result in there?
Uh-huh..
So which one of those results you link to are you suggesting we can we copy to:
please do post that answer!
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
.dan. is the New Zealand Drupal Developer working on Government Web Standards
Moving site developed on XAMPP is tough
Sorry this was a duplicate
Moving and upgarde in one go
I am planing to move my entire web site from one testing server to a live web site on a new hosting server.
How am I able to move a Drupal 6.0 to the new Hosting and at the same time upgrade to Drupal 6.1 release?
Thanks
do not
Upgrade, test, then move.
Otherwise you'll never know what went wrong if you need to fix it.
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
.dan. is the New Zealand Drupal Developer working on Government Web Standards
As dman stated, you should
As dman stated, you should test the website after upgrading it. You should break this up into two different tasks, upgrading Drupal and moving Drupal. Which order you do it in doesn't really matter. In both cases you should backup the database and site before performing the task and test the website after completing the task.
Before you move Drupal make sure you turn of clean urls and clear out both the cache and session tables.
"Before you move Drupal make
"Before you move Drupal make sure you turn of clean urls and clear out both the cache and session tables."
How do I do this? please give the instruction, thanks
Moved entire site, but host made me change DB name
I've read through all of these 'moving entire site + DB' threads, and I have a grasp on it, but have hit a snag. I am hosting on GoDaddy, and I have a few different websites under my account. Here is a summary:
Old site: www.site1.com Old site DB: database
New site: www.site2.com New site DB: database2
GoDaddy wouldn't let allow me to have an identical DB name for the new site, so I named it database2. I'm wondering if this is what's causing me problems. I changed settings.php to match the new db settings and base URL - but are there any other places I need to change DB references?
FWIW I have DB backups set up on www.site1.com, and I simply restored the DB on www.site2.com using a backup of www.site1.com
Thanks everyone!
Moving a multi-site installtion
I have successfully moved whole Drupal sites from a host to another before, but now I'm about to move a Drupal multi-site with 8 different websites (in the /sites/ folder) to a new host. All the sites have their own DBs. Is there anything specific I need to take into consideration while doing the move? ..Besides the fact that I have to create the subdomains again.
Using Drupal 6.19
Thanks!