Foros de discusión

Double Login on web content - Need Help

Dennis2009 Harris, modificado hace 14 años.

Double Login on web content - Need Help

New Member Mensaje: 1 Fecha de incorporación: 6/10/09 Mensajes recientes
Hi everyone,

I had Liferay setup on a dev server and added alot of web content. I was accessing the system via the IP since we had not purchased the domain name. Once we got the domain name and had it pointed to liferay. Now when I access Liferay and login it asks me to login in again for each web content. Now if you look at the source of the web content it shows the IP and not the domain name, if I change it here it work. But I have alot of users in the system and it would be very time consuming to go and change all the source. Is there a workaround for this.

Thanks,
D
thumbnail
Lisa Simpson, modificado hace 14 años.

RE: Double Login on web content - Need Help

Liferay Legend Mensajes: 2034 Fecha de incorporación: 5/03/09 Mensajes recientes
Maybe an update query on your database to replace the IP with the host name?
thumbnail
Olaf Kock, modificado hace 14 años.

RE: Double Login on web content - Need Help

Liferay Legend Mensajes: 6403 Fecha de incorporación: 23/09/08 Mensajes recientes
You mean that you've used absolute links to the IP-Address in your webcontent? I believe there's no solution out of the box. You might get away as Lisa suggested, locating your content in the database and query/replace the content there with a tool that you're familiar with (you sound like you're just starting with Liferay)

Also, Liferay has an API that you could leverage to read all articles, change them as required and save them again, but this would require some Java-coding against said API - might be the best solution, but requires some involvement with the API. Nice investment into the future I might say though. Especially as you could run this often to fix any links being created wrong later.

Whatever you do: Don't change your links from http://10.0.0.1/web/guest/welcome to http://www.example.com/web/guest/welcome, but make them relative to the current server root, e.g. /web/guest/welcome. This way the IP address as well as the hostname will work. Plus, if you decide to leverage https later, this will work out of the box.