Error 200 on create and edit Media Sources

Support
1

Summary

I get an error 200 when I try to create or edit a MediaSource. I notice that the dropdown for Source Type is displaying a path (MODX\Revolution\Sources\modFileMediaSource).

The media sources do work and function as planned. So what ever the error is, it is not preventing correct functionality

Step to reproduce

Editing or creating a media source triggers the error

Observed behavior

Displays error 200 error dialog but Media Sources do function correctly

Environment

MODX 3.0.3 on a shared hosting environment. Installed using Softaculous. I think (not 100% sure) the original install was 3.0.2 and then upgraded to 3.0.3 using Softaculous. Since 200 errors are typically permission issues, I checked to see if the user is a sudo super admin (yes). The user has 187 permissions (I have not worked with ACLs in Modx3.x, only 2.8.x), so I am not sure if any permissions were added in 3.0.3 and I need to set them.

2

Aren’t 200 status codes only for successful responses?

3

I have see this error 200 dialog in modx in 2.8.x when I have errors in the ACL/permissions for users. Have never seen the error when creating Media Sources in other installs of MODX 3.x.

Also the incorrect display of Source type, makes me think it might be another issue.

Roy

4

This is not a path, it’s the class with the namespace.

So is there any error message?

5

Here is a screen capture:

error-200-media-sources
error-200-media-sources2078×1406 178 KB

6

Open the developer tools of your browser and go to the “Network” tab.

When you edit a MediaSource, it should create an AJAX-request with the action “Source/Type/GetList” to get the values for the “Source Type” dropdown. What is the response of this request?

7

I hope this is the info you are looking for

Here is the error in the Dev Tools:

network-1
network-12778×1054 162 KB

The header info is a follows:

URL: https://historichomesofstillwater.com/connectors/index.php
Status: 200 OK
Source: Network
Address: 184.154.46.199:443
Initiator: 
ext-base.js:21:18813


Request
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Language: en-US,en;q=0.9
Accept-Encoding: gzip, deflate, br
Host: historichomesofstillwater.com
Origin: https://historichomesofstillwater.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15
Referer: https://historichomesofstillwater.com/manager/?a=source/update&id=3
Content-Length: 151
Connection: keep-alive
Cookie: PHPSESSID=fd39fd27ee7030ec82b617c34f05da4a
X-Requested-With: XMLHttpRequest
Priority: u=3, i
modAuth: modx6402b75e80f219.81811988_164176468033ad5.64980522

Response
Pragma: no-cache
Set-Cookie: PHPSESSID=fd39fd27ee7030ec82b617c34f05da4a; path=/; HttpOnly; secure
Content-Type: text/html; charset=UTF-8
Date: Mon, 20 Mar 2023 19:33:09 GMT
Content-Length: 0
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Server: LiteSpeed

Request Data
MIME Type: application/x-www-form-urlencoded; charset=UTF-8
class: MODX\Revolution\Sources\modFileMediaSource
action: Source/Type/GetList
HTTP_MODAUTH: modx6402b75e80f219.81811988_164176468033ad5.64980522
type or paste code here

Thanks
Roy

8

This is weird. The response should be JSON and contain the available options for the dropdown.

When you try to edit a MediaSource, does anything get added to the MODX error log?
Do you have an extra installed, that adds a custom media source (and is maybe not compatible with MODX 3)?