Automattic / Automattic/jetpack
Geolocation: Conflict with wordpress-geo-mashup
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
User in 1682740-zen has found that our geolocation feature runs into the duplicate namespace attribute issue (mentioned here: #10061) when JP is active at the same time as `wordpress-geo-mashup`. Their corresponding GitHub issue is here:
https://github.com/cyberhobo/wordpress-geo-mashup/issues/829
Per @jeherve in Slack:
> We could check for a list of plugins that already do that before we enable our feature
Contributor guide
Research direction
Start by reading issue #10061 and the linked wordpress-geo-mashup issue #829 to understand the duplicate namespace attribute conflict. Then locate Jetpack's geolocation feature and determine how compatibility with an active wordpress-geo-mashup installation should be handled; done means the conflict no longer occurs when both plugins are active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100