search

PGBI / kong-dashboard

Dashboard for managing Kong gateway
MIT License
2.17k stars 390 forks source link

not working #214

Closed leetomlee123 closed 4 years ago

leetomlee123 commented 5 years ago

Issue summary

Briefly describe the issue you are experiencing (or the feature you want to see added). Tell us what you were trying to do and what happened instead.

Remember, an issue is not the place to ask questions. You can use Stack Overflow for that.

Your environment

Issue description

image

Current behavior

Tell us what happens. any action not working, i`m use docker

Expected behavior

Tell us what should happen instead.

Steps to reproduce

Tell us how to reproduce this issue.

Good to have

Any screenshots? Browsers' logs?

spiroo commented 5 years ago

me too! image

CHOMNANP commented 5 years ago

I'm having the same issue :D

huangtao1 commented 5 years ago

I'm having the same issue...

YixuanZeng commented 5 years ago

I'm having the same issue...

KylinHe commented 5 years ago

I'm having the same issue... ovo~

espider commented 5 years ago

I'm having the same issue

jlcoding commented 5 years ago

I'm having the same issue

akjamie commented 5 years ago

having same issue

yuleiqq commented 5 years ago

having same issue

davidback0420 commented 5 years ago

스크린샷 2019-06-16 오전 10 33 53

I'm having the same issue.

TreeZhiyuan commented 5 years ago

Does this project no longer maintained？

towardsyoung commented 5 years ago

Having same issue 1 years ago...

ygm521 commented 5 years ago

Having same issue 1 years ago...

guohailong2006 commented 5 years ago

哈哈哈哈，需要一个前端来fixed掉它

m344739968 commented 5 years ago
WechatIMG88

why?

yifengjin commented 5 years ago

Having same issue

hugbe8 commented 5 years ago

having same issue

2030405043 commented 5 years ago

Having same issue

kuoshijia commented 4 years ago

Having same issue

unil19 commented 4 years ago

there is some config missed for kong-schemas.js image

you can either fill up your config for your version such as 1.1, 1.2, 1.3 or make the 1.0 config used by default when your kong version is above 1.0; I solve the problems with the latter way by change the getter like this; var Schema = { get: function(version) { var major = semver.major(version); var minor = major==0?semver.minor(version):0; return schemas[major + '.' + minor]; } };

illyaMs commented 4 years ago

@unil19 yeah, seems like a bad version check in schema helper (I must confess my hands are dirty here 😄).

Should be OK to use your second solution, since kong has a stable (1.x) version and (hopefully) those guys do respect semver.

Could you please create a MR, so the owner of the repo may merge it and publish? Seems like the issue is quite popular, so that'll be a great contribution.

linuxdevopscn commented 4 years ago

Having same issue

illyaMs commented 4 years ago

There's a fix done by @yaohx submitted in #220 Some tests did not pass, but I guess it won't be a big deal to fix them if needed. We're using this forked version in our company currently: https://github.com/yaohx/kong-dashboard/commit/369b5df5969cbbbe582a3d2bed126f8e69b9df95

One more note is that the option provided above by @unil19 seems to be more elegant, imho (so maybe this could also be sent as a PR).

Whatever option is preffered, I think we need @PGBI to intervene as he's the maintainer (and thus the only person that can merge these fixes to upstream and release/tag an updated docker image).