-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Gutenberg: Reimplement Location Feature #29670
Comments
Marking as low priority compared to other user requests. It looks like this is also already supported in Jetpack: https://github.com/Automattic/jetpack/blob/master/modules/geo-location/class.jetpack-geo-location.php#L3 |
@Copons are you still working on this, or would you like to unassign the issue? |
This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels. |
This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels. |
It has been several years since the original report, and geotagging feature request doesn't come up often from our users. Even if it does, our doc currently recommends navigating to the classic editor to make use of that feature. As such, I'll close this for now but we can reopen if we feel that this should be possible from the block editor as well. |
The Calypso Classic editor has a Location feature in the sidebar that adds a location to a published post. This issue will add that to wpcom and we should consider if this also makes sense in Jetpack.
Screenshot / Video
Extra notes
The text was updated successfully, but these errors were encountered: