A custom, REST-based API that returns JSON for various content from the Drupal CMS.
$queue_factory = \Drupal::service('queue'); | |
$queue_manager = \Drupal::service('plugin.manager.queue_worker'); | |
$queue_worker = $queue_manager->createInstance('queue_name'); | |
$queue = $queue_factory->get('queue_name'); | |
$item = $queue->claimItem(); | |
$queue_worker->processItem($item->data); |
# Lando version is at least +3.0 | |
name: drupal-nine | |
recipe: drupal9 | |
services: | |
appserver: | |
webroot: web | |
xdebug: debug | |
config: | |
php: .vscode/php.ini |
These are instructions for setting up git to authenticate with GitHub when you have 2-factor authentication set up. This authentication should be inherited by any GUI client you are using. These are intentionally brief instructions, with links to more detail in the appropriate places.
-
Download and install the git command-line client (if required).
-
Open the git bash window and introduce yourself to git (if required):
git config --global user.name 'Firstname Lastname' git config --global user.email '[email protected]'
# Defaults / Configuration options for homebridge | |
# The following settings tells homebridge where to find the config.json file and where to persist the data (i.e. pairing and others) | |
HOMEBRIDGE_OPTS=-U /var/lib/homebridge | |
# If you uncomment the following line, homebridge will log more | |
# You can display this via systemd's journalctl: journalctl -f -u homebridge | |
# DEBUG=* |
Thanks to HAP-NodeJS
Service | UUID |
---|---|
Accessory Information | 0000003E-0000-1000-8000-0026BB765291 |
Air Quality Sensor | 0000008D-0000-1000-8000-0026BB765291 |
Battery Service | 00000096-0000-1000-8000-0026BB765291 |
Bridging State | 00000062-0000-1000-8000-0026BB765291 |
One would expect that a preferred menu link item would be that link item in a menu which is the default or primary menu link item for any particular path where more than one menu link exists in the same menu with the same link path. For example, when you create a new node instance which allows for menu link creation within the node edit form, it would be expected that when the node is fully loaded (therefore contains the property menu
as an array which is loaded via the invocation of hook_node_prepare
that is implemented by the menu module) the $node->menu
represents the preferred menu link for this node. While we can significantly rely on this method for any node's menu link when retrieved via a node object ($node->menu
), we cannot expect to be the same as what may be returned from menu_link_get_preferred('node/' . $node->nid)
. So which is the the correct preferred menu link?
With the expectation that $node->menu
represents the preferred menu link for th
dependencies[] = ctools | |
; Views Handlers | |
files[] = views/mymodule_handler_handlername.inc |