Forum: Instiki – Topic: SVG editor doesn't work

This looks like a path or routing issue rather than a browser issue.

The request is trying to load:

/svg-edit/editor/jgraduate/css/jGraduate.css

but Instiki is treating it like a wiki page request under the web name svg-edit:

/svg-edit/…

That is why it returns 404 instead of serving the CSS file as a static asset.

A few things to check:

1. Make sure the svg-edit folder actually exists in the public directory, not inside a wiki/web directory.

The expected file should be somewhere like:

public/svg-edit/editor/jgraduate/css/jGraduate.css

1. Check the exact capitalization of the file and folder names.

On Linux servers, file paths are case-sensitive. For example:

jGraduate.css

is not the same as:

jgraduate.css

or

JGraduate.css

1. Check whether your Instiki routing is catching static asset paths.

If static files are not being served before wiki routes, Instiki may interpret /svg-edit/… as a wiki web instead of a public asset path.

1. Try opening the CSS file directly in the browser:

http://localhost:2500/svg-edit/editor/jgraduate/css/jGraduate.css

If that gives 404, the problem is definitely the static file path or asset serving setup.

1. If the file exists but still gives 404, check the server configuration and make sure the public directory is being served correctly.

In short, the SVG popup is blank because the editor CSS is not loading. The main fix is to make sure the svg-edit assets are placed under the public/static asset path and that Instiki does not route those asset URLs as wiki page requests.