2.2.1 - does not honor config.absRefPrefix anymore

[infabo]

привет,

since 2.2.1 absRefPrefix in HMENU is not respected anymore. Switching back to 2.2.0 - and it works like a charm again.

[infabo]

my best guess:

commit: 235d377eac30c3f5ce204b7f6eeb5bc11399a720

[adrienjacob]

That's my opinion too, cf. suggested fix : https://github.com/dmitryd/typo3-realurl/pull/478

[dmitryd]

I can't confirm it. I made a menu with HMENU and absRefPrefix is taken into account.

[infabo]

I'm not using crossdomain linking, since the menu is generated for the primary domain.

I can confirm. 2.2.0 -> OK. 2.2.1 - > DEAD.

Reproduce:

1. create HMENU with at least one sub-level
2. go to frontend and
3. navigate to sublevel-page.
4. step 3 is important. on root-page the HMENU is an absolute dream. so please honor step 3.
5. see the "broken" HMENU urls

[tcrass]

Same here! Consider a menu structure like

    + foo
      + bar 
        + baz

Page at /foo contains ok link to /foo/bar Page at /foo/bar contains wrong link to /foo/foo/bar/baz

Can also confirm that reverting to 2.2.0 fixes this behaviour.

[dmitryd]

As I wrote above, I was not able to reproduce that. I can't fix it until I can reproduce it.

Please, post information about your config.absRefPrefix setting and also example of menu generation code.

[dmitryd]

I am using my test site. I am on "Subpage A" and hovering my mouse over "Subpage AA". The link is correct:

My menu setup is here.

Guys, are you sure you did not forget to add config.absRefPrefix = / to your TS?

[tcrass]

Dimitry,

thanks for responding!

Guys, are you sure you did not forget to add |config.absRefPrefix = /| to your TS?

Positive, in my case, config.absRefPrefix is set to "/" for all of my multi-domain websites.

Unfortunately, I'm currently quite busy preparing for my holidays; I hope I'll soon find the time to create a minimum working example demonstrating the problem.

(Just one thought: In my case, the root pages (and yes, they are marked as such in both PageTS and the corresponding template ;) are page links -- is it possible that this may be part of the problem?)

Cheers --

Torsten

[tzNewtown]

Hello Mr. Dulepov,

to reproduce this issue you need the following setup:

Create a Page called "root", set "use as root page" to enabled Create a sub-page to "root", call it "main website". set "use as root page" to enabled Create some sub-pages to "main website", add the domain record to "main website" and create the HMENU.

If you need help for the setup or have further questions do not hasitate to contact me.

best regards Thomas

[dmitryd]

@tzNewtown

Create a Page called "root", set "use as root page" to enabled Create a sub-page to "root", call it "main website". set "use as root page" to enabled

You are trying to use nested domains. This is officially not supported. There can be only one root page in the rootline.

[tzNewtown]

@dmitryd, Thank you, for your fast reply.

from the wiki page you linked to:

Nested domains are not supported. This means you can have only one domain from any page up to the root of the page tree.

There must be no "nested domains". This means that there can be only one domain record from the current page down to the root of the page tree. RealURL does not support nested domains!

Please read my instructions of how to reproduce the issue once again.

Create a Page called "root", set "use as root page" to enabled Create a sub-page to "root", call it "main website". set "use as root page" to enabled Create some sub-pages to "main website", add the domain record to "main website" and create the HMENU.

There is only a single domain record located at the "main website" page. the page "root" does not have any domain records. The only domain record of the whole TYPO3 installation is located at page "main website".

There is no nesting of domains invovled. So this is not violating the "nested domains not supported" requirement.

Thanks in advance, regards Thomas

[dmitryd]

In TYPO3 "use as root page" means the same as the domain record.

[albig]

I've just tried 2.2.1 with our setup and stuck in this issue. I read the limitation, that nested domains are not supported. And I was happy, that our setup did work anyway up to 2.2.0.

That's what we are doing:

page 1: Domain www.example.com, is_siteroot = 1
  |- page 2
  |- page 3: Domain blog.example.com, is siteroot = 1
       |- page 4
       |- page 5

On all pages, the config.absRefPrefix = / is set by Typoscript.

If you're on page 4, with realurl 2.2.0 the link to page 3 is /, and to page 5 is /page-5/.

If you're on page 4, with realurl 2.2.1 the link to page 3 is /, and to page 5 is page-5/ --> the resulting link is http://blog.example.com/page-4/page-5/.

[AndreasA]

Why not move blog.example.com outside of the page-1 root and create a shortcut page to it inside page-1? That removes the nexting and you still have a link to the blog inside page-1 menu.