gentics / gentics/mesh

Error getting a specific version when using webroot url

Open
#1,112 1 comment 0 reactions 0 assignees View on GitHub
bug f/rest
Dominant language
Java
Stars
593
Forks
123
Avg merge
2d 18h
Merged PRs (30d)
4

Description

## Gentics Mesh Version.
- v1.7

## Operating System
- Windows

## JVM
- Oracle JDK 11.0.8

## Problem
according to the documentation [versioning](https://getmesh.io/docs/features/#versioning), adding the query parameter version follow by the version number [major].[minor], the specif version should be generated, when I used this format

/api/v2/{project}/nodes/{uuid}?version=[major].[minor]

it works without problems, but if I used this format

/api/v2/{project}/webroot/{slug}?version=[major].[minor]

it shows the next error message

{
"i18nParameters" : [ "{slug}" ],
"i18nKey" : "node_not_found_for_path",
"properties" : { },
"type" : "generic_error",
"message" : "Node for path \{slug}" could not be found."
}

I used the draft and published values in order to check the behavior and both work using the webroot path

Contributor guide

Open the contributing guide

Research direction

Start with the versioning documentation and compare request handling for `/api/v2/{project}/nodes/{uuid}?version=[major].[minor]` and `/api/v2/{project}/webroot/{slug}?version=[major].[minor]`. Reproduce the reported `node_not_found_for_path` response with draft and published values; done when the webroot URL returns the requested version consistently with the node endpoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.