[Neos] Neos 1.2.6 - Path For New Pages

[Aske Ertmann]

Hi Nikos

Yes it by intention, this is the change that caused it
https://review.typo3.org/#/c/37525/

In short, the existing solution was unreliable and didn't make sense when
having translated content. If you use FlowQuery you can use a filter like
[uriPathSegment="your-url"] to achieve the same as before.

Cheers,
Aske

On Fri, May 15, 2015 at 12:57 PM, nikos <nick at jamalade.com> wrote:

> It seems that unless you look into the database or the route cache it is
> impossible to create a URI from a nodepath as it does not relate at all to
> uriPathSegment which is human readable.
>
> Is this really the itention? Is it a general issue or could it be my
> setup? As it seems to me anything created before the upgrade (could have
> been before 1.2.6) you can use the uriPathSegment anything after you can't.
> Quite frustrating.
>
> Warm regards
>
> Nikos
>
>
> On 14/05/2015 20:15, nikos wrote:
>
>> Hi
>>
>> I have just upgraded my dev install from 1.2.3 to 1.2.6 using composer
>> and all ran smoothly, thanks for all the great work :)
>>
>> However I have noticed that when I create new pages from the back end
>> their nodepath no longer seems to have the uirsegment but something like
>> "node-123445".
>>
>> In the browser the uri resolves as extepected mysite/new-page.html
>>
>> However when I try and create a URI using
>> \TYPO3\Flow\Mvc\Routing\UriBuilder->uriFor(...) eg to Redirect a Form to
>> new-page it is unable to resolve
>> the node using the human readable node name "new-page". If I use
>> "node-123445" it works but that doesn't feel like the right thing to do.
>>
>> Is this the expected behaviour? Should I be using something other than
>> UriBuilder for this now? Or might it be a problem with my setup?
>>
>> Any help or ideas welcome and appreciated.
>>
>> Warm wishes
>>
>> Nikos
>>
>>
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
>