Nacos console still have ServiceManagement when start service with FUNCTION_MODE config

[dlzht]

Describe the bug
When start server with 'startup.sh -m standalone -f config', and access 127.0.0.1:8848/nacos, nacos console still contain ServiceManagement. I am not sure if it is reasonable.

Expected behavior
Nacos console does not have ServiceManagement, just like this post described.

Desktop (please complete the following information):

• OS: Arch
• Version: nacos-server 1.4.1
• browser: Firefox 85.0

Additional context
log start.out:

• Nacos 1.4.1
• Running in stand alone mode, config function modules

[KomachiSion]

I'm not sure whether it show when only use one mode.
@chuntaojun @yanlinly, What's the behavior before?

[stale]

Thanks for your feedback and contribution. But the issue/pull request has not had recent activity more than 180 days. This issue/pull request will be closed if no further activity occurs 7 days later.
We may solve this issue in new version. So can you upgrade to newest version and retry?
If there are still issues or want to contribute again. Please create new issue or pull request again.

[grapeqin]

Nacos 2.0.3
Ubuntu18

When I start nacos with command 'bash bin/startup.sh -m standalone -f config' then the logs/start.out print

I try to verify naming service with ‘curl -X POST 'http://127.0.0.1:8848/nacos/v1/ns/instance?serviceName=nacos.naming.serviceName&ip=192.168.89.99&port=8080' ’ it return 'OK'

So I guess '-f' parameter is not effect，and the console also show naming service menu like this

is that any thing wrong？

waiting for your reply，

best regards ! Thanks.