starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #2129] [bug]: Editing environment no longer possible #715

New issue

Closed

opened 2026-03-16 16:50:39 +03:00 by kerem · 9 comments

kerem commented

2026-03-16 16:50:39 +03:00

Owner

Originally created by @lapo-luchini on GitHub (Feb 24, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2129

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Clicking on "edit environment" opens a dialog no longer.

Steps to reproduce

Environment

Production

Version

Cloud

Originally created by @lapo-luchini on GitHub (Feb 24, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2129 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior Clicking on "edit environment" opens a dialog no longer. ### Steps to reproduce ![image](https://user-images.githubusercontent.com/420454/155484225-db26aa78-1c3d-4495-8882-e54eece95306.png) ### Environment Production ### Version Cloud

kerem

2026-03-16 16:50:39 +03:00

closed this issue
added the
bug

resolved
labels

kerem commented

2026-03-16 16:50:55 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 24, 2022):

Hi @lapo-luchini, can you check if there are any errors on the browser's console? Press F12 to open console logs.

Also what happens when you click on the environment name? It's supposed to bring up the edit environment window. I can't seem to reproduce the issue at my end, would be helpful to see a screen record of bug reproduction with browser's console logs.

@liyasthomas commented on GitHub (Feb 24, 2022): Hi @lapo-luchini, can you check if there are any errors on the browser's console? Press <kbd>F12</kbd> to open console logs. Also what happens when you click on the environment name? It's supposed to bring up the edit environment window. I can't seem to reproduce the issue at my end, would be helpful to see a screen record of bug reproduction with browser's console logs.

kerem commented

2026-03-16 16:51:00 +03:00

Author

Owner

@lapo-luchini commented on GitHub (Feb 24, 2022):

Oh, sorry, I checked but I forgot to report: nothing happens in the console.

And I'm using the "installed" PWA (from Chrome Beta for Windows).

…but I can reproduce the problem also on Firefox when visiting the normal website.

@lapo-luchini commented on GitHub (Feb 24, 2022): Oh, sorry, I checked but I forgot to report: nothing happens in the console. And I'm using the "installed" PWA (from Chrome Beta for Windows). …but I can reproduce the problem also on Firefox when visiting the normal website.

kerem commented

2026-03-16 16:51:05 +03:00

Author

Owner

@lapo-luchini commented on GitHub (Feb 24, 2022):

It seems to be working in an incognito window, so I guess this is depending on my own "cloud sync'ed" data.

@lapo-luchini commented on GitHub (Feb 24, 2022): It seems to be working in an incognito window, so I guess this is depending on my own "cloud sync'ed" data.

kerem commented

2026-03-16 16:51:10 +03:00

Author

Owner

@lapo-luchini commented on GitHub (Feb 24, 2022):

Everything console related (all appears on PWA reload, nothing more appears when clicking on name clicking or edit menu clicking):

@lapo-luchini commented on GitHub (Feb 24, 2022): Everything console related (all appears on PWA reload, nothing more appears when clicking on name clicking or edit menu clicking): <img width="799" alt="image" src="https://user-images.githubusercontent.com/420454/155576551-6f53861e-279e-4356-96b6-71446426a499.png">

kerem commented

2026-03-16 16:51:16 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Feb 26, 2022):

@lapo-luchini can you delete the environment and try creating again, most probably its a cloud sync issue, you could also try exporting the environment and give us the text content of it (preferably with any private stuff redacted), we could confirm its a sync issues.

@AndrewBastin commented on GitHub (Feb 26, 2022): @lapo-luchini can you delete the environment and try creating again, most probably its a cloud sync issue, you could also try exporting the environment and give us the text content of it (preferably with any private stuff redacted), we could confirm its a sync issues.

kerem commented

2026-03-16 16:51:21 +03:00

Author

Owner

@lapo-luchini commented on GitHub (Feb 26, 2022):

Sync is working, as I just logged in a new Firefox and it did receive the 4 environments I use. But isn't editable here neither, so yes, most definitely something about the content that gets sync'ed.
Looks pretty normal though.
It's just structure like this, repeated 5 times:

[
  {
    "variables": [
      {
        "value": "https://(hostname)/we2/",
        "key": "we2"
      },
      {
        "key": "username",
        "value": "(email address)"
      },
      {
        "value": 123456,
        "key": "password"
      }
    ],
    "environmentIndex": 1,
    "name": "WE test9"
  },
  // 4 others similar objects
]

Can I send you the (complete) JSON export to you privately? It doesn't contain anything excessively private, but I'd rather not attach it in public GitHub.
Mhh, now that I notice: the first element (the oldest one) has a "environmentIndex": 1 field while the other 4 environs don't.

@lapo-luchini commented on GitHub (Feb 26, 2022): Sync is working, as I just logged in a new Firefox and it did receive the 4 environments I use. But isn't editable here neither, so yes, most definitely something about the content that gets sync'ed. Looks pretty normal though. It's just structure like this, repeated 5 times: ```json [ { "variables": [ { "value": "https://(hostname)/we2/", "key": "we2" }, { "key": "username", "value": "(email address)" }, { "value": 123456, "key": "password" } ], "environmentIndex": 1, "name": "WE test9" }, // 4 others similar objects ] ``` Can I send you the (complete) JSON export to you privately? It doesn't contain anything excessively private, but I'd rather not attach it in public GitHub. Mhh, now that I notice: the first element (the oldest one) has a `"environmentIndex": 1` field while the other 4 environs don't.

kerem commented

2026-03-16 16:51:26 +03:00

Author

Owner

@lapo-luchini commented on GitHub (Feb 26, 2022):

OK, by bisection of exported/imported environs I found the issue: that "value": 123456 element. Which I guess was created by an old version of Hoppscotch, as if I delete/re-create that from the GUI it gets created correctly as a string instead of a number.

So, ok, my problem is solved! Do you want to keep this open in order to track the "old values with wrong numeric content break all environ editing with no warning in the console" thing, or feel free to close this when you see it.

@lapo-luchini commented on GitHub (Feb 26, 2022): OK, by bisection of exported/imported environs I found the issue: that `"value": 123456` element. Which I guess was created by an old version of Hoppscotch, as if I delete/re-create that from the GUI it gets created correctly as a string instead of a number. So, ok, my problem is solved! Do you want to keep this open in order to track the "old values with wrong numeric content break all environ editing with no warning in the console" thing, or feel free to close this when you see it.

kerem commented

2026-03-16 16:51:31 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Feb 26, 2022):

@lapo-luchini hehe, I expected this to be a translation issue. Yeah, this could have been something that was lost in translation over to the new environments format. We will keep the issue open until we have a formal resolution of it.

Thanks so much for your help and collaboration! ❤️

@AndrewBastin commented on GitHub (Feb 26, 2022): @lapo-luchini hehe, I expected this to be a translation issue. Yeah, this could have been something that was lost in translation over to the new environments format. We will keep the issue open until we have a formal resolution of it. Thanks so much for your help and collaboration! ❤️

kerem commented

2026-03-16 16:51:36 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 9, 2023):

Closing due to inactivity.

@liyasthomas commented on GitHub (Dec 9, 2023): Closing due to inactivity.

kerem referenced this issue

2026-03-17 00:28:55 +03:00

[PR #715] [MERGED] Turkish Language Updated. #2807