Site Migration - Clean URLs broken
14 views
Skip to first unread message
Spud
Oct 27, 2008, 8:13:51 PM10/27/08
to Pixie
I first created my site in a directory under my web design site,
http://www.sitename.com/flyinlift/ and now moved it to http://www.flyinlift.org.
However, under the Admin page on "Settings - Site" I changed the Site
URL to the new url and now the "Clean URLS" do not work. When I turn
these off it works fine, however with Clean URLS on the links are all
broken. Any thoughts on this?
http://www.sitename.com/flyinlift/ and now moved it to http://www.flyinlift.org.
However, under the Admin page on "Settings - Site" I changed the Site
URL to the new url and now the "Clean URLS" do not work. When I turn
these off it works fine, however with Clean URLS on the links are all
broken. Any thoughts on this?
Gavin
Oct 27, 2008, 8:29:01 PM10/27/08
to Pixie
That's exactly the issue I am having.
On Oct 27, 8:13 pm, Spud <AndrewCGreg...@gmail.com> wrote:
> I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/and now moved it tohttp://www.flyinlift.org.
On Oct 27, 8:13 pm, Spud <AndrewCGreg...@gmail.com> wrote:
> I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/and now moved it tohttp://www.flyinlift.org.
Scott
Oct 28, 2008, 11:26:09 AM10/28/08
to Pixie
Hi All
I have not come across this yet, my suggestion would be to make sure
that the .htaccess file is present and you will also have to edit it
to reflect your new url.
If your site was originally install here: http://www.sitename.com/flyinlift/
then your .htaccess will look like this:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /flyinlift
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php?%{QUERY_STRING} [L]
</IfModule>
Once your site has been moved to: http://www.flyinlift.org,
the .htaccess will need to change to:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php?%{QUERY_STRING} [L]
</IfModule>
If this does not work, I would try and install Pixie again straight
onto the correct url and then migrate your database over to get your
content back.
Let me know how you get on
Scott
On Oct 28, 12:29 am, Gavin <failed...@gmail.com> wrote:
> That's exactly the issue I am having.
>
> On Oct 27, 8:13 pm, Spud <AndrewCGreg...@gmail.com> wrote:
>
> > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnow moved it tohttp://www.flyinlift.org.
I have not come across this yet, my suggestion would be to make sure
that the .htaccess file is present and you will also have to edit it
to reflect your new url.
If your site was originally install here: http://www.sitename.com/flyinlift/
then your .htaccess will look like this:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /flyinlift
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php?%{QUERY_STRING} [L]
</IfModule>
Once your site has been moved to: http://www.flyinlift.org,
the .htaccess will need to change to:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php?%{QUERY_STRING} [L]
</IfModule>
If this does not work, I would try and install Pixie again straight
onto the correct url and then migrate your database over to get your
content back.
Let me know how you get on
Scott
On Oct 28, 12:29 am, Gavin <failed...@gmail.com> wrote:
> That's exactly the issue I am having.
>
> On Oct 27, 8:13 pm, Spud <AndrewCGreg...@gmail.com> wrote:
>
Gavin
Oct 28, 2008, 12:33:00 PM10/28/08
to Pixie
I did modify the .htaccess file originally, it didn't help. When I
tried to run the installer on this new server, as soon as I hit 'next'
from the database information installer page, it gave me a 'database
unavailable' error. It might have something to do with the htaccess I
coppied from the current install, though, trying to enavle URL
rewriting in the new install. I'll try it without an htaccess.
> > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmoved it tohttp://www.flyinlift.org.
tried to run the installer on this new server, as soon as I hit 'next'
from the database information installer page, it gave me a 'database
unavailable' error. It might have something to do with the htaccess I
coppied from the current install, though, trying to enavle URL
rewriting in the new install. I'll try it without an htaccess.
Gavin
Oct 28, 2008, 6:10:26 PM10/28/08
to Pixie
Okay, I tried the install again without the htaccess - same problem.
This time I put in the wrong DB information first, and got the 'could
not connect to database' error on top of the form. When I put in the
right information, I got a blank page with this in the center:
------
Database Unavailable
Pixie has not been able to display the website your are visiting as a
database connection could not be established. Try to visit the site
again in a few moments.
------
It's like it doesn't know it's in the install process. Any idea what's
causing this one?
Thanks for your help so far, it's really appreciated.
> > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmoved it tohttp://www.flyinlift.org.
This time I put in the wrong DB information first, and got the 'could
not connect to database' error on top of the form. When I put in the
right information, I got a blank page with this in the center:
------
Database Unavailable
Pixie has not been able to display the website your are visiting as a
database connection could not be established. Try to visit the site
again in a few moments.
------
It's like it doesn't know it's in the install process. Any idea what's
causing this one?
Thanks for your help so far, it's really appreciated.
Scott
Oct 28, 2008, 6:40:55 PM10/28/08
to Pixie
Are you installing Pixie into the same database as before? If so that
is probably confusing Pixie. Could you create a new database (backup
the old one) and install into that? then using something like
PhpMyAdmin restore the original data from the backup you made?
If the .htaccess is correct and the URL in Pixie is correct I am
pretty certain the move should have been successful first time round.
The Database unavailable message means that Pixie cannot talk to the
database, this normally occurs if the database is down OR if your
details are incorrect in admin/config.php
Let me know how you get on
Scott
> > > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmovedit tohttp://www.flyinlift.org.
is probably confusing Pixie. Could you create a new database (backup
the old one) and install into that? then using something like
PhpMyAdmin restore the original data from the backup you made?
If the .htaccess is correct and the URL in Pixie is correct I am
pretty certain the move should have been successful first time round.
The Database unavailable message means that Pixie cannot talk to the
database, this normally occurs if the database is down OR if your
details are incorrect in admin/config.php
Let me know how you get on
Scott
Gavin
Oct 28, 2008, 6:43:51 PM10/28/08
to Pixie
I was installing to a fresh database. This is why I'm so confused, I
can't find any references to the location of the site other than the
site URL in the DB and the htaccess file. I am going to try removing
all pixie installs from the new server and starting again.
> > > > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmovedittohttp://www.flyinlift.org.
can't find any references to the location of the site other than the
site URL in the DB and the htaccess file. I am going to try removing
all pixie installs from the new server and starting again.
Scott
Oct 28, 2008, 6:49:52 PM10/28/08
to Pixie
Good idea (make sure your admin/config.php is an empty file too) !
best of luck
Scott
> > > > > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmovedittohttp://www.flyinlift....
best of luck
Scott
Gavin
Oct 28, 2008, 7:05:59 PM10/28/08
to Pixie
I'm completely unable to do a new install on this server. After the
first page, where you define your DB and DB user, it directs to /admin/
install/index.php where it gives me the previously displayed message -
and the DB information IS correct, the previous installs all connected
properly with it. I don't understand.
first page, where you define your DB and DB user, it directs to /admin/
install/index.php where it gives me the previously displayed message -
and the DB information IS correct, the previous installs all connected
properly with it. I don't understand.
Gavin
Oct 28, 2008, 7:18:05 PM10/28/08
to Pixie
Now I managed to get installed by building config.php manually. At
this point I can rebuild it, however there's still a problem. Paths
are still being written as I originally mentioned, with ./ in front of
them. Regardless of whether I'm in the root of the site or on a page, /
news/, paths are written preceded by ./ . I don't understand how that
would work.
this point I can rebuild it, however there's still a problem. Paths
are still being written as I originally mentioned, with ./ in front of
them. Regardless of whether I'm in the root of the site or on a page, /
news/, paths are written preceded by ./ . I don't understand how that
would work.
Spud
Oct 28, 2008, 9:37:21 PM10/28/08
to Pixie
Scott,
Thanks, this solved my problem completely. I didn't think to look in
that file for any changes.
- Andrew
> > > I first created my site in a directory under my web design site,http://www.sitename.com/flyinlift/andnowmoved it tohttp://www.flyinlift.org.
Thanks, this solved my problem completely. I didn't think to look in
that file for any changes.
- Andrew
Kathryn
Oct 30, 2008, 12:10:17 PM10/30/08
to Pixie
Hey Gavin,
Not sure if you are still struggling with this, but I'm glad you and
Scott have been posting about this as I myself just went through a
migration and had similar concerns/issues.
All of Scott's advice is valid. Creating a new database and doing a
clean install of pixie on your new server definitely helps (make sure
you export a copy of your old database, and to make my life easier, I
also saved copies of my modified theme, associated images, etc.).
After I reinstalled Pixie, I imported my database copy into my new
pixie database. I also encountered issues regarding references in my
menu navigation to the old URLs. I resolved this by using phpMyAdmin
to write in new information in the "(databasename)_settings"
directory, specifically changing the values for the "site_url" and the
"default_page" (*I had been getting error 404 messages when just
accessing my domain, and realized that was because the fresh install
populated the default_page with "blog/" - a page I do not have in my
database copy; I simply changed that to a page I do have, the one I
want users to see first when they hit my domain).
Hopefully my experience might help yours?
Cheers,
Kathryn
Not sure if you are still struggling with this, but I'm glad you and
Scott have been posting about this as I myself just went through a
migration and had similar concerns/issues.
All of Scott's advice is valid. Creating a new database and doing a
clean install of pixie on your new server definitely helps (make sure
you export a copy of your old database, and to make my life easier, I
also saved copies of my modified theme, associated images, etc.).
After I reinstalled Pixie, I imported my database copy into my new
pixie database. I also encountered issues regarding references in my
menu navigation to the old URLs. I resolved this by using phpMyAdmin
to write in new information in the "(databasename)_settings"
directory, specifically changing the values for the "site_url" and the
"default_page" (*I had been getting error 404 messages when just
accessing my domain, and realized that was because the fresh install
populated the default_page with "blog/" - a page I do not have in my
database copy; I simply changed that to a page I do have, the one I
want users to see first when they hit my domain).
Hopefully my experience might help yours?
Cheers,
Kathryn
Kathryn
Oct 30, 2008, 12:10:29 PM10/30/08
to Pixie
Hey Gavin,
Not sure if you are still struggling with this, but I'm glad you and
Scott have been posting about this as I myself just went through a
migration and had similar concerns/issues.
All of Scott's advice is valid. Creating a new database and doing a
clean install of pixie on your new server definitely helps (make sure
you export a copy of your old database, and to make my life easier, I
also saved copies of my modified theme, associated images, etc.).
After I reinstalled Pixie, I imported my database copy into my new
pixie database. I also encountered issues regarding references in my
menu navigation to the old URLs. I resolved this by using phpMyAdmin
to write in new information in the "(databasename)_settings"
directory, specifically changing the values for the "site_url" and the
"default_page" (*I had been getting error 404 messages when just
accessing my domain, and realized that was because the fresh install
populated the default_page with "blog/" - a page I do not have in my
database copy; I simply changed that to a page I do have, the one I
want users to see first when they hit my domain).
Hopefully my experience might help yours?
Cheers,
Kathryn
On Oct 28, 7:18 pm, Gavin <failed...@gmail.com> wrote:
Not sure if you are still struggling with this, but I'm glad you and
Scott have been posting about this as I myself just went through a
migration and had similar concerns/issues.
All of Scott's advice is valid. Creating a new database and doing a
clean install of pixie on your new server definitely helps (make sure
you export a copy of your old database, and to make my life easier, I
also saved copies of my modified theme, associated images, etc.).
After I reinstalled Pixie, I imported my database copy into my new
pixie database. I also encountered issues regarding references in my
menu navigation to the old URLs. I resolved this by using phpMyAdmin
to write in new information in the "(databasename)_settings"
directory, specifically changing the values for the "site_url" and the
"default_page" (*I had been getting error 404 messages when just
accessing my domain, and realized that was because the fresh install
populated the default_page with "blog/" - a page I do not have in my
database copy; I simply changed that to a page I do have, the one I
want users to see first when they hit my domain).
Hopefully my experience might help yours?
Cheers,
Kathryn
On Oct 28, 7:18 pm, Gavin <failed...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages