|
Author
|
Message
|
|
Paul Borgermans
|
Saturday 07 June 2003 5:51:23 am
----------------------
Arrghh redundant, Karsten posted the same request earlier here, so consider it as more weigth to his request
---------------------- Hi ez crew, With the upcoming changes and the need to adapt the contributed docs, I think the cross linking may pose problems with the use of url_alias. As the docs grow in size and number, some re-arrangements may be necessary. The use of url_alias is not robust in this respect. A simple additional field with "link me url" in the style of /content/view/full/nodeid may make the work of contributors a bit easier for porting between these link styles. Regards Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Bård Farstad
|
Saturday 07 June 2003 6:17:14 am
We will do something with this. Most likely add something like <link href="eznode:42">link to node 42</link>. Alternatively <node id="42" />, which will work similar to object related object but will have information about the node placement. Suggestions about how to make this as simple as possible are appreciated. --bård
Documentation: http://ez.no/doc
|
|
Gabriel Ambuehl
|
Sunday 08 June 2003 4:31:16 am
Keep the url_alias stuff and make the content module intelligent enough to change references? The ignorant version is to just scan the DB for references and substitute them with the new URL, the somewhat more elegant version would keep track of what pages links to what other pages.
Visit http://triligon.org
|
|
Paul Borgermans
|
Monday 09 June 2003 5:58:03 am
>We will do something with this. Most likely add something
>like <link href="eznode:42">link to node 42</link>.
>Alternatively <node id="42" />, which will work similar to
>object related object but will have information about the
>node placement. Either of them seem fine, but I do not quite understand what you mean by "but will have information about the node placement". Does it mean that it'll display like url_alias?
>Suggestions about how to make this as simple as possible are
>appreciated. In any case, to "port" the links , it would be handy to have the node id displayed somewhere (a tiny string at the bottom is OK). Opening each article in edit mode gives the object id, not the node id so that's no option to discover it. Or else an interface for contributors like the admin->content for this section (also for moving things around and/or deleting obsolete articles). Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Bård Farstad
|
Monday 09 June 2003 6:03:35 am
> Either of them seem fine, but I do not quite understand what you mean by
> "but will have information about the node placement". Does it mean that
> it'll display like url_alias?
Yes, if you have a node tag you can make it display the url_alias as a link. When you have an object you don't know which node placement to show ( of course you could show the main ). In any case, eZ publish should update the links when moving an object. This is no problem. However we do not use XML in the forums and many links would then be broken when a page moves. How should this be handled? --bård
Documentation: http://ez.no/doc
|
|
Paul Borgermans
|
Monday 09 June 2003 8:20:21 am
>In any case, eZ publish should update the links when moving an
>object. This is no problem. However we do not use XML in the
>forums and many links would then be broken when a page
>moves. How should this be handled? Difficult, but ....
--------I know this means quite some work------
Since path (node placement) is unfortunately not kept with object versions, some conversion should be done before moving anything. Links in forum messages should be converted to /content/view/full/<nodeid> upon posting if they refer to content on ez.no.
--------------------------------------- Actually, this is the universal nightmare of persistent content. The use of /content/view/full/node-id is probably the only way to go in the long term for content within one-and-ony-one site. One of the things to discuss in the future developments of ez publish is to how to use universal locators of content in general, even across sites. This is also one of the tough issues for W3C standardisation, allthough some of it is addressed in a down to earth approach: http://purl.oclc.org/ What we want to do is setting up something like that and integrate this into ezpublish. Perhaps not for every content object, but at least for some classes where a upon creation of a new object, a PURL is registred into the local as well as a central server. An ezpublish template operator could then be used to generate always the PURL link (for backwards compatibility --generate a PURL if one does not exist yet) together with a new object attribute delivering the very same PURL. Something for discussion at the summer camp I guess.... Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Gabriel Ambuehl
|
Tuesday 10 June 2003 1:25:42 am
Paul,
as to getting node id: the admin interface will show it to you when you hover over a link, the number at the end of the edit URL will be the node id. Sure, it isn't exactly straight forward but it works.
Visit http://triligon.org
|
|
Paul Borgermans
|
Tuesday 10 June 2003 1:38:55 am
Gabriel, Yes I know, but I doubt we'll getting access to the admin interface fo ez.no for editing the user contributed docs ;-) Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Jerry Jalava
|
Friday 13 June 2003 9:17:18 am
Just a thougt:
One good add to the url_alias would be converting Ä,Ö,Å's to A,O,A's and also special marks could be changed to _'s...
This would help alot when using other languages like finnish...
ie. Right now I have a link "hkkisen_psiinen" which should be like "häkkisen_pääsiäinen"... ;)
Regards,
Jerry
|
|
willy jansen
|
Wednesday 03 November 2004 6:25:27 am
This discussion took place a year ago.
Is there any news on this topic? Did this suggestion end up in the bin? I searched the website for "eznode" and get 0 results.
|