Vanja Bertalan wrote:
> There are lots of hard-coded link in the example site which don't seem
> flexible. ie. $article = mgd_get_article(15); on the homepage of example
> site presumes that we know the ID of the article and that it won't get
> deleted.
> Same thing with groups, if we test mgd_is_member(hardcode), we pretty much
> depend on particular group not to be deleted or something.
1.2.6 (now in beta) has functions to select/get objects by their name
instead
of IDs.
> Anyway, I thing that mapping dynamic content to pages should be explained.
> Maybe I'm missing the obvious here...thoughts?
The pages will use Midgard/PHP code to retrieve data from the content
trees
and display it.
> BTW anything new with the manual? Chapters 5.4, 5.5, 5.6, 6 and 7 would
> be...eh...a relief 8))
The Manual is being reworked extensively by Ron Parker now. I'm sure he
won't
mind sharing the workload, so if anyone feels inclined to write parts of
the
manual, don't hesitate. If you feel you don't understand enough of
midgard to
write for the manual, so much the better. You'll approach the with a
fresh
perspective and the techies (like myself) will be able to fill in the
details
when there are questions.
Emile
--
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]
