Hi Thanh,

The signin module is a legacy module, it is not intended for current use, I just haven't removed it yet but I plan to remove it. It was replaced by the login page.

Joe

Hi Thanh,

I would suggest first to rename it so you don't lose it if you update from svn after I remove it.

To make it work you would need to look at the logic in the login page and make it the same in the signin module.

One thing to be aware of though is later if you ever upgrade to the 2.x branch of mojoportal, the login logic has changed completely to use the new membership api so any work you do in your custom signin module will have to be re-done at that point.

Originally the signin control was in the skin and displayed on every page if the user was not logged in.

One of the reasons I decided to use a login page instead of the signin control is because I can easily force ssl on the login page without requiring ssl on other pages. If you put the signin module on multiple pages it won't be very secure unless every page you put it on requires ssl

Hope it helps,

Joe

Yes it might work but I recommend you don't do that.

As I said before I recommend you copy the logic into the signin control instead and rename it to be your own custom module.

If you change things that are part of the core of mojoportal you won't be able to update to future versions very easily.

Joe