I prefer 'Fossil' myself, having ticketing and a wiki and a single binary 
as your source control makes everything super easy. Plus, it's what the 
sqlite people use for their source control.

http://fossil-scm.org/index.html/doc/tip/www/index.wiki

That said, the problem at hand is that it's not filling in fields on a 
redirect. So either redirect changed, or the names of those fields on the 
reset password page changed.


On Monday, January 5, 2015 12:41:57 PM UTC-7, Dave S wrote:
>
>
>
> On Monday, January 5, 2015 8:49:34 AM UTC-8, Ramashish Gaurav wrote:
>>
>> Hi all,
>>
>> I have deployed my app on internet. At initial stage, every thing was 
>> working great. No bugs. When a user would register himself, a confirmation 
>> email would be successfully sent to the user's registered email id. Even 
>> the 'Lost Password' option was working correct. Now I made some changes in 
>> my app few days ago. I cannot remember at which places.
>>
>
> That sounds like you don't use source control to keep a record of your 
> previous versions (and of changes between versions).  If you don't, may I 
> recommend that you do?  One of the things a good source control tool does 
> is provide a way for you to narrow down *when *a bug was introduced, 
> which helps to narrow down *where* it was introduced.
>
> If you're not familiar with source control, aka version control, here's a 
> good introduction:
> <URL:http://ericsink.com/vcbe/>
>
> (I'm a Mercurial-type; somewhere between an advanced beginner and a power 
> user; I can also use SVN, because I have to at work.)
>
> /dps
>
>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to