Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{bbox} token not working #1694

Open
Swarkin opened this issue Feb 22, 2025 · 2 comments
Open

{bbox} token not working #1694

Swarkin opened this issue Feb 22, 2025 · 2 comments

Comments

@Swarkin
Copy link

Swarkin commented Feb 22, 2025

Description

When using a custom url with the {bbox} token, all tokens stop working and Rapid no longer replaces them.

Screenshots

No response

Version

2.5.2

What browser are you seeing the problem on? What version are you running?

Firefox 135.0.1

The OS you're using

Windows 11 LTSC

Steps to reproduce

  1. Use custom imagery
  2. Add {bbox} token

The browser URL at the time you encountered the bug

https://rapideditor.org/canary#map=20/.../...&poweruser=true

The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)

No response

@Bonkles
Copy link
Contributor

Bonkles commented Feb 25, 2025

hi @Swarkin - do you have a more detailed set of repro steps (url that you pasted into the custom imagery UI, etc) that I can use to look into this?

@Swarkin
Copy link
Author

Swarkin commented Feb 25, 2025

hi @Swarkin - do you have a more detailed set of repro steps (url that you pasted into the custom imagery UI, etc) that I can use to look into this?

Hello, yes I have found out some better reproduction steps:

  • First off, you need to have some kind of different functional custom imagery selected
  • Next, you have to paste in a link to some imagery source that makes use of the {bbox} token
  • This now causes the new imagery to be requested without Rapid replacing the tokens!
  • Changing the custom url at this point has no effect
  • Refreshing the tab results in working imagery again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants