Browser Console Errors

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, jquery, php, wordpress
Domain
frontend, web-dev

Research direction

Start by reproducing the reported console errors while creating a map in the WordPress backend or frontend submission form, especially after adding a line and at least three route points. The report names no source files or tests, so trace the errors from the map editor and check the jQuery and layer calls involved. Done means the reported errors no longer occur during map creation and item removal.

Written by the indexing model from the issue text.

Description

When creating a map in Waymark in WP backend or frontend submission form we see the following console errors as we add things to the map:

JQMIGRATE: jQuery.fn.change() event shorthand is deprecated
console.trace
migrateWarn	@	jquery-migrate.js?ver=3.4.1:138
obj.<computed>	@	jquery-migrate.js?ver=3.4.1:170
onAdd	@	waymark-js.min.js?ver=1.8.1:9
addTo	@	waymark-js.min.js?ver=1.8.1:1
addControl	@	waymark-js.min.js?ver=1.8.1:1
Waymark_Map_Editor.create_buttons	@	waymark-js.min.js?ver=1.8.1:9
Waymark_Map.setup_map	@	waymark-js.min.js?ver=1.8.1:9
Waymark_Map.init	@	waymark-js.min.js?ver=1.8.1:9
(anonymous)	@	create-map-2:6076
mightThrow	@	jquery.js?ver=3.7.1:3489
process

When adding a line followed by adding 3+ route points to a map I'd see the following come up:
jQuery.fn.hover() is deprecated

Uncaught TypeError: layer.getRadius is not a function

When removing items I've seen:
JQMIGRATE: jQuery.fn.removeAttr no longer sets boolean properties: selected

Dominant language
PHP
Stars
29
Forks
12
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenGIS/waymark-wp

All issues in OpenGIS/waymark-wp

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.