Using Delta and Context modules you can extend PM Vista to suite various use cases / needs.
All in all the modules that could be used to extend PM Vista are,
From time to time, you may want to use a newer or even older version of a module than what is included in a kit. That is expected and supported by utilizing the order Drupal allows overriding modules. Similar to how a .tpl file for a theme can override the version include with the base theme or a module by placing it in sites/all/themes/[YOURTHEMENAME], adding a module to sites/all/modules will override the version in profiles/[STARTERKIT]/modules.
The module is overridden if it is a newer or older version of the module. The ideal workflow is to open an issue to alert other developers working with the kits about why you needed a different version. If you need a newer version and you didn't find any conflicts or issues with other modules in the kit, other sites should test that by overriding to too. If there are no issues, the kit should be updated.
ONCE THE KIT IS UPDATED, YOU MUST REMOVE THE MODULE FROM SITES/ALL/MODULES OR IT WILL CONTINUE TO BE OVERRIDDEN.
When moving modules between profiles/[STARTERKIT]/modules and sites/all/modules, you may run into issues with modules that use Drupal's registry table. This happens more often if you are changing the location and version at the same time.
There are a few ways to work through these issues.
- drush rr - http://drupal.org/project/registry_rebuild
The Soundslides module allows the users to upload the soundslides project via media browser(provided by media module) in the form of a zip file and provides media formatters to render them.
For git you need the "GIT backend" module.
Here is an example of using GIT backend:
Step 1: create an bare GIT repository (skip this if you already have one)
git init --bare
Step 2: set up your Drupal site with that repository
- Enable the "Version Control API", "Commit Log" and "GIT backend" modules.
- Flush cache.
- Go to Configuration > Development > Version Control settings (url: /admin/config/development/versioncontrol-settings)
- Set "Git binary path". (Notice: Can be problems with Windows OS. On *nix OS there are no problems with path)
- Go to Content > VCS repositories > Add Git repository in the admin area. (url: /admin/content/versioncontrol-repositories/add-git)
- Repository name: "Test repo", or whatever.
- Repository root: "/path/to/repository/bare.git".
- For other settings follow fields descriptions(and check "Web viewer URL handler" because by default it's not set. Might it'll be fixed in closest time)
- Save the repository.
- Enable the "Commit messages" menu entry, or go directly to the "/commitlog" path.
$block = module_invoke('module_name', 'block_view', 'block_delta');<br/>
'module_name' = The machine name of the module (i.e. the module's folder name). This is true for core modules too, so for instance 'search', 'user' and 'comment' would all work here.
'block_delta' = The machine name of the block. You can determine what this is by visiting the block administration page and editing the block. The URL for editing a webform block, for instance, would be something like:
Drupal 7: admin/structure/block/manage/webform/*client-block-11*/configure
In this example, 'webform' is the module's name, 'client-block-11' is the block's delta.
Custom blocks will have module name of 'block' and a number for a delta, which you can also find by editing the block.
More information: http://drupal.org/node/26502