Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

Destry · 2005-10-02 10:26:14

I can install a new TxP site locally no problem, but when I try and transfer a copy of a live site to local, I can’t login to my local admin pages for that site (I can see the frontside no problem, so I know the transfer went reasonably well, except for the password problem).

Both database are 4.1 and my password was only 7 characters; hence, password character count should not have been the problem.
I have also tried all the change password techniques (even though I didn’t forget my password), but those don’t work either.

I just don’t get it, and trying to recreate everything from a fresh install is practically out of the question, nor should it be necessary.

Has anyone gone this direction (from live to local) with XAMPP, and if so, can you share what you did, any little detail that I might have missed.?

Thanks a ton.

Oh, I was thinking of trying this…

Clear tables from the local database.
Install a new package of textpattern (since that seems to work for sites I don’t try and transfer); then when I get to the step of creating the config.php file, I’ll use the same variables as they exist now.
Reimport all the old tables, overwriting the new (empty) ones with the same name, EXCEPT the users table (which theoretically will be holding the newly generated, and supposedly working, password).

See any problems with this?

Last edited by Destry (2005-10-02 10:28:35)

Sencer · 2005-10-02 10:40:21

Both database are 4.1 and my password was only 7 characters; hence, password character count should not have been the problem.

Actually that’s not necessarily the case. 4.1 has a compatibility setting for 4.0 type passwords. It is possible that one uses it and the other doesn’t. That would result in the same problem as using a 4.0 and a 4.1 database.

I have also tried all the change password techniques (even though I didn’t forget my password), but those don’t work either.

Have you tried independently with PASSWORD and with OLD_PASSWORD? Have you amde sure to NOT use uppercase letters?

The 3 step process seems a lot more work than necessary, because:

EXCEPT the users table (which theoretically will be holding the newly generated, and supposedly working, password).

why leave the passwords in place and export import everything around it, when you could just as easily copy the content of the password field in the user-table over from a working installation on the same server.
It will look something like: 43e9a4ab71370f5b – take that from the user-account that you can log-in with (from an installation on the same server) and paste it in for the user-account you can’t login to. The latter should now take the same password as the former.

Destry · 2005-10-03 11:17:30

Thanks for the comments, Sencer; I’ll check into them and report back.

Last edited by Destry (2005-10-03 12:57:06)

davidm · 2005-10-03 12:57:07

I have done this kind of stuff quite a bit, but from EasyPHP to TextDrive most of the time. Thanks Sencer for the infos, so far I always hacked my way around like a p%g (last time upgrading a site from 1.19gamma to 4.01 while moving from one Host to another… duh), it might help I’ll try that too. This could prove useful for TextBook too :-)

Destry · 2005-10-03 12:57:17

Sencer wrote: why leave the passwords in place and export import everything around it, when you could just as easily copy the content of the password field in the user-table over from a working installation on the same server.

Excellent point! And it worked like a charm. (DB’s were indeed both 4.1, and all caps were not the issue.)

Just one more thing…I have one little blip in the diagnostics, <strike>which might have to do with why a couple of images I have uploaded are not showing up where they are supposed to</strike> (see Edit2 note at bottom).

<pre>Textpattern version: 4.0.1 (r888)
last_update: 2005-09-10 17:45:45/2005-09-10 18:44:15
Document root: C:/_txp/colloquialtongue (C:\_txp\colloquialtongue)
$path_to_site: C:\_txp\colloquialtongue
Textpattern path: c:\_txp\colloquialtongue\textpattern
Permanent link mode: section_title
upload_tmp_dir: .;c:\apachefriends\xampp\tmp
Temp folder: C:\_txp\colloquialtongue\textpattern\tmp
Site URL: colloquialtongue.com
PHP version: 5.0.4
Register globals: 1
Magic quotes: 1/0
MySQL: 4.1.12
Locale: en_US.UTF-8
Server: Apache/2.0.54 (Win32) mod_ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4
Apache version: Apache/2.0.54 (Win32) mod_ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4

Pre-flight check:
————————————
File Upload Path is not writable: /var/tmp
————————————</pre>

Notes:

.htaccess contents are default
local virtual host container is local.colloquialtongue.com, but Site URL in admin prefs is set as colloquialtongue.com

I think this is perhaps a permissions issue on the respective <code>tmp</code> folder, but I can’t seem to undo the “Read-only” aspect of this folder, whether using and FTP client or directly using file manager; when I undo read-only and save, it immediately reverts back to read-only. The diagnostics above indicate two tmp folders…

<pre>upload_tmp_dir: .;c:\apachefriends\xampp\tmp
Temp folder: C:\_txp\colloquialtongue\textpattern\tmp</pre>

…but I can’t change the read-only value in either case. How to handle that diagnostic?

EDIT: Oh, one observation I had when copy/paste-ing the good password from a different local install to the users table of the install in focus: both of the actual passwords were exactly the same, but the one in the screwy install (the I couldn’t log into) had a hash that was twice as long and began with an asterisk (*). Don’t know if that means anything, but there it is. When I changed it, as indicated above, all was good with my tea.

EDIT2: Well simply moving the images to the local images folder solved that problem, but I’m still wondering if I would be able to upload any images or files in the local install because of the diagnostic problem that still exists. (When I’m ready with an image, I’ll try uploading it locally and see what happens.)

Last edited by Destry (2005-10-03 13:47:17)

Destry · 2005-10-03 13:00:40

davidm wrote: This could prove useful for TextBook too :-)

Oh yeah, it’s going in there, as soon as I iron-out the kinks. ;)

davidm · 2005-10-03 14:58:58

That’s cool :-) For my part, I might document how to go up from 1.19gamma to 4.01 after asking if anyone had similar experience to share (to write something more “generic”)

Destry · 2005-10-17 07:21:02

As promised (er…something), I’ve written up the process and will be transcribing a more generic version (if possible) to TextBook at Moving Installation from Remote (Live) Server to Localhost. Or you can see the full article here.

I still have that little diagnostic issue (see post #5 above); can’t seem to change permissions on the tmp folder (either one) no matter what I try. Any ideas what’s going on there?

Textpattern CMS

Textpattern CMS support forum

#1 2005-10-02 10:26:14

Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#2 2005-10-02 10:40:21

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#3 2005-10-03 11:17:30

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#4 2005-10-03 12:57:07

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#5 2005-10-03 12:57:17

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#6 2005-10-03 13:00:40

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#7 2005-10-03 14:58:58

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

#8 2005-10-17 07:21:02

Re: Attn XAMPP Users: Transferred a TxP site to local w/o psswd problems?

Board footer