SOLVED: Custom map marker does not work if using custom URL

Bugs
1

Browser: any
OS: any
URL: Link to a page that illustrates this issue

I am using a dynamic function to provide the URL of the marker image in a Map Connector.

Bricks
Bricks1872Ă—203 51.9 KB

On the frontend, I get the generic marker. My custom marker is not used.

Code
Code670Ă—797 204 KB

I am unable to reproduce this in the sandbox because code execution is disabled.

Also, the width and height fields (as shown in your documentation) are missing from the UI, which correspond to the `scaledSize` property.

2

Hi @glp,

If you just choose the image, does it work then? I’ve tested with echo tag, where my function returns an image ID, and it works. What does your function return? Does it work with some other image?

Best regards,
Matej

3

My function returns a URL that varies depending on a taxonomy. I have tried both possible URLs, and both appear in the builder sidebar (so they are valid and correct), just not on the actual page. It does not matter what what the URL is.

Recording

4

The result is the same without a function call. Pasting a URL into the field is also no good.

Screenshot 2025-12-01 at 5.24.33 AM
Screenshot 2025-12-01 at 5.24.33 AM1871Ă—307 81.5 KB

5

Hi @glp,

if it’s returning the URL, then please ensure that you are using “Custom URL” field. Do you?

CleanShot 2025-12-01 at 15.35.08@2x
CleanShot 2025-12-01 at 15.35.08@2x578Ă—604 20.5 KB

Matej

6

Yes of course I am using the Custom URL field

7

If I change the settings and the function to use an ID, that works to get them output on the page. Obviously that is not ideal because I do not want these images in the media library. And moreover, they do not display at the correct size; they are both scaled to 40px. One should be 24px and the other 46px.

8

Hi @glp ,

Yes, we are aware of this issue in 2.1.4 (Reported by other users via email in November).
When using “Full URL” in custom URL control, it’s not rendering.

I believe Matej was using our latest development code (which already fixed this issue) and so he can’t replicate this issue :slight_smile:

Regards,

Jenn

1 Like
9

We fixed this issue in Bricks 2.2 beta, which is now available in your account.
Changelog: Bricks 2.2-beta Changelog – Bricks

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment. The more feedback we get, the better :v: