[Bug]: Diag-OFT not working in Forge

### Checklist

- [X] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Diag-OFT (network) doesn't work in Forge, but does work in Auto1111. Here is an example:

Forge:

Auto1111:

First 4 Images are Diag-OFT and last 2 Images are LoRA trained on same Concept. This is only been tested on XL and not on 1.5.
Other factors that might be related could be, that this is trained with XL tenc. This theory isn't tested yet.

### Steps to reproduce the problem

load a model, that was trained on Diag-OFT

### What should have happened?

Work same as Auto1111 Webui

### What browsers do you use to access the UI ?

Other

### Sysinfo

[sysinfo-2024-02-13-19-55.json](https://github.com/lllyasviel/stable-diffusion-webui-forge/files/14271653/sysinfo-2024-02-13-19-55.json)

### Console logs

```Shell
https://pastebin.com/RyGY2mCb
```

### Additional information

_No response_

Start by reproducing the issue with an XL model trained on Diag-OFT, using the linked sysinfo and console log as context, then compare the Forge result with Auto1111. Done means Diag-OFT produces the expected result in Forge; the issue does not identify a source file or test to begin with.

Written by the indexing model from the issue text.