search

neos / flow-development-collection

The unified repository containing the Flow core packages, used for Flow development.
https://flow.neos.io/
MIT License
139 stars 188 forks source link

FizzleParser has a problem with "numbers" only nodepaths #2877

Open gerdemann opened 8 years ago

gerdemann commented 8 years ago

Description

If I run in TypoScript a find('/sites/shop/products-abc-de/07400/074008468') I get the following error:

The Selector "/sites/shop/products-abc-de/07400/074008468" could not be parsed. Error at character 28

Steps to Reproduce

  1. Create a Node with "numbers" only path
  2. Search in TypoScript with e.g. find('/sites/shop/products-abc-de/07400/074008468')

    Expected behavior

I expect a valid result.

Actual behavior

I get the following error:

The Selector "/sites/shop/products-abc-de/07400/074008468" could not be parsed. Error at character 28

Affected Versions

Neos: 2.3.7 Flow: 3.3.4

kitsunet commented 7 years ago

This is very much related to (and could be fixed by) https://github.com/neos/neos-development-collection/pull/1477

aertmann commented 7 years ago

Wait, this issue is a bug and should be fixed in existing versions. Might be fixed by neos/neos-development-collection#1477, but not necessarily.

mhsdesign commented 2 years ago

This is still an issue and was not fixed.

The Selector "/sites/shop/products-abc-de/0740e0/f074e008468" could not be parsed. Error at character 28.

mhsdesign commented 2 years ago

this seems to be a flow issue - (the parser for the filter lies there) https://github.com/neos/flow-development-collection/blob/25f0b6abba5d45e1376fdfa05c5b7589e2bc3a54/Neos.Eel/Resources/Private/Grammar/Fizzle.peg.inc#L121