Editing in forms crashes on second save in Edge

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.
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.
This thread is closed to new posts. You must sign in to post in the forums.
2/13/2019 3:54:18 AM
Gravatar
Total Posts 121

Editing in forms crashes on second save in Edge

Apologies if this is a duplicate, I thought I'd logged it before but now cannot see it.

On any mojo form like /Admin/ManageUsers.aspx?userid=n
in Edge

Make a change and save > OK > make another change and save > crash.

This is log:

2019-02-04 14:20:12,305 ERROR 82.69.xx.xxx - en-GB - /Admin/SiteSettings.aspx - mojoPortal.Web.Global -  Referrer(none) useragent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134
System.NullReferenceException: Object reference not set to an instance of an object.
   at mojoPortal.Web.SiteUtils.IsFishyPost(HttpRequest request)
   at mojoPortal.Web.AdminUI.SiteSettingsPage.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at mojoPortal.Web.mojoBasePage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The cause seems to be that the referrer is empty on the second update.

Interim solution: add this to user.config...

 <add key="CheckFishyReferer" value="false"/>

But is this a security risk? If so, I hope the check can be modified to detect this scenario and save successfully anyway.

 

You must sign in to post in the forums. This thread is closed to new posts.