Blogger, the well-known public weblog service, provides an application programing interface (API) to allow remote procedure calls (RPC) to the Blogger service. Drupal supports this Blogger API, which means that many remote clients (e.g. Radio, TextRouter, Blogbuddy, Bloggar,PerlyBlog), may post to Drupal. These clients provide a bevy of interesting capabilities like offline composing, spellcheck, and WYSIWYG editing; many folks prefer to blog with a client application over typical web forms. By supporting the Blogger API, Drupal grows grander than a web site engine, it's a content accepting machine™. -
The Blogger RPC API uses the XML-RPC protocol for communicating with the outside world. XML-RPC, originally developed by Dave Winer of UserLand Software, is a simple XML-based RPC specification ideally suited to the web. Drupal also uses XML-RPC for several other tasks (e.g. notifiying weblogs.com of blog updates and making/accepting "user", "op" => "help")) ?> requests)
+The Blogger RPC API uses the XML-RPC protocol for communicating with the outside world. XML-RPC, originally developed by Dave Winer of UserLand Software, is a simple XML-based RPC specification ideally suited to the web. Drupal also uses XML-RPC for several other tasks (e.g. notifiying weblogs.com of blog updates and making/accepting "user", "op" => "help")) ?> requests)
Book pages are a special, powerful node type. These nodes are specifically designed to be included in a book. Their special power comes from the bilility to embed PHP within the body of the page. This capability is only offerred to administrators, since malicious users could abuse this power. In addiiton, book pages contain a log message field which helps your users understand the motivation behind an edit of a book page. Each edited version of a book page is usually stored as a new revision of a node. This capability makes it easy to revert to an old version of a page, should that become desirable.
-Like other node types, book submissions and edits may be subject to moderation, depending on your configuration. Similarly, books use "user", "op" => "permission")) ?> to determine who may read and write to them. Only administrators are allowed to create new books, which are really just nodes whose parent is <root>. To include an existing node in your book, click on the "administer"-link in that node. At the bottom of this administration page, click on the edit book outline button. This enables you to place the node wherever you'd like within the book hierarchy. To add a new node into your book, use the create book page link.
+Like other node types, book submissions and edits may be subject to moderation, depending on your configuration. Similarly, books use "user", "op" => "permission")) ?> to determine who may read and write to them. Only administrators are allowed to create new books, which are really just nodes whose parent is <root>. To include an existing node in your book, click on the "administer"-link in that node. At the bottom of this administration page, click on the edit book outline button. This enables you to place the node wherever you'd like within the book hierarchy. To add a new node into your book, use the create book page link.
-Administrators may review the hierarchy of their books by clicking on the "book")) ?> in the adminstration pages. There, nodes may be edited, reorganized, removed from book, and deleted. This behavior may change in the future. When a parent node is deleted, he may leave behind child nodes. -These nodes are now orphans. Administrators should periodically "book", "op" => "orphan")) ?> and reaffiliate those pages as desired. Finally, administrators may also - "book", "op" => "feed")) ?> to a single, flat HTML page which is suitable for printing.
+Administrators may review the hierarchy of their books by clicking on the "book")) ?> in the adminstration pages. There, nodes may be edited, reorganized, removed from book, and deleted. This behavior may change in the future. When a parent node is deleted, he may leave behind child nodes. +These nodes are now orphans. Administrators should periodically "book", "op" => "orphan")) ?> and reaffiliate those pages as desired. Finally, administrators may also + "book", "op" => "feed")) ?> to a single, flat HTML page which is suitable for printing.
In order to view the nodes associated with a term or a collection of terms, you should browse to a properly formed URL. For example, see "node", "or" => "1,2"), "module"); ?>"> "node", "or" => "1,2"), "module"); ?>. Taxonomy URLs always contain a term ID or list of term IDs at the end of the URL (aka querystring). You may learn the term ID for a given term by hovering over that term in the "taxonomy")) ?> page in the Admin and noting the number after the querystring parameter called tid. If you wish to see nodes from a collection of term IDs, separate each term ID with a comma. Also, the name of the querystring parameter may be or or and: or shows nodes which appear in any of the term IDs while and shows nodes in all the specified term IDs. Thus, or is less specific than and.
+In order to view the nodes associated with a term or a collection of terms, you should browse to a properly formed URL. For example, see "node", "or" => "1,2"), "module"); ?>"> "node", "or" => "1,2"), "module"); ?>. Taxonomy URLs always contain a term ID or list of term IDs at the end of the URL (aka querystring). You may learn the term ID for a given term by hovering over that term in the "taxonomy")) ?> page in the Admin and noting the number after the querystring parameter called tid. If you wish to see nodes from a collection of term IDs, separate each term ID with a comma. Also, the name of the querystring parameter may be or or and: or shows nodes which appear in any of the term IDs while and shows nodes in all the specified term IDs. Thus, or is less specific than and.
Every term, or collection of terms, provides an RSS feed to which interested users may subscribe. The URL format for an sample RSS feed is "node", "op" => "feed", "or" => "1,2"), "module"); ?>"> "node", "op" => "feed", "or" => "1,2"), "module"); ?>.
diff --git a/modules/user.module b/modules/user.module index bc989c7882f..2791895a6de 100644 --- a/modules/user.module +++ b/modules/user.module @@ -1718,7 +1718,7 @@ roles: Changes made here take effect immediately. Also, administrators may make profile and preferences changes in the Admin Center on behalf of their users.Module developers are provided several hooks for adding custom fields to the user view/edit pages. These hooks are described in the Developer section of the Drupal Handbook. For an example, see the jabber_user() function in /modules/jabber.module.
Drupal is setup so that it is very easy to add support for any external authentication source. You currently have the following authentication modules installed ...
- " . module_invoke($module, "info", "name") . ""; @@ -1929,7 +1929,7 @@ function user_help_devel_da() { and Drupal_support mailing lists. You might also want to post a story on Drop.org.Extra credit: use the hotlist.module to provide Julia users a mechanism for bookmarking their favorite recipes.
- \ No newline at end of file diff --git a/themes/goofy/goofy.theme b/themes/goofy/goofy.theme index 5df9772a949..3c938f96c24 100644 --- a/themes/goofy/goofy.theme +++ b/themes/goofy/goofy.theme @@ -176,7 +176,7 @@ function c(subject,mod,author,date,body) {document.writeln("