Modify

Ticket #5436 (closed defect: fixed)

Opened 17 months ago

Last modified 17 months ago

cannot load external presets: schema_reference failed

Reported by: bastiK Owned by: team
Priority: normal Component: Core
Version: latest Keywords:
Cc:

Description

see screenshot:

Attachments

josm-presets.png Download (20.1 KB) - added by bastiK 17 months ago.
josm-validation.png Download (26.0 KB) - added by bastiK 17 months ago.

Change History

Changed 17 months ago by bastiK

comment:1 follow-up: ↓ 10 Changed 17 months ago by anonymous

Fixed oneclick.xml, othes probably will fails as well. Reason is missing

xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"

in main tag.

comment:2 Changed 17 months ago by bastiK

Why is this needed? Is it possible to make it optional?

(Remark: I think you broke the xml - missing ">")

comment:3 Changed 17 months ago by jttt

It is optional - you can say that you want to use preset anyway and it will be loaded (if possible).

comment:4 Changed 17 months ago by stoecker

I updated the presets attached to presets page.

comment:5 Changed 17 months ago by vsandre

The problem still occurs although the files contains xmlns-tag.

comment:6 Changed 17 months ago by stoecker

You deleted the local mirror file (or the mirror entry in advanced preferences)?

comment:7 Changed 17 months ago by anonymous

No, but I tested it with presets I have used before. So I could not delete a preset. If I add another preset the message pops up for others not changed presets as well.

comment:8 Changed 17 months ago by stoecker

JOSM keeps the old files. You wont get the new one except you either wait a week or delete the local mirrorfile. If both does not work, specify exactly which file fails.

comment:9 Changed 17 months ago by vsandre

I have deleted all mirror files and started josm again. But if add or delete another preset the message pops up again. After a restart it works without any errors.

comment:10 in reply to: ↑ 1 Changed 17 months ago by bastiK

Replying to anonymous:

Fixed oneclick.xml, othes probably will fails as well. Reason is missing

xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"

in main tag.

It seems this does not help. The error comes even for internal preset.

comment:11 Changed 17 months ago by jttt

What is marked as Internal preset is in fact rule file for MapPaintVisitor, it should be probably removed from preset list. xmlns tag shouldn't be required, validator will use http://josm.openstreetmap.de/tagging-preset-1.0 if nothing else is specified.

comment:12 Changed 17 months ago by jttt

The error message is shown because tagging-preset.xsd file is not included in josm jar. When xsd file is available (for example when running custom build josm), some preset will be loaded without problems (for example one-click), others will complain about real errors.

Changed 17 months ago by bastiK

comment:13 Changed 17 months ago by bastiK

I included the tagging-preset.xsd in my custom build. The xmlns does not seem to be optional (but should be) - see previous screenshot.

comment:14 Changed 17 months ago by stoecker

(In [3533]) see #5436 - move xsd to proper place

comment:15 Changed 17 months ago by jttt

In the screenshot is error message about space tag being at wrong place, nothing about xmlns. I don't have the file here right now, but from the error message it looks like space tag is used where presets are defined, but it makes sense only inside of item tag.

comment:16 Changed 17 months ago by bastiK

  • Status changed from new to closed
  • Resolution set to fixed

comment:17 Changed 17 months ago by stoecker

I set up a redirect, so that http://josm.openstreetmap.de/tagging-preset-1.0 actually works :-)

BTW: Could we get a http://josm.openstreetmap.de/mappaint-style-1.0 as well?

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.