Login module button not running in 2.9.1 if in home page -

Login module button not running in 2.9.1 if in home page

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

What operating system were you running when the bug appeared?
What database platform is your site using?
What version of mojoPortal are you running?
What version of .NET do you use?
What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You must sign in to post in the forums.

5/21/2025 3:07:08 PM

massimiliano

Total Posts 152

View Posts

Login module button not running in 2.9.1 if in home page

in the latest release (2.9.1) I noticed that a login form is on the home page (www.mydomain/website/) does not work by pressing the login button.
while it works regularly if in a page (www.mydomain/website/default.aspx)
this is not good because when you arrive on the site you are always in www.mydomain/website
how can I solve it? in the previous version it works correctly instead

6/3/2025 12:40:15 PM

massimiliano

Total Posts 152

View Posts

Re: Login module button not running in 2.9.1 if in home page

I also did some tests on the mojo demo site and I actually saw that I get the same result. the login button to the site does not work if we are in (example www.mydomain.com) while it works if we are in (example www.mydomain.com/default.aspx)

any ideas ??

8/1/2025 4:46:38 PM

Joe Davis

Total Posts 2263

View Posts

Re: Login module button not running in 2.9.1 if in home page

Hi Massi,

We found what is causing this and we have fixed it in the repo.

You can work around the issue by changing a property value in the web.config. Find <modules runAllManagedModulesForAllRequests="true"> at or near line 1018 of the web.config. Change the "true" to "false" and save the web.config.

Thank you,
Joe

8/13/2025 10:37:33 AM

Joe Davis