| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
- Removing gAMA chunk from xtemplate logo.png for less to avoid more gamma issues.
|
| | |
|
| |
|
|
| |
is set to unlimited and fixed up some code comments.
|
| |
|
|
| |
left-overs.
|
| |
|
|
| |
able to use this patch too.
|
| | |
|
| |
|
|
| |
bug less obvious.
|
| |
|
|
| |
the point.
|
| | |
|
| |
|
|
| |
attribute for links to provide a slightly more detailed explanation as to the purpose of a link or where it goes.
|
| |
|
|
|
| |
+ the confirmation before deleting a comment was missing a check_output.
+ after editing a comment, two pages were shown (two calls to theme('page',..)), replaced this by a drupal_goto.
|
| | |
|
| |
|
|
| |
should be simplified more.
|
| |
|
|
| |
in repeating the title).
|
| | |
|
| | |
|
| |
|
|
| |
update 80 (moving the profile fields to their own tables) no longer works.
|
| |
|
|
| |
to set book breadcrumbs for nodes that weren't books.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
which maintains a list of modules that have already been loaded in a static array, and will not load another module of the same name, or if the file does not exist.
Modules can be stored anywhere, as there is now a set of functions called module_get_filename, and module_set_filename .. which allow system_listing and module_list to specify the locations of the files.
A new function module_load_all() replaces the hardcoded includes in module_init, and loads all modules which have been enabled, using module_load.
module_listing no longer includes files itself, instead it just keeps the listing (and sets the filenames).
This patch is a requirement for the multisite configuration patch, as overriding modules are currently being loaded due to the only protection of loading them is include_once.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here's a new patch that unifies the node/52 and book/view/52 paths for nodes. It involves a small change to hook_view(), which is discussed first:
Currently hook_view() expects node modules to return a themed node. However, each module does this the same way; they modify $node as necessary, then call theme('node', $node) and return the result. We can refactor this so that the calling function node_view() calls theme('node') instead. By doing this, it becomes possible for hook_nodeapi('view') to be called after hook_view() where the node contents are filtered, and before theme('node') where the body is enclosed in other HTML. This way the book module can insert its navigation into the body right before the theming.
Advantages of this refactoring:
- I can use it for book.module to remove the extra viewing path.
- The function of hook_nodeapi('view') becomes more like hook_view(), as neither will expect a return value.
- We more closely follow the flow of other nodeapi calls, which usually directly follow their corresponding specific node type hooks (instead of preceding them).
- The attachment.module people could use it to append their attachments in a list after the node.
- Gabor could use it instead of his filter perversion for his "articles in a series" module.
- A little less code in each view hook.
- The content hook is no longer needed, so that means even less code.
Disadvantages:
- Any modules written to use nodeapi('view') could be affected (but these would all be post-4.4 modules).
- Implementations of hook_view() would need to be updated (but return values would be ignored, so most would work without updates anyway).
Now the patch takes advantage of this API shift to inject its navigation at the end of all book nodes, regardless of the viewing path. In fact, since the paths become identical, I've removed the book/view handler entirely. We should probably provide an .htaccess rewrite for this (one is still needed for node/view/nn anyway). At the same time, there is a check in book_block() that shows the block appropriately on these pages.
|
| |
|
|
|
|
|
|
| |
The headers stored for cached pages ended in a newline, which caused header("") to get called when serving the page.
On some PHP versions (happens on 4.3.3 at least, but not in 5.0), PHP adds a blank header to the HTTP request (i.e. just \r\n) which ends HTTP headers prematurely and adds a newline at the beginning of the page.
This was not an issue before because we output HTML. Now that we have GZip compression, this bug caused corruption of the output. :P
*phew*
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
GPL). The main benefit here is that timezones are handled properly (I have been noticing increasing complaints about that). I tested with a few feeds of different time formats and time zones and everything appeared correctly in my site's local time. Making this another function adds the benefit of parsability by other RSS (or other contexts) and RSS extension handling functions, where the W3C DTF is recomended.
|
| |
|
|
|
|
|
| |
- Restoring background coloring for the watchdog logs (was broken)
- Making watchdog backgrounds lighter, makes it easier on the eyes and improves readability.
- Adjusted the spacing between items on the frontpage a bit to be clearer.
- Fixed the vertical stretching of table rows with form controls in them.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
db_next_id().
|
| | |
|
| |
|
|
|
|
| |
Currently pager_query() is the black sheep of the database query family, because it does not allow for printf-style arguments to be inserted in the query. This is a problem because it introduces developer confusion when moving from an unpaged query to a paged one, and it encourages substitution of variables directly into the query, which can bypass our check_query() security feature.
This patch adds this ability to pager_query(). The change is backwards-compatible, but a couple calls to the function in core have been changed to use the new capability.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
- #8193: Moving the two instances of the timezone list into a function.
- #3859: Adding drupal_goto for module/theme/settings pages. Aside from general drupal_goto usability, this fixes the bug of menu items not immediately appearing after enabling a module.
|
| |
|
|
| |
PostgreSQL
|
| |
|
|
| |
'false' in this case)
|
| |
|
|
| |
in the name.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
else's account.
|
| | |
|
| |
|
|
| |
files consistent with Drupal standards, and adds a wealth of Doxygen-style comments to aid developers in writing solid database access code using the API.
|
| |
|
|
| |
additional menu's were never displayed, but were saved. Only the last custom menu was displayed.
|
| |
|
|
| |
if "user_register" was set to 0.
|
