# روابط تضمين خرائط جوجل تعمل أحيانًا ولا تعمل أحيانًا أخرى (onebox 404)

**URL:** <https://meta.discourse.org/t/google-maps-embeded-links-sometimes-work-sometimes-dont-onebox-404/243976>\
**Category:** Bug\
**Created:** [2 نوفمبر 2022، 11:57ص UTC](https://meta.discourse.org/t/google-maps-embeded-links-sometimes-work-sometimes-dont-onebox-404/243976 "2022-11-02T11:57:09Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![loic](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/loic/32/105621_2.png) [@loic](https://meta.discourse.org/u/loic)\
**Post date:** [1 مارس 2023، 11:46ص UTC](https://meta.discourse.org/t/google-maps-embeded-links-sometimes-work-sometimes-dont-onebox-404/243976/10 "2023-03-01T11:46:06Z")

</div>

تم الإصلاح هنا:

> <https://github.com/discourse/discourse/pull/20497>
>
> Sometimes we get Maps URL containing a zoom level as a float (17.5z and not 17z)… but this doesn’t work with our current onebox implementation.
> 
> While Google accepts those float zoom levels, it removes automatically the floating part in the URL (thus when visiting a Maps URL containing 17.5z, the URL will be rewritten shortly after as 17z). When putting a float zoom level in an embedded URL, this actually breaks (Maps API returns a 400 error).
> 
> This PR addresses the issue by allowing the onebox engine to match on a zoom level expressed as a float but we only keep the integer part, thus rendering properly maps.

---

_[View the full topic](https://meta.discourse.org/t/google-maps-embeded-links-sometimes-work-sometimes-dont-onebox-404/243976)._