BLOCKGLOW · VERSION 2.1.0
BlockGlow Feature Documentation
Find the right tool, follow the steps, and know what to check.
BlockGlow documentation
On this page
- Custom CSS and block IDs
- Styles, selectors and responsive helpers
- Block animations
- Content Slider and Filter blocks
- Filter a Query Loop
- Related Posts
- Table of Contents
- Social Share
- LCP detection and preloading
- Uploads Cleanup and oldest images
- Rename an image filename
- Protect Simple Membership forms
- Troubleshooting and maintenance
Custom CSS and block IDs
Enable the editor in BlockGlow → Enhance. Select a block and open its BlockGlow inspector panel. Use standard Gutenberg controls first, then add CSS for styling those controls do not cover.
Each styled block has a BlockGlow ID. New IDs use bg- followed by six characters. Duplicated or copied blocks receive distinct IDs while their custom CSS is copied and retargeted. Existing IDs may be longer. Avoid editing IDs manually.
& {
padding: clamp(20px, 4vw, 40px);
}
& a:hover {
text-decoration: underline;
}
@media (max-width: 600px) {
& { border-radius: 12px; }
}BlockGlow scopes & to the selected block. The editor also accepts selector as its block placeholder. A descendant selector such as & h2 styles headings inside that block. Generated CSS is managed under Enhance; inline output is a fallback when file generation is unavailable.
Styles, selectors and responsive helpers
- Styles: search theme colors, fonts, font sizes, gradients and shadows. Clicking a preset inserts its CSS variable at the editor cursor. Color choices show their color values.
- Selectors: insert states such as :hover, :focus-visible and :active, or pseudo-elements such as ::before and ::after. Add declarations inside the selector’s braces.
- Responsive: insert a media-query starter, then adjust its condition and CSS to suit the layout.
- !important: insert the priority marker when needed. Prefer a suitable selector before overriding the cascade.
- Live preview: use Render CSS in editor to preview changes. Save the page and check the actual front end before considering the work finished.
Block animations
Select a block and use the animation button to open its settings. Choose an effect, start on page load or when visible on scroll, then set duration, delay and whether it plays once. Replay the preview before saving.
Keep important content understandable without motion. BlockGlow respects the visitor’s reduced-motion preference. Avoid adding animation to every block or delaying content the reader needs immediately.
Content Slider and Filter blocks
- Content Slider: add Slide blocks, then place any supported Gutenberg blocks inside each Slide. Configure vertical or horizontal movement, spacing, viewport and speed. You can hide controls, place them above or below, and choose scrollbar visibility.
- Slider preview: autoplay is a front-end behavior. Hover, focus and user interaction can pause movement; use visible controls where readers need a dependable way to pause. Reduced-motion preferences are respected.
- Filter: create a manually assembled content grid. Put blocks inside each Filter Item and enter its categories in the sidebar. The parent block creates category buttons. Adjust its columns and result count.
- Choose the right filter: Filter handles items you build inside it. Query Loop filtering searches matching WordPress posts or custom post types. It does not filter the manually assembled items.
Filter a Query Loop
- Insert a Query Loop and choose its post type and card layout. In List View, select the outer Query Loop, not Post Template or an individual card.
- Open BlockGlow Filters and enable Enable resource filters. Use a Custom query, with inheritance off.
- Choose a Button taxonomy for category-style buttons and, optionally, a Dropdown taxonomy for a second filter. The taxonomy must belong to the chosen post type.
- Toggle Search and Sort controls as needed. Set the All items label. Save and preview.
- Change a filter and check results and pagination. Search and select controls apply automatically, so there is no Apply button. Test Enter in the search field as well.
Filters retain your Query Loop card layout and narrow the query’s existing constraints. If no items match, show a helpful Query No Results message. Public filtering is not membership access control: protected content still needs its membership plugin’s rules.
Related Posts
Insert BlockGlow Related Posts, a Query Loop variation, in a single-post layout or template. Its sidebar can match the displayed article by categories, tags, either, or both. Customize the cards using normal Query Loop blocks.
The current article is excluded. Matching requires assigned terms; a missing category or tag can correctly produce no results. Existing explicit taxonomy filters remain additional constraints. Check an actual article on the front end rather than relying on a template preview alone.
Table of Contents
Add BlockGlow Table of Contents to a page or a single-post template that contains a Post Content block. Choose the heading levels, title, numbering and optional collapsible display. The front-end script builds links from the displayed article’s headings.
Clicking an entry scrolls smoothly unless reduced motion is requested. The selected list item receives is-active; its link gets aria-current="location", and the target heading receives bg-toc-heading-active. The first entry starts active.
& li.is-active > a {
font-weight: 700;
text-decoration: underline;
}If the contents list is hidden, check that the displayed Post Content has headings within the selected levels and that JavaScript is loading.
Social Share
Insert BlockGlow Social Share in your article or single-post template. Choose the available sharing options, including Copy Link and More sharing options, then adjust icon colors and backgrounds in the block settings.
Sharing uses the displayed article’s URL. Copy Link requires browser clipboard permission and a secure context such as HTTPS. The native More sharing sheet depends on browser and device support. Test the actual page and keep descriptive button labels.
LCP detection and preloading
LCP, or Largest Contentful Paint, measures when the largest visible content element appears. A preload can help a suitable resource load earlier; it does not fix slow hosting or guarantee a faster page.
- Open BlockGlow → Optimize and enable LCP preload for the post types you want to manage.
- Save the page, then open its front end while signed in as a user who can edit it. Anonymous visitors cannot update the saved detected resource.
- Use the LCP analysis or re-analysis controls after changing the hero image or above-the-fold layout.
- Review the saved resource and compare performance before and after. Remove stale or unnecessary preloads.
Detection depends on browser support and an eligible resource. A text-based LCP may not produce an image URL. Avoid preloading several competing images.
Uploads Cleanup and oldest images
Open BlockGlow → Optimize → Uploads Cleanup. Back up your database and uploads first. A scan identifies candidates for review, not proof that an image is unused.
- Choose the scan options, including whether to include Media Library images and obsolete generated-size files.
- Choose 10, 20, 50 or 100 images per load. Start the scan and use Load more to continue.
- Review thumbnails and usage information. Select all applies only to currently loaded images, not every file in uploads.
- Use the oldest-images view to inspect older media and its detected page, pattern or template references. Age alone does not make an image unused.
- Choose only items you are confident you no longer need, then confirm deletion. A Media Library deletion also removes the attachment record and related generated files.
Unused-file scanning targets supported image types older than 30 days in dated upload folders. It checks stored filenames and image IDs across content, templates, fields, settings and active theme files. Plugin-managed folders are excluded. Dynamic, remote, external and plugin-generated references may be missed.
A responsive size can still be used through srcset even when it is absent from the main image URL. The optional derivative audit protects metadata-tracked sizes and current registered sizes, and only offers obsolete unreferenced files as candidates.
Why is an image marked for manual review?
A missing, recent or unsafe related file, changed metadata, or a reference-check failure can block removal. Read the card’s issue label, inspect the attachment in Media Library and keep it until its references and paths are understood. Do not bypass the safety check by deleting files blindly.
Daily background pre-scan prepares saved results in cron batches and never deletes images automatically. If WordPress traffic cron is disabled, a server or Docker cron runner must process scheduled events.
Rename an image filename
- Back up the database and uploads. Enable image filename renaming in BlockGlow → Optimize, then reload the block editor.
- Select an Image block and open Image filename – BlockGlow. Enter a concise descriptive name and preview the proposed changes.
- Review affected files, then confirm. The tool renames eligible originals and generated sizes and updates stored URLs while keeping the attachment ID, alt text and caption.
- Clear relevant caches and check every important page that shares the image. Update external or hard-coded links manually where necessary.
Old-URL redirects are not created. Shared uses are affected; external websites may still point to the old URL. Unsafe paths, conflicting filenames or unsupported stored data can require manual review. A filename is only one small part of image SEO; useful alt text and appropriate image sizing still matter.
Protect Simple Membership forms
Open BlockGlow → Protect. Enable the honeypot for supported Simple Membership forms. To use Turnstile, create Cloudflare Turnstile site and secret keys for your hostname, enter them in the settings and enable the feature.
Test registration and other supported forms while signed out, including on mobile. Keep secret keys private. Cloudflare handles challenge and verification requests when Turnstile is enabled; review its privacy terms before using it. Other form plugins are not automatically protected by this integration.
Troubleshooting and maintenance
My CSS is saved but not visible
Check the selected block and feature toggle, save the page, and inspect the front end. Look for selector errors and competing CSS. Clear page/CDN caches. Check generated-file permissions if styles cannot be written. Do not delete all generated CSS as a first troubleshooting step.
A block behaves differently in the editor
Sliders, filters, sharing and the contents list need a front-end preview for their full behavior. Check browser console errors and ensure optimization tools have not delayed or blocked their scripts. Test one change at a time on staging.
Where do I ask for help?
Request help with setup or report a reproducible issue. Include versions, steps and expected versus actual behavior.
