preloader

PublishPress Blocks plugin review and common issues

PublishPress Blocks is used for building pages and layouts with WordPress blocks instead of a full page builder. In most cases, it fits business sites better than building the same workflow from scratch too early. A common issue is that styles drift or layouts shift when theme CSS and block styles are not working together. This usually happens when settings overlap with themes, optimization tools, or other plugins already on the site. It can save time, but it still needs testing on a staging site before major changes go live. From experience, PublishPress Blocks works best when the setup stays focused and the main settings are documented. It is useful in production, but it still needs updates, reviews, and periodic cleanup.

PublishPress Blocks plugin review and common issues

What is PublishPress Blocks plugin?

Header Footer Code Manager (HFCM) is a free WordPress plugin for inserting scripts, tracking codes, and custom HTML/CSS/JavaScript into the header or footer of WordPress pages — without editing theme files. With over 500,000 active installations and a 4.9-star rating, it is the straightforward solution for tasks like adding Google Analytics, Facebook Pixel, TikTok Pixel, Google Tag Manager, custom fonts, or any script that needs to appear in specific page sections.

HFCM’s interface is organized around “code snippets” that each have a placement location (header, footer, or specific content position), a scope (sitewide, specific posts/pages, specific post types), and the code itself. A changelog feature tracks changes made by each admin user, which is valuable for teams where multiple people manage tracking scripts. The plugin can also inject code into specific body positions, not just header and footer.

For users who need only header/footer script injection on a single site without the broader snippet management features of Code Snippets or WPCode, HFCM’s focused simplicity is an advantage. It does not support PHP snippet execution — it is specifically designed for HTML, JavaScript, and CSS injection. This limitation makes it safer than PHP-capable plugins for non-developer users, as misconfigured HTML cannot break WordPress the way a bad PHP snippet can.

Need Help With PublishPress Blocks Setup, Troubleshooting, or Customization?

Need help with PublishPress Blocks? Whether you are dealing with errors, broken functionality, styling problems, plugin conflicts, or advanced customization, we can help you fix the issue and get the plugin working properly on your WordPress site.

Get PublishPress Blocks Expert Help

Key Features

  • Insert HTML, CSS, JavaScript, and other code into header or footer
  • Sitewide or page-specific script injection
  • Support for all post types, specific pages, or category-specific injection
  • Snippet changelog showing who made each change and when
  • Enable/disable individual snippets without deletion

Pros & Cons

Pros

  • Extremely simple interface — fastest solution for adding tracking pixels without theme editing
  • Changelog tracking is valuable for multi-admin sites where tracking script management accountability matters
  • No PHP execution reduces the risk of site-breaking mistakes

Cons

  • No PHP code execution — not suitable for functional WordPress customizations
  • Less configuration flexibility than WPCode or WPCodeBox

Free vs Premium

Completely free. No paid version.

Common Problems & Fixes

A script added in HFCM header is not appearing in the page source — the tracking pixel code is missing. How do I verify it is being output?

Check: (1) the snippet is enabled in HFCM → All Snippets (active status); (2) the scope is set to include the current page — “All Pages,” specific post types, or the specific page; (3) view the page source (Ctrl+U) and search for a unique string from your snippet — this bypasses browser caching; (4) clear all caches — a cached page may not include recently added HFCM snippets; (5) HFCM hooks into wp_head() and wp_footer() — themes that do not call these WordPress functions will not output HFCM snippets.

HFCM is inserting a script on all pages but I need it only on the WooCommerce checkout page. How do I restrict it?

In the HFCM snippet settings, change the Scope from “All Pages” to “Specific Page” and select the WooCommerce Checkout page from the page dropdown. HFCM will then only inject the script when that specific page is being served. For targeting based on URL patterns or conditions beyond specific page selection, consider using WPCode which provides more sophisticated conditional logic including WooCommerce-specific conditions (is_checkout(), is_cart(), etc.) through its condition builder.

The HFCM changelog is not showing recent changes — edits by team members are not being recorded. How do I verify changelog is working?

HFCM’s changelog records changes when snippets are saved through the HFCM admin interface. If changes are not recorded: (1) the changelog only records changes made through HFCM’s own edit screen — programmatic changes (WP-CLI, direct database edits, REST API) are not logged; (2) verify the user making changes is logged in with a WordPress account (not anonymous); (3) check if a caching or performance plugin is interfering with the save operation; (4) the changelog view may need a page refresh to show the latest entries.

Customization & Developer Notes

How do I use HFCM to add Google Tag Manager to a WordPress site?

Create two HFCM snippets: (1) Header snippet — paste the GTM script provided by Google (the tag portion) and set placement to "Header"; set scope to "All Pages"; (2) Body snippet — paste the GTM portion and set placement to "Body (after tag)"; set scope to "All Pages." Save and enable both snippets. Google Tag Manager will now be active on all pages. Test using Google Tag Manager's Preview mode and verify the GTM container is firing correctly on your pages.

How do I add a different Facebook Pixel for different sections of a WooCommerce store using HFCM?

Create separate HFCM snippets for each tracking goal: (1) Main pixel — active on All Pages, contains the base Facebook Pixel initialization code; (2) Purchase event pixel — scope set to “Specific Page” → Order Received/Thank You page, contains the Purchase event tracking code; (3) ViewContent event — scope set to specific product post type, contains ViewContent event code. This precise event placement sends the right Facebook pixel events to the right pages, enabling more accurate conversion tracking and remarketing campaign optimization.

Frequently Asked Questions

Is HFCM better than just using Google Tag Manager for tracking script management?

Google Tag Manager (GTM) is more powerful for tracking script management at scale — it handles multiple tags from a single GTM snippet, provides a testing/preview interface, and allows non-developers to add tracking without WordPress admin access. HFCM is simpler for adding a few scripts directly without GTM overhead. For sites with one or two tracking pixels, HFCM is quicker to set up. For sites with multiple analytics, marketing, and retargeting pixels that change regularly, GTM’s tag management capability is worth the additional setup.

Can HFCM execute PHP code in snippets?

No — HFCM is specifically designed for HTML, CSS, and JavaScript injection only. PHP code added to HFCM snippets will not execute (it may appear as raw text or cause parsing errors). For PHP custom code management, use Code Snippets or WPCode — both are designed for PHP snippet execution with appropriate safety features. HFCM’s limitation to markup/scripts is intentional and makes it safer for non-developer users who might accidentally add broken PHP.

Can PublishPress Blocks break after updates?

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

What should I check before installing PublishPress Blocks?

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.

Need a PublishPress Blocks Developer?

Find a vetted WordPress developer specializing in PublishPress Blocks. From setup and configuration to custom PublishPress Blocks development — get expert help on WPWizzy.
Get a Free Estimate

Ready to hire your WordPress developer?

WPWizzy connects you with vetted freelance WordPress developers from the Codeable network — the top 2% of WordPress experts worldwide, , you can get a free no-obligation project estimate before hiring. Every developer is carefully screened, backed by Codeable’s satisfaction guarantee, and rated by real clients based on completed WordPress projects.

Pick one option and we’ll take you to the right next step.

After submitting your request, up to three WordPress developers may review your project and ask a few questions to better understand the issue.
This step helps us define the scope of work and provide an accurate estimate. Most projects receive a response within 24 hours.
Providing a few key details about your website or the problem will help us respond faster. There is no obligation to proceed with the project.