Files Interface in CMS fails to load, Internal Server Error

[jenniferaslan]

Steps to reproduce the issue in an SS4 site:

1. Add a has_one Image::class to Page.php

2. Add an UploadField for that Image to getCMSFields

3. Using Firefox, log into the CMS and go to a Page page

4. Right-click anywhere and choose Inspect Element from the contextual menu

5. In the Developer Tools window, choose the Network tab (it may help to pop this out into its own window)

6. In the CMS, view the interface in Split mode

7. Attach an image using the UploadField

8. Save the page

9. Click the UploadField to see the interface for choosing an image and see that the selected image is shown in the right-hand side of the dialog
   

10. Close the dialog

11. Refresh the page

12. Click the UploadField to see the interface for choosing an image and see that this time the right-hand side of the dialog is empty except for a message about internal server error.
    

13. Look over at the Network tab in the Developer Tools window to see the error 500 that just happened
    
    500error.txt

14. Close the dialog for choosing an image

15. Click the Files button in the far left column of the CMS

16. Notice that the right side of the interface fails to load
    

17. Look at the Network tab of the Developer Tools window to see that the last item that loaded is “types” and the final two items that usually appear after “types” failed to load.
    Normal Loading:
    
    Incomplete Loading:
    

18. Log out of the CMS and log back in and it will all work okay until you happen to refresh the page with the Split view open.

I don’t think this happens if you work only in Edit mode. I think this has something to do with ?stage=Stage.

composershow.txt

[jenniferaslan]

I have received feedback from a client that she doesn’t use the split view because she thinks it’s buggy, but she still experiences the problem described in this issue.

[mlewis-everley]

I just did a test on a sandbox install I have and wasn't able to replicate the issue at all. What version of SS4 are you using? Also, what modules do you have installed?

[jenniferaslan]

My composer show results are attached at the bottom of this issue. I have SS 4.2 installed on this site. We are going to test on a simple SS4 install that doesn't have certain modules installed on it to see if this still happens to us.

[mlewis-everley]

You have got quite a few modules installed, my first guess would be something to do with that.

Have you tried making sure everything is up to date? Might be a version issue.

[micahsheets]

I have narrowed the issue down to using SilverStripe\Versioned\Versioned: use_session: true in the yml config. If that setting is there this error is reproduce able. If it is removed, it does not happen. I do not know of the side affects of not having use_session: true.

[kinglozzer]

If Versioned.use_session is the cause, then perhaps this issue is another symptom of silverstripe/silverstripe-admin#607?

[chillu]

Yeah this might be fixed by silverstripe/silverstripe-asset-admin#824?

[bergice]

Confirmed that this is fixed by silverstripe/silverstripe-asset-admin#824

Will review again as soon as that has been merged and closed.

[bergice]

Resolved with silverstripe/silverstripe-versioned#173