| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
depricated by form API patch though. Hopefully helps migration.
|
|
|
|
|
|
| |
Usernames can now be themed; eg. an icon/avatar could be added.
TODO: update contributed modules + update the migration docs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
usual comment form, similar to what we did for nodes. This resulted lots of duplicate code removal. Also gave administrators the ability to change the author and timestamp of a comment. Also removed comment links from the bottom of the comment preview box (as we did for nodes)
Modifications: fixed breadcrumbs, tidied up delete confirmation page to be consistent with node deletions..
|
| |
|
| |
|
| |
|
|
|
|
| |
TODO: document the defaults in the PHPdoc comments.
|
|
|
|
|
|
| |
NOTE: this patch works well, but the improved node edit form still has
some rough edges. It is important that we continue to improve
usability. Give it a try.
|
| |
|
| |
|
|
|
|
| |
constants for readability.
|
| |
|
|
|
|
| |
after approval in the moderation queue.
|
| |
|
| |
|
|
|
|
| |
instead of the form functions. The unpublish selection actually didn't seem to work, so I removed it since we have delete. It should be implemented as a link anyway.
|
|
|
|
| |
should write guidelines for this -- maybe in the PHPDoc code of the _help hook.
|
| |
|
|
|
|
| |
nodes.
|
| |
|
| |
|
| |
|
|
|
|
| |
the history table anymore) are counted as new comments, since the timestamp retrieved from the history table is used to check for new comments (which is 0, if an entry was not found). This patch sets the timestamp used to check for new comments to the NODE_NEW_LIMIT value at least (which is when the history table was/should have been pruned).
|
|
|
|
| |
there are a required e-mail field. This field are, as far as i can see, not shown publicly. A user asked me about this and after confirming that it is not shown publicly I added a description that inform the users of this. I have included a patch that add the description "The content of this field is kept private and will not be shown publicly". This is the same description that is used by the profile module.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- permissions menu link updates in a number of modules help
- anchor link fix in distributed auth help
- "my account" link fix in user help
- spelling correction in tracker.module help
- I also changed 'admin/access/perms' to 'admin/access/permissions'.
|
| |
|
|
|
|
|
|
| |
referring page after completing a form.
(Moshe: the patch against node.module failed to apply.)
|
|
|
|
| |
comment.module.
|
|
|
|
| |
Goba: it would be nice if one of the core themes would showcase this functionality. ;-)
|
| |
|
|
|
|
| |
ability to define different types of markers (while retaining the old default behaviour of the new and required markers to look the same). Someone with enough time on his hands might be able to partition the new marker to a real new marker and a changed marker (since node_is_new() returns TRUE even if nodes changed, and not only when they are new). This is the base on which the new patch can be worked though.
|
|
|
|
|
|
| |
type) configuration page.
Modified the patch to remove some redundant code, to translate strings, and to better use the menu system.
|
|
|
|
|
|
| |
set, and it counted nodes with more than 1 comment as multiple nodes).
- Clean up various SQL queries: removing literally inserted data (db_escape_string is evil!), fixing single "%" which should be "%%", fixing integers being compared as strings.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We added a 'severity' column to watchdog():
watchdog($type, $message, $link) --> watchdog($type, $message, $severity, $link);
* Specify a severity in case you are reporting a warning or error.
* The $link-parameter is now the fourth parameter instead of the third.
TODO: document this in the upgrade guide.
|
|
|
|
|
|
|
|
| |
1) The different types of search, which used to be radio button options in the search form, are now subtabs of "search" (default "search/node"). This seems better from a UI point of view, but also has another advantage: modules which implement a custom search form (flexinode, project) can add it as a subtab of search. This means that all search forms will be located in the same place, and also without needing an extra api call to search.module.
2) The current code was a bit hackish, as the indexing of comments along with nodes was hardcoded in node.module. Instead, I created a nodeapi operation "update index" which allows modules to add more data for a node that is being indexed. Comments are now indexed using this mechanism and from comment.module, which is a lot cleaner.
3) The search results format was also hardcoded to include "N comments". I replaced this with a nodeapi operation "search result" and moved the comment code to comment.module where it belongs. This op is quite useful, as for example I also modified upload.module to add "N attachments" to a search result if any are present.
|
| |
|
|
|
|
| |
if we are in preview mode. We show the post button in preview mode even if there are form errors so that optional form elements (e.g., captcha) can be updated in preview mode.
|