#277 — Link to translationsbrowserpopup broken in some VirtualHost setups
by
Thomas Graf
—
last modified
Jun 26, 2011 01:09 PM
| State | Resolved |
|---|---|
| Version: | 4.x |
| Area | User interface |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Thomas Graf |
| Submitted on | Jun 15, 2011 |
| Responsible |
—
|
| Target release: | 4.x |
The link to the translationbrowser_popup from manage_translations_form uses the path from the context to ZODB root. (startup_directory python:'/'.join(here.getPhysicalPath());)
This breaks the link in some virtualHost setups especialy where the _vh_ feature of the VHM is used.
Changing the startup_dir var to something like python:context.getCanonical().absolute_url(); could solve the problem.
This breaks the link in some virtualHost setups especialy where the _vh_ feature of the VHM is used.
Changing the startup_dir var to something like python:context.getCanonical().absolute_url(); could solve the problem.
- Steps to reproduce:
- Asume the following setup:
In the zodb the plone site resides in /plonesite/
Our instance listens to localhost:8080
Our webserver takes requests for example.com. The plonesite is mapped to example.com/coolstuff via following rewrite:
http://localhost:8080/[…]/$1
If you call the translationsbrowser from the subpage example.com/coolstuff/subpage linguaplone tries to load the browser from (example.com)/plonesite/subpage/translationbrowser_popup
The correct Link is (example.com)/coolstuff/subpage/translationbrowser_popup
Added by
Hanno Schlichting
on
Jun 26, 2011 01:09 PM
Thanks for the patch. I applied and verified it. The fix will be released with LinguaPlone 4.0.4.
Issue state:
Unconfirmed
→
Resolved
Target release:
None
→
4.x
No responses can be added.
If you can, please log in before submitting a reaction.

diff.patch