- Removed all instances of '$user->nodes'.
- Committed Moshe's taxonomy patch - minus the node_compact_list() bit. It needs a bit more thought/work. This patch changes the links of taxonomy pages/feeds so update your custom code and themes accordingly!
Themes should now use "taxonomy_link("taxonomy terms", $node)" to get an array of taxonomy term links. The old construct is deprecated and should be changed.
// old theme blob:
if (function_exists("taxonomy_node_get_terms")) {
foreach (taxonomy_node_get_terms($node->nid) as $term) {
$terms[] = l($term->name, NULL, array(), "or=$term->tid");
}
}
// new theme blob:
if (module_exist("taxonomy")) {
$terms = taxonomy_link("taxonomy terms", $node);
}
// old URL:
http://foo.com/index.php?or=1,2
// new URL:
http://foo.com/?q=taxonomy/page/or/1,2
- forum: fixed link to new topic
- forum: new topic shows default forum correctly
- forum: first_new is back; the anchor didn't consider multiple pages
- forum: use standard pager, needed some changes/fixes to pager.inc
- forum: some cleanup
- forum: taxonomy hook
- renamed first_new to simply new
- added an optional parameter to pager_query for the count query
- used the optional count param for paging forum topics
- internal change: moving a topic doesn't duplicate the node anymore but just
changes the forum (term); no change in functionality, and shadow still
works (suggested by Dries). This probably also made some queries somewhat
lighter.
- bug fixed: anonymous users always saw "n (n new)" in the replies column
- updated pager help and moved from _help to phpdoc
- The href target for a new window is "_new", not "new".
- Generating <div> sections within <p> sections is forbidden by the
XHTML standard. Using just the right aligned <div> should be
sufficient and makes XHTML themes possible.
(Prove at http://blog.rompe.org/ )
- While parsing the header of an RSS feed one should be aware that
there may be more <title> tags in subsections and that POSIX regular
expressions are always gready. So make shure we don't get too much.
(If you agree that using PCRE instead of the POSIX ones would be
generally a good idea, then I am willing to make the patch, but for
now I didn't want to mix POSIX and PCRE in one file.)
(Prove at http://blog.rompe.org/index.php?q=import/feed/43 , try
this feed without my patch)
- Some RSS 2.0 feeds don't have a per item <link> section but have the
permalink embedded in the <guid> section. This is not perfectly
correct and the documentation mentions this possibility only in the
examples, but since Dave Winer himself implements it this way it
will happen more than once. So, if there is no link available and
the guid looks like an address, then use that one.
(Prove at http://blog.rompe.org/index.php?q=import/feed/22 , try
this feed without my patch)
- Don't only write eventually new Feed Header information into the
database but also use them immediatly. Reuse the $feed array that is
made for it.
- If a feed doesn't provide per item titles, make shure to not produce
defective markup by cutting the remainder of an entity. Instead of
just cutting off anything behing the leading 30 characters of the
cleaned description, it seems slicker to use up to 40 characters and
split on word boundaries, but not on "&" or ";".
(Prove also at http://blog.rompe.org/index.php?q=import/feed/22 .
This feed will have title tags starting on February 1st, but I
suspect many others without them out there.)
With this patch one could consider Drupals aggregator RSS 2.0 ready.
parent is supposed to exclude terms that are descendants of the current
term, to avoid creating cycles. However, the terms with the first few
term IDs are excluded instead. Patch by JonBob.
or "operation" link.
- Made the main page of the administration section show an overview of all
watchdog entries with such action link.
- Fixed typo in PostgreSQL database scheme.
Dries Buytaert