System module hook_init()

100%

System module hook_init()

✓ Published0🌍 Public

Last edited Mar 7, 2018

Created on Mar 7, 2018

This example shows Drupal’s `system_init()` function managing CSS assets and database slave handling during each page request. It calls `drupal_add_css()` to load system stylesheets with specific groups and `every_page` flags, while also checking `path_is_admin()` for admin-only CSS. The code then examines `$_SESSION['ignore_slave_server']` against `REQUEST_TIME` to conditionally call `Database::ignoreTarget()`, temporarily disabling slave database servers to avoid read lag after writes. It concludes by invoking `system_add_module_assets()` to include assets declared in module `.info` files.

AI-generated description

Similar vizzes

Loading thumbnail…

no page_alter

This example shows a Backdrop CMS module hook that conditionally loads JavaScript and CSS assets for code syntax highlighting on specific node types. It uses `hook_page_alter()` to check the current node’s type against configured enabled types, then calls `backdrop_add_css()` and `backdrop_add_js()` to include the Highlight.js library, a theme stylesheet, and a custom inline script that triggers `hljs.initHighlightingOnLoad()`. The rendering approach relies on server-side PHP logic rather than a client-side visualization library, with asset paths derived from `backdrop_get_path()`.

Aalexfinnarn

55% match

Loading thumbnail…

Gist 1b1889baaec2adffe574

This example demonstrates a WordPress theme’s strategy for optimizing CSS delivery by inlining critical styles and asynchronously loading the full stylesheet. It shows how PHP hooks like `wp_head` and `wp_footer` conditionally inject scripts, styles, and a cookie-based cache check. The code uses `file_get_contents` to embed JavaScript files such as `loadCSS.js` and `onloadCSS.js`, alongside a `<style>` block for critical CSS. A `noscript` fallback ensures the full stylesheet loads without JavaScript. The implementation relies on the `Roots\Sage\Assets` namespace and functions like `asset_path()` to resolve file paths.

GGolodhros

50% match

Loading thumbnail…

running some drush commands

This example shows a shell script that automates the setup and management of a Backdrop CMS site using Drush commands. It demonstrates the sequence of installing the site with a MySQL database, starting a local development server, and enabling a specified module. The code relies on the Drush command-line interface, invoking `drush si`, `drush backdrop-runserver`, and `drush en` with flags for database configuration and non-interactive execution. The script uses environment variables for the module name and targets a localhost port, with output redirected to suppress server logs.

Aalexfinnarn

49% match

Loading thumbnail…

Gist e41a467021a94517f5c22751e175aacc

This example shows a PHP routine that synchronizes link data for a bean entity between a Drupal site and its database, prioritizing link uniqueness and handling replication lag. It first ignores the slave database by setting a session variable and calls `db_ignore_slave()`, then queries the `linkchecker_link` table using `db_query` with a URL hash to check for existing links. Missing links are inserted via `drupal_write_record`, and the code adds records to the `linkchecker_bean` table using `db_insert`, wrapped in a `db_transaction` with rollback on exceptions. After processing, it clears the session variable to resume normal slave usage, demonstrating Drupal’s database abstraction and transaction handling.

Aalexfinnarn

48% match

Loading thumbnail…

user role config info hook

This example shows a Drupal-style configuration hook that defines user role settings for a site. It demonstrates how the `hook_config_info()` function registers two role prefixes, `developer` and `site_owner`, each with name and label keys and a shared group label. The code returns an array of prefix definitions, mapping each role to its metadata structure. It uses the Backdrop CMS configuration API, specifically the `config_info` hook pattern, to declare configurable items without any rendering or data visualization logic. The data source is the hardcoded PHP array of role definitions.

Aalexfinnarn

46% match

Loading thumbnail…

Gist 23705f481029d7e1cb22973540188d19

This snippet demonstrates a WordPress performance optimization technique by filtering the `style_loader_tag` hook to modify how stylesheet links are rendered. It shows the `add_rel_preload` function, which replaces standard `<link>` tags with preload directives that include an `onload` handler to swap `rel='preload'` to `rel='stylesheet'`, enabling asynchronous CSS loading. The code uses WordPress PHP APIs (`add_filter`, `is_admin`) and outputs a heredoc string with the HTML. It explicitly avoids altering output in the admin panel, targeting front-end performance only.

KKopylovVitalik

44% match

Loading thumbnail…

Remove WooCommerce related resources except on WooCommerce-based pages (products, cart, checkout, etc). Use on a testing environment before pasting this into your live website!

This code sample demonstrates how to selectively disable WooCommerce stylesheets and scripts on non-WooCommerce pages using WordPress PHP hooks. It shows a site optimization technique that checks for WooCommerce-specific conditions before dequeuing assets. The implementation uses the `wp_enqueue_scripts` action hook and WooCommerce conditionals like `is_woocommerce()`, `is_cart()`, and `is_checkout()` to determine page context, then removes targeted handles such as `woocommerce-general`, `wc-cart-fragments`, and `jquery-blockui`. The code runs on a testing environment before deployment to production.

CChrisb4

44% match

Loading thumbnail…

WYSIWYG to CKEdtior hooks

This example shows how a Drupal module integrates a custom code syntax highlighting button into CKEditor through two hook implementations. The first hook, `hook_wysiwyg_plugin`, registers a plugin button for the CKEditor instance, while `hook_ckeditor_plugins` defines the plugin’s JavaScript file, button label, and icon image path. The code specifies the plugin’s location via `backdrop_get_path()` and uses t() for translatable UI strings, demonstrating the API contract for extending editor functionality in Backdrop CMS.

Aalexfinnarn

43% match