I think there is some confusion here...
First of all I just reverted the changes I did yesterday to allow links on the current page because in the case of absolute addressing of container lists and fields it is indeed useful.
Then, Jahia internally uses "JahiaPage" objects to represent : - DIRECT pages : the actual content pages - Internal links : basically an object that points to a DIRECT page - External URLs : a String containing an URL to anything
So as each JahiaPage object is identified by a unique ID, it is normal that new PIDs ( = Page IDs) are created for Direct pages, internal links and external URLs. In the case of the the Link, we have something like this :
JahiaPage : pid=84, type=link, linktarget=1
which means that the PID=84 contains a link to page 1.
As for the warning you are getting in the console, this is normal, and shouldn't cause any kind of concern.
If you have another problem apart from this PID problem I am sorry but I didn't understand it, but nothing that you say seems to indicate unwanted behavior.
Regards, Serge Huber.
Roch CHIRON wrote:
Thanks, What i exactly did : 1. I selected the "Link to an existing Jahia page" option in the page popup. 2. And then i selected the Home Page in the "tree page popup".
The use of creating a link on the current page i had is to create a menu (with absolute pageField), the menu need a link to the page where the menu is editable, and so a link to the current page.
So for me to disallow the fonctionality that has an issue is not the best solution because i used it... Of course i can find an other way, but ...
And overall, the issue is more general and occures for link's creation that should not create a page : "Link to an existing Jahia page" (current page or not) or "Create a link to an external web site") : in this two cases, jahia create a page that is nor visible in the sitemap nor accessible ...
If you do some tests about creation of all types of links, and then try to access a page by writing the url with "pid = pid of last created page + 1", you should see the "unwanted" pages. (I've done such tests in the online demo today pid 89 to 94).
Thanks by advance,
Roch CHIRON
-----Message d'origine-----
De : Serge Huber [mailto:[EMAIL PROTECTED] Envoyé : jeudi 9 septembre 2004 14:11
À : [EMAIL PROTECTED]
Objet : Re: Link creation trouble
What do you mean by "creating a link" ? Do you mean an internal link or a hardcoded URL ? What operation exactly did you do in the page popup ?
Anyway I just committed to the CVS some code that disallows to create links on the current page, as I see no use for it anyway, so maybe this will solve this issue.
Regards, Serge Huber.
Roch CHIRON wrote:
Hello,
It seems to be a bug in jahia 4.0.4 cvs branch and online demo.
I’ve done a test on the online home page (in french) : i added a portlet of links, and then created a link named “HomeToHome” to the existing jahia page (Home pid=1).
The result is that it(jahia) created a page (with Home template) : you
activated.can see this page with pid=84.
Other way you can see an alerte on the workflow screen, that looks like a trouble :
Page 85 only has staged entries and recursive activation is not
(I created an other link to a new jahia page (jahia page creation.pid=85 but the alert was displayed before)org.jahia.content.ContentContainerListsXRefManager.getAbsoluteContainerL
And in my local tomcat logger output i can read :
3149241 [Thread-10] DEBUG
istsFromPageID:112
- Expected page type in cross reference list, ignoring value...
Looks like missing a parameter in the “creation page/link” form.
Thanks if someone already fixed this or has an idea about.
Roch CHIRON
