load the most recent revision that matches the specified conditions.
Like that we can load the last good revision of a book page using the
line: book_revision_load($page, array("moderate" => 0, "status" => 1)).
Updating your own blog entry will demote it (if promoted),
and will queue it in the moderation queue for promotion.
If a node administrator updates his own blog entry through
the blog update mechanism that regular users use, then he
will be treated as a regular user and his blog entry will
be demoted. But when an administrator updates blog entries
through the admin pages, they will not be changed unless
explicitly specified.
- Bugfix: the "Edit comments" part of the node administration pages did not
display the correct comments.
- Bugfix: somethimes, update in a book page would mess up the book.
- Improvement: when "node administrators" update a book page through the
"update this book page"-link (like regular users do), their update will
be subject to moderation.
- Improvement: made some intermediate changes to the filter mechanism. Needs
more work.
- Made the /comment links/ jump to the comments instead of to the top
of the page.
- Replaced the "Add comment"-button by a "add new comment"-link.
(This should make UnConeD jump up and down of wild excitement.)
- Moved all comment related logic from theme.inc and node.module to
comment.inc and comment.module (where they belong).
- Added some links to ease the site's usability/navigation.
as this breaks revisions.
- modified link_node() to take a third parameter $main, which will be passed on
to _link hooks. This lets modules decide which links a node will get when
shown on the main page, or when not.
- updated themes to use the new syntax.
+ Made the filters work again!
+ There is one strange thing that I can't track down though: for some
reason, "^M" characters (?) are padded after newline ("\n" and / or
"\r") characters.
+ Re-introduced and re-wrote the book admin pages; there is a separate
page for every book and a page with all "orphan pages" (= pages that
got de-linked).
+ Updated the documentation to use a Jabber or Drupal IDs instead of
Deplhi IDs (as delphi.module won't be part of the default distro).
Drupal and Jabber authentication make a better example.
+ added missing localization / t() functions in
user_validate_authmaps()
+ applied coding convention:
* fixed indentation
* removed "EOF"; and <<EOFs from user module
* changed some HTML into XHTML: use small letters, quote
attributes
* quoted some array indices: $edit[foo] --> $edit["foo"]
+ removed some useless sprintf()'s
+ removed hard-coded references to drop.org.
+ I don't think the authentication methods should /know/ there help
link. Instead, the user module should now where to find the help
(it does by knowing the hook to look for), and it is the user
module that should take care of exporting the help to the preferred
location:
* removed the "link" field from the $info field in drupal_info
and jabber_info; it wasn't used anyway?
+ removed the "maintainer" and "maintaineremail" from the auth
modules; we don't keep this info in the other modules either so
I don't see a reason to do so here.
+ made some improvements to the node access checks
- queue module:
+ form()-ified the queue module and added some extra information
or guidelines
+ added a few missing translations
+ ...
+ Added the "delete node"-link: apparently it got lost during the last
commit. Odd.
+ Changed "Edit node" to "Edit <node_name>" on the 'edit node'-page of
the admin section. (There a 4 "Node"s that still need to be removed
though.)
+ Updated the initial submission page (the old submit.php) to include
some descriptions.
+ Changed node_form() to use good ol' tables instead of div/CSS-tags.
+ Revised the "revision API": I think we have both an easy and powerful
API now that should make everyone happy.
+ Improved the usability of the rollback functionality a bit.
+ Removed the "view node" link from the "node overview" page in the
admin section and added a "delete node" link instead.
+ Added a few missing translations; there might be missing more
translations though.
- book.module:
+ Made the book module use the "revision API" instead of having it poke
and use the innards and underlying details of the revision system.
- queue.module:
+ Made the queue module use the improved revision number.
- module.inc:
+ Applied Moshe's patch: added more arguments to module_invoke()
- mail-to-sql.pl:
+ Added support for more header fields and for folded fields
Notes:
- no database updates required
+ fixed a typo in node_load(): it should be faster now
- book module:
+ removed the functions book_parent() and book_parent_query() as
they were no longer needed. Gerhard & co: this should fix the
occasional SQL errors you get, and should improve performance.
+ made the "next", "previous" and "up" links work correctly ...
+ XHTML-ified the code
+ added some missing translations
I'm working on the book module now to make it possible to update book
pages.
Drupal to display submission guidelines, or any other kind of explanation
such as "NO TEST POSTS", for example.
- Added node versioning: it is possible to create revisions, to view old
revisions and to roll-back to older revisions. You'll need to apply a
SQL update.
I'm going to work on the book module now, so I might be changing a few
things to enable collaborative, moderated revisions - but feel free to
send some first feedback, if you like.
- Added some configuration options which can be used to set the minimum
number of words a blog/story should consist of. Hopefully this will
be usefull to stop the (almost empty) test blogs.
- Various improvements:
+ Fine-tuned new node permission system.
+ Fine-tuned the functions in node.inc.
+ Fine-tuned some forms.
+ XHTML-ified some code.
+ introduced basic node permissions ("create", "delete", "update" and
"view") at the node level: it's up to the "<$node->type>_module" to
hide gory details (if any).
+ made the "blog it"-feature in the blog and import module work with
the new node system, in specific with the new centralized forms.
+ made it possible to update blogs.
+ made the page module work with the new node system.
+ various smaller improvements.
variables.
Example: set site_frontpage to "node" and site_frontpage_extra to
"$meta = 'news'" and only nodes with that meta tag will be displayed on
your main page.
This requires some internal knowledge of how the various modules work
and what settings can be passed to <module>_page() functions.
Dries Buytaert
Kjartan Mannes
Steven Wittens
natrak