Parent Directory
| 
Revision Log
| 
Revision Graph
| Links to HEAD: | (view) (download) (annotate) |
| Sticky Tag: |
- Patch #598758 by stBorchert, sun, pwolanin, eigentor, TheRec, seutje: add link to the permissions and configuration page of each module from the module configuration page. Great team work!
#538660 by JacobSingh, dww, JoshuaRogers, adrian, Crell, chx, anarcat, and cwgordon7: Add a functioning Plugin Manager to core. Can you say module installation and updates through the UI? I knew you could! :D
- Patch #604618 by Crell, JacobSingh: create a common interface for Archive operations so we can handle .zip, .tar.gz.
#331180 by pwolanin and Rob Loach: Added pluggable smtp/mail framework.
- Patch #113614 by eaton, fago, et al: add centralized token/placeholder subsituation to core.
- Patch #486558 by PEAR, chx: add tar-support to Drupal.
- Patch #449198 by boombatower: cealn up test loading and related API.
- Patch #391340 by chx, dww, neclimdul, Crell, alex_b, et al: job queue API. The queue system allows placing items in a queue and processing them later. The system tries to ensure that only one consumer can process an item. Before a queue can be used it needs to be created by DrupalQueueInterface::createQueue(). Items can be added to the queue by passing an arbitrary data object to DrupalQueueInterface::createItem(). To process an item, call DrupalQueueInterface::claimItem() and specify how long you want to have a lease for working on that item. When finished processing, the item needs to be deleted by calling DrupalQueueInterface::deleteItem(). If the consumer dies, the item will be made available again by the DrapalQueueInterface implementation once the lease expires. Another consumer will then be able to receive it when calling DrupalQueueInterface::claimItem(). The $item object used by the DrupalQueueInterface can contain arbitrary metadata depending on the implementation. Systems using the interface should only rely on the data property which will contain the information passed to DrupalQueueInterface::createItem(). The full queue item returned by DrupalQueueInterface::createItem() needs to be passed to DrupalQueueInterface::deleteItem() once processing is completed. While the queue system makes a best effort to preserve order in messages, due to the pluggable nature of the queue, there is no guarantee that items will be delivered on claim in the order they were sent. For example, some implementations like beanstalkd or others with distributed back-ends like Amazon SQS will be managing jobs for a large set of producers and consumers where a strict FIFO ordering will likely not be preserved. The system also makes no guarantees about a task only being executed once: callers that have non-idempotent tasks either need to live with the possiblity of the task being invoked multiple times in cases where a claim lease expires, or need to implement their own transactions to make their tasks idempotent.
#320024 by Dave Reid: Replace hardcoded drupal_required_modules() with required = TRUE in .info files.
#319699 follow-up by Dave Reid: Simplify required module hiding in admin/build/modules.
#318984 by Xano and Dave Reid: Change 'Core - optional' to 'Core' in modules UI.
#318892 by justinrandell and chx: Add .install files to the list of files added to .info files.
- Patch #270508 by paul.levvik and pwolanin: usability improvement: image toolkits should not have to be copied.
- Patch #221964 by chx, dopry, webernet, moshe, webchick, justinrandall, flobruit et al. Can you say 'registry'? Drupal now maintains an internal registry of all functions or classes in the system, allowing it to lazy-load code files as needed (reducing the amount of code that must be parsed on each request). The list of included files is cached per menu callback for subsequent loading by the menu router. This way, a given page request will have all the code it needs but little else, minimizing time spent parsing unneeded code.
- Patch #221384 by webernet: update core compatibility to Drupal 7.
- Patch #146910 by dww: only allow enabling modules with the same Drupal core compatibility version.
- Patch #87298 by webchick, neil, dww et al: show version numbers on modules page.
- Patch #81740 by merlinofchaos, webchick, moshe, neclimdul et al: added package support to the modules page.
- Patch #80952 by earl, webchick, neclimdul et al: .info files
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.
| ViewVC Help | |
| Powered by ViewVC 1.1.2 |