Sorry, I had to take a break from this for a few days.
I don't use phpmyadmin, but i can check the users table.
I think for some reason it's not clear when I say I am running a dev site, the ONLY imported thing is the db, period. And yes, I downloaded the db. I can gzip it to make sure to trigger the binary transfer mode in the ftp client I guess, but last time I did this, it was a gz file for the sql.
I'll give this another try, however, I can't do all the steps of the move site procedure because all I am doing is importing the db, but i can retest that.
As for the sites being exactly the same, re php/mysql etc, give that some thought, what if someone has to move their site? Ummm... problem, no? Big problem, the only server with the exact configuration will be the server the site is on in almost all cases.
Let me check these things:
the login user the site claims does not exist is present in the db table modx_users, as of course it has to be since I imported the directly via mysql.
However, I am noting that the rest of the site is also blank, so I'm going to try some other procedures I've learned from the past failures.
The problem is not in resetting the password, it's there in the db, hashed.
However, I will again expand the upgrade cheat sheet I've made, and see if there is a step that is required, but given that if we ever had to move the site to a new server this stuff could bite us again, it's not frankly a risk I want to take.
On the plus side, had to do some updates etc today on the live site, and again, I am saddened by the fact that modx met our needs so well on the feature level, it's really almost ideal, if not totally ideal, and I kind of doubt any of the other cms will meet these requirements as well, since I had picked modx from the start to meet them over the others out there. Love the templating, the chunks, the snippets, the friendly url handling, the ease of creating stuff for the site without changing a character of the core programming, so many pluses with modx, but this update / portability issue has been an issue for me ever since I first installed and ran evolution, in fact, I now approach each update/upgrade with terror, and that just isn't going to work.
So I know that portability of the software is now a core requirement for a cms, annoying but there it is. But I am an optimist, and will continue to see if I can beat this issue back somehow or other, by either trying again things that have not worked in the past, or trying things that might work now, always a gamble though.
On the bright side, I totally redid the man page for my favorite project, and did a lot of other changes which people seemed to like, so I guess I can dip back into the more frustrating part of the world again for a bit.
thanks for taking a look though.
It may be possible that one simply cannot just import the db, odd as that seems to me, but I can admit I am beaten. But for dev purposes, I have to be able to run the site on my local server, and it's not practical to maintain the exact lamp or fbamp setup for each and every web site I do, never needed it ever before, that's a bit too much for me, to bill clients for that type of thing I'd have to increase my hourly rates by about 50% or so to justify the time.
But let's see if something really obvious shows, the only way I can really face these issues is by believing there is a solution.
Client has already agreed to move on from modx but I think he's not aware of the large cost involved in such a move, and I do actually like it, when it doesn't do something like not work or not upgrade or whatever
☆ A M B ☆
