As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
Assuming your code is running for a node page, the methods I see used most often in core/contrib modules are either using menu_get_object() or arg():
if ($node = menu_get_object()) {
// Get the nid
$nid = $node->nid;
@see commandes https://thinktandem.io/blog/2017/10/23/killer-d8-workflow-using-lando-and-platform-sh/
Lancer la commande lando behat à partir du dossier /tests.
Ou lancer la commande lando behat --config=tests/behat.yml à partir de la root.
find . -printf '%s %p\n'| sort -nr | head -10
| <?php | |
| /** | |
| * @file | |
| * Drupal site-specific configuration file. | |
| * | |
| * IMPORTANT NOTE: | |
| * This file may have been set to read-only by the Drupal installation program. | |
| * If you make changes to this file, be sure to protect it again after making | |
| * your modifications. Failure to remove write permissions to this file is a |
A basic install instance could be
site_name:
$ git log origin/master
// Update 2021
composer create-project drupal/recommended-project myproject -n or
composer create-project drupal/recommended-project:^8.9 myproject -n
cd myproject
lando init --source cwd --recipe drupal8 --webroot web --name myproject
lando start