Shortcut leads to 404 about typo3-realurl

[markuskappe]

Complete 404 message:
Reason: Segment "mypagename" was not a keyword for a postVarSet as expected on page with id=1.

[dmitryd]

I cannot reproduce it. Please, post your config.

[markuskappe]

unserialized it for readability; generated by autoconf feature

array (
  '_DEFAULT' => 
  array (
    'init' => 
    array (
      'appendMissingSlash' => 'ifNotFile,redirect',
      'emptyUrlReturnValue' => '/',
    ),
    'pagePath' => 
    array (
      'rootpage_id' => '1',
    ),
    'fileName' => 
    array (
      'defaultToHTMLsuffixOnPrev' => 0,
      'acceptHTMLsuffix' => 1,
      'index' => 
      array (
        'print' => 
        array (
          'keyValues' => 
          array (
            'type' => 98,
          ),
        ),
      ),
    ),
    'postVarSets' => 
    array (
      '_DEFAULT' => 
      array (
        'news' => 
        array (
          0 => 
          array (
            'GETvar' => 'tx_news_pi1[news]',
            'lookUpTable' => 
            array (
              'table' => 'tx_news_domain_model_news',
              'id_field' => 'uid',
              'alias_field' => 'title',
              'useUniqueCache' => 1,
              'useUniqueCache_conf' => 
              array (
                'strtolower' => 1,
                'spaceCharacter' => '-',
              ),
            ),
          ),
        ),
      ),
    ),
  ),
)

same problem here, I enabled automatic configuration.

I get the same error msg with disabled pages in the rootline . I have a fresh Typo3 6.2.19 website with no own realurl configuration, just auto config.

[dmitryd]

Disabled pages in the rootline usually break the rootline and does not allow browsing.

[jdequeant]

Same problem only when I'm logged in backend (works perfectly when not logged in), no page disabled in the rootline.

I use TYPO3 7.6.4

[Kephson]

Same problem for me only when I'm logged in in TYPO3 backend and it works when I'm not logged in.
TYPO3 7.6.4
I will try to find out, what's the problem and give you feedback.

[dmitryd]

Yes, reproduced. Going to fix.

[Kephson]

Thanks a lot for your realurl update! Coding is really clean to understand now ;-).
\DmitryDulepov\Realurl\Utility->getCache() produces the problem, I think you still found out the problem.
Why is the cache initialized as NullCache when backend user is logged in? Is there a strange behaviour or problems?

[dmitryd]

Cache must be null when the BE user is logged in because BE user can see some pages that normal visitors cannot see (for example, hidden pages). If it is not null, cache may get wrong entries.

[dmitryd]

Those, who want to help with testing, try this branch: https://github.com/dmitryd/typo3-realurl/tree/feature/bug_42

You will need to clear both path cache and url cache. Sorry about that. Alternatively delete cache entries for shortcut page (source).

To clear caches using sql:

truncate tx_realurl_urlcache;
truncate tx_realurl_pathcache;

[Kephson]

Hi Dmitry,
thanks for the fast update! I tested your branch with the fix and for me it's working like expected.

[dmitryd]

Okay, good. Let's see if works for somebody else too. If yes, I will merge it.

[jdequeant]

Works for me !! Thanks for all your hard work.

[dmitryd]

You can now update to release 2.0.3, which contains the fix.

[stekna]

i still get this error with fresh installed realurl 2.0.10 (typo3 is on 7.6.4).
e.g. error on "normal page"

- shortcut-page
-- sub-shortcut-page
--- normal page (error)

e.g. no error on "normal page"

- shortcut-page
-- normal page (no error)

[ogrosko]

Can confirm
Same problem at typo3 v7.6.6 and realurl v2.0.14