Short description of the enhancement
hookable LanguageSupportPageNames::getPagePath()
Current vs. suggested behavior
Currently LanguageSupportPageNames::getPagePath() is not hookable whereas Page::path() is.
Why would the enhancement be useful to users?
I am currently working on a complete rewrite of the Multisite module (single database).
https://github.com/kixe/Multisite/tree/kixe
https://processwire.com/talk/topic/1025-multisite/?page=10#comment-144509
To modify the page pathes I decided to hook in Page::path() instead of modifying the output of Page::render(). The module works already quite stable, but needs to have LanguageSupportPageNames::getPagePath() hookable for full language support.
Short description of the enhancement
hookable
LanguageSupportPageNames::getPagePath()Current vs. suggested behavior
Currently
LanguageSupportPageNames::getPagePath()is not hookable whereasPage::path()is.Why would the enhancement be useful to users?
I am currently working on a complete rewrite of the Multisite module (single database).
https://github.com/kixe/Multisite/tree/kixe
https://processwire.com/talk/topic/1025-multisite/?page=10#comment-144509
To modify the page pathes I decided to hook in
Page::path()instead of modifying the output ofPage::render(). The module works already quite stable, but needs to haveLanguageSupportPageNames::getPagePath()hookable for full language support.