> > This workaround would be ok for a restricted set of > > cases, but in a lot of applications you really would > > need to have something equivalent to a full symbolic > > link. Otherwise you would need to copy an article > > to a number of topic locations, which is certainly > > undesirable from the viewpoint of document maintenance, > > or alternatively have some more complex referencing > > methods outside of the built-in Midgard utilities. > > One solution could be to create a table (in another database) > that holds (topic, article) tuples to register articles > 'softlinked' to a given topic. The downside is that the > usual filtering and sorting won't apply to these links. Thanks for the suggestions, Jean-Pierre and Emile. I decided to use the following method: - Set up the primary article under the appropriate (secondary) topic; - Create a linking article under the primary topic. This article has the same title as the primary article, except that it ends with "<link>". In the extra1 field, enter the id of the primary article. Otherwise the linking article is empty. - When the linking article is fetched, detect "<link>" in the article title, then get the article in the id at $article->extra1 and make the appropriate variable substitutions prior to display. This way you get to preserve the sorting logic of mgd_list_topic_articles* (the linking article has the same title as the primary except for the terminating string and you can set its score). An ugly kludge? Definitely. I think this will turn out to be a common requirement, and I hope that eventually whoever is/will be working on this part of the Midgard code will implement the equivalent of a symbolic link that will be triggered by a flag dedicated to the purpose. Paul -- This is The Midgard Project's mailing list. For more information, please visit the project's web site at http://www.midgard-project.org To unsubscribe the list, send an empty email message to address [EMAIL PROTECTED]
