#Admin-UI: Customers and Orders Information are not rendered

31 messages · Page 1 of 1 (latest)

noble hare
#

When i click on an order or a customer, i get forwarded to the route, but nothing is rendered:

package.json

    "@medusajs/admin": "^6.0.2",
    "@medusajs/cache-inmemory": "^1.8.0",
    "@medusajs/cache-redis": "^1.8.0",
    "@medusajs/event-bus-local": "^1.8.0",
    "@medusajs/event-bus-redis": "^1.8.0",
    "@medusajs/medusa": "^1.12.3",
    "@medusajs/medusa-cli": "^1.3.14",
    "babel-preset-medusa-package": "^1.1.13",
    "body-parser": "^1.19.0",
    "cors": "^2.8.5",
    "express": "^4.17.2",
    "medusa-file-cloudinary": "^1.0.1",
    "medusa-fulfillment-manual": "^1.1.37",
    "medusa-interfaces": "^1.3.7",
    "medusa-payment-manual": "^1.0.23",
    "medusa-payment-stripe": "^6.0.1",
    "typeorm": "^0.3.11"

oak tusk
#

Could you post a screenshot of the Console tab here as well, please

noble hare
#

hi @oak tusk
thank you for your time
sure

#

DOMException: Blocked a frame with origin "http://localhost:9000" from accessing a cross-origin frame.
that one is interesting for sure, since i do have that as an admin cors, but maybe it's not being loaded

#

okey fixed that one up, had to update my doppler env variables,

the orders and clients are still not showing

oak tusk
#

Interesting. Could I see the Network tab? We should be making a request to /admin/customers/:id when you click on one, wondering if that's firing off and what it's responding with

noble hare
#

@oak tusk sure
no request is being sent to /admin/customers/:id 🙂

#

same for orders

oak tusk
#

Odd indeed. It's 10PM now, but I'll have a think/look tomorrow 👍

oak tusk
#

Given that you're running [email protected], I'm guessing you don't have any customizations that could be breaking this?

#

Could I get you to try with our latest beta, yarn add @medusajs/admin@beta?

noble hare
#

ok i'm on @medusajs/admin@beta 🙂

#

Customers are being rendered and works now tho!

oak tusk
#

Interesting, so they do load on beta. They load for me on the version you were running as well, though, so I'm not sure 🤔

For that error, could I get you to yarn dev instead, and access admin at localhost:7001, so we get proper error messages

noble hare
#

btw not sure if relevant, but yarn dev throws a warning

warn:    An error occured while registering endpoints in your Medusa project
warn:    TypeError: app.use() requires a middleware function
noble hare
#

hehe i can't manage to change the port even after hardcoding it

oak tusk
#

No, you don't have to manually change the port. yarn dev will run the backend on :9000 still, but will run the admin react in dev, on :7001 instead of serving it as prod, as part of the main medusa server

noble hare
#

well that's not working either:

#

also, it seems like a bug to not be able to change the port :D?

oak tusk
#

If you want to change the medusa server port you can just set the PORT env variable

noble hare
pale socket
#

just add "dev:admin": "medusa-admin dev", script to you medusa-backend package.json. And then run the yarn dev:admin **or **eject the admin with "eject:admin": "medusa-admin eject -o admin-latest" and then go to the admin-latest folder in your medusa-backend folder, install the packages and then try yarn dev and check localhost:7001. I hope it helps.

oak tusk
#

Ended up pretty busy yesterday, sorry. Do not eject the new admin, that’s not something it supports anymore. But he’s right, you might be missing some scripts, forgot about that. The docs should have what you need for the admin beta, can link a bit later if needed, as I’m on my phone at the moment.

pale socket
oak tusk
#

The current beta, which marks the next major release, introducing extensions

proven pagoda
noble hare
#

@oak tusk i figured it out, i had to run the latest migrations