Activities

Today
Jorge Ferrer updated LPS-86216.
6:07 AM Updated priority to Trivial.<br />
Jorge Ferrer updated LPS-86532.
1:23 AM Updated status to Aligned with Roadmap.<br />
Yesterday
Jorge Ferrer updated LPS-44217.
11:54 PM Updated status to Aligned with Roadmap.<br />
Jorge Ferrer updated LPS-44217.
11:54 PM Updated status to Open.<br />
Jorge Ferrer commented on LPS-44217.
11:54 PM Thanks [~jose.jimenez] and [~jardineworks], those are very useful examples. I&#039;m going to transition the ticket to &#034;Aligned with roadmap&#034;
June 14
Jorge Ferrer updated LPS-44217.
3:48 AM Updated status to Needs More Information.<br />
Jorge Ferrer commented on LPS-44217.
3:48 AM Hey [~jose.jimenez], [~istvan.gergely], Is the need always linked to translations? If so, I think it would be best for the solution to address that case specifically, instead of implementing a generic solution of allowing multiple virtual host names. Also, would it be necessary to ask them to specify the virtual host names? Wouldn&#039;t it be better to generate them automatically for each of the languages enabled for the site?
Jorge Ferrer updated LPS-78298.
3:46 AM Updated resolution to Won&#039;t Do.<br />Updated status to Does Not Fit Roadmap.<br />
Jorge Ferrer updated LPS-78298.
3:46 AM Updated status to Open.<br />
Jorge Ferrer commented on LPS-78298.
3:45 AM For the record, here are the conclusions that we have reached after analyzing this request # The purpose of the &#034;Link to page&#034; functionality is to allow showing an specific page in several places in the navigation of a site. # The way this functionality has been implemented allows specifying a URL for the &#034;link&#034; which results in a temporary redirect to the URL of the target page. It is important that this redirect is made temporary, so that browsers and HTTP proxies don&#039;t cache the redirect. If the redirect were permanent, and the &#034;Link to page&#034; is at some point updated to point to a different page, that change would not propagate, creating an undeterministic result. # It would have probably been more optimal to not allow entering a URL for the &#034;link&#034; and just use the URL of the target page from the beginning, avoiding the need for a redirect. However, since this could cause issues to existing customers leveraging &#034;Link to page&#034; as explained in point #4, we have decided to keep the behavior as it is. # We have identified that a significant number of users are leveraging the &#034;Link to page&#034; functionality to configure redirects. This is very handy, since alternatives like configuring redirects in HTTP Servers are often most costly. However it has the drawback that for those cases it&#039;s desired to be able to choose between permanent and temporary redirects depending on the case. This is what has led to this feature request. We understand the need based on the description in the last point above. At the same time, we believe that changing the &#034;Link to page&#034; functionality to make the type of redirect configurable, would add a complexity that would be negative for those using the functionality for its main purpose. Not only that, we would be providing an option (permanent redirects) which can cause undeterministic negative effects when the target page is changed. Because of this we have concluded that allowing this configurability would be a bad idea for the product. We believe that better solutions are needed. One solution that we have in our roadmap is to automatically keep working old friendly URLs for a page (and other content types) whenever there is a change to it. In this case, when the old URL is used, a permanent redirect would be sent to the client. For more generic needs to configure redirects, we believe that other tools outside of Liferay might be a better solution.  
Subscribe to Jorge Ferrer's activities. (Opens New Window)