| 开发者 |
fernandot
ayudawp |
|---|---|
| 更新时间 | 2026年5月2日 13:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
ayudawp_lightbox_selectors) that allows developers to customize CSS selectors to include or exclude specific elementslightbox-images-for-divi-enhanced folder to /wp-content/plugins/ directoryThe plugin will not activate and will show an error message explaining that either Divi theme or Divi Builder plugin is required.
No, this plugin is specifically designed to work only with the Divi ecosystem (Divi theme or Divi Builder plugin). It will not function with other WordPress themes.
The plugin will automatically deactivate itself and show an admin notice explaining why it was deactivated.
Yes, the plugin fully supports Divi 5. It works both in backwards compatibility mode (using Magnific Popup) and in native Divi 5 pages (using a lightweight built-in lightbox). No jQuery is required.
Yes, since version 2.2.0 the plugin handles both direct image URLs (e.g. photo.jpg) and WordPress attachment page links. The full-size image is resolved automatically from the embedded image element.
For advanced users and developers, the plugin provides an ayudawp_lightbox_selectors filter. You can use this filter in your child theme's functions.php file to add or modify the CSS selectors that the plugin uses to identify images. For example:
php add_filter( 'ayudawp_lightbox_selectors', 'my_custom_lightbox_selectors' ); function my_custom_lightbox_selectors( $selectors ) { $selectors[] = '.my-custom-module a'; // Add selector for custom module return $selectors; }
Yes, as long as you have the Divi Builder plugin installed and active, the plugin will work regardless of your active theme.
hrefattachment_id query parameter or have a path slug that matches the image file name<img> are now left untouched, restoring the original click behaviormagnific-popup.js and magnific_popup.css.et_pb_post_content) is now correctly recognized as an allowed content area
For older changelog entries, please check the changelog.txt file