Hi All We were not able to reproduce this issue on any of our machines during pre-release testing for v4.28. Then after some R&D, we are able to reproduce this issue.
*Cause of the problem*: if value of "*HKEY_CLASSES_ROOT\.js\Content Type*" is set to "text/plain" then issue is reproducible. In any javascript file, the content type should be “text/javascript” in the response header but in the above registry setting it is "text/plain", so the browser won't allow it. *Solution: *Open the registry and changed the value of "*HKEY_CLASSES_ROOT\.js\Content Type*" to "text/javascript". Please let us know the above solution works for you all. On Fri, Nov 13, 2020 at 9:54 AM Akshay Joshi <akshay.jo...@enterprisedb.com> wrote: > Hi All > > We are working on the fix and will try to fix it asap. Once we fix the > issue will release the pgAdmin 4. > > Sorry for the inconvenience. > > On Fri, Nov 13, 2020 at 12:05 AM tito.calleros <tito.calle...@gmail.com> > wrote: > >> I have the same problem, I just upgrade from v4.27 to v4.28. >> >> Refused to execute script from >> 'http://127.0.0.1:57313/static/vendor/require/require.min.js?ver=42800' >> because its MIME type ('text/plain') is not executable, and strict MIME >> type >> checking is enabled. >> >> (index):39 Uncaught ReferenceError: require is not defined at (index):39 >> >> >> >> -- >> Sent from: >> https://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html >> >> >> > > -- > *Thanks & Regards* > *Akshay Joshi* > *pgAdmin Hacker | Principal Software Architect* > *EDB Postgres <http://edbpostgres.com>* > > *Mobile: +91 976-788-8246* > -- *Thanks & Regards* *Akshay Joshi* *pgAdmin Hacker | Principal Software Architect* *EDB Postgres <http://edbpostgres.com>* *Mobile: +91 976-788-8246*