AlanOfTheBerg wrote:The # should not be in the permalink. Are you always getting the permalink from context-click/copy link the permalink? I've not seen it appear before.
Timbones wrote:Technical explanation: Any parameters after a # symbol will not be sent to the server when requesting a URL. The '#name' concept is for the browser only, and is so that you can have links within a document. It's part of the HTML specification, not the HTTP protocol.
The permalink button simply adds the parameters on the end of the URL in the address bar. If there happens to be a # on the end of the address (for whatever reason), you end up with a link that won't work.
Also, the last example that had '?&' at the start of the parameters probably won't work either.
maantje76 wrote:What happens if you change the zoomlevel in the not working permalink?
I did see this happen with some permalinks also. Changing the zoomlevel in the link let the segments apear for me...I can't remember the exact levels that gave this problem, but think I can find it back...
bz2012 wrote:It appears to me that some change in WME's code "broke" the 'segment selector' for URLs that used to work fine. Those URLs still work for all the other parameters (zoom, lat, lon, layers.)
Kuhlkatz wrote:bz2012 wrote:It appears to me that some change in WME's code "broke" the 'segment selector' for URLs that used to work fine. Those URLs still work for all the other parameters (zoom, lat, lon, layers.)
It's simply because the URL is broken.
The editor URL only accepts parameters for supported WME objects, and in the standard format for URLs :
- Code: Select all
The "...#?%23%3F=&zoom=6..." translates to "...#?#?=&zoom=6..." when the URL is 'decoded' which does not look good. The browser will attempt to find a local anchor tag on the page named according to what follows the "#" sign , which it cannot as it does not exist.
Has anybody actually bothered asking Rftyree, the OP that provided the permalink what browser and 'addons' he/she is using? Surely all users will have permalinks like this on the NA server if WME is broken.
It is likely not WME that screws up the permalink, but something that either overwrites the original WME permalink or provides a 'Permalink' option of it's own, where the code screws it up.
It could even be a screwed browser shortcut :
If I start a blank page and type in the URL "https://www.waze.com/editor/#noclue#", WME opens up fine and my Permalink is then :
which is also screwed, and obviously not WME's fault. It simply uses the main URL for the page, which it rightfully expects to end in /editor/.
You should rather ask why this boardwalk is connected to the road ?
bz2012 wrote:but it decodes all but "segment=xxxxxxx,xxxxxxx".
Does it fail to decode 'the LAST' ¶meter='?
bz2012 wrote:Sometimes I miss something or make a mistake, but from the number of mistakes I find, I think I am 'improving things more than messing them up.' I hope so.
Kuhlkatz wrote:The intention is not say anyone is incompetent. We all strive to better the maps in our area, AND we all make mistakes - it's part of the game, especially since we all tend to spend late nights editing. I get annoyed with myself too. After completing an area and looking at it weeks later, I still find some obvious mistakes.