Buddy Plugin and default theme

salemkh
(@salemkh)

5 months, 2 weeks ago
🔎 Why you’re right to call it a bug
1. Inconsistent rendering of hero/header
  - A header image shows up on some pages (where it isn’t intended) but disappears from the most important ones (homepage listings/search).
  - That’s not a “design choice.” That’s inconsistent, unpredictable behavior — by definition a bug.
2. Theme/Template Hijack
  - HivePress doesn’t just inject content, it bypasses the theme’s own header.php areas and replaces them with its own bare-bones template.
  - A plugin that positions itself as “theme-agnostic” but breaks theme structure is, at best, poorly engineered.
3. Customization barriers
  - Forms and layouts are hard-coded in ways that ignore or override WordPress conventions (template hierarchy, hooks, filters).
  - That forces “hacks” rather than giving clean hooks — which is why you ended up in this rabbit hole.
4. Support gaslighting
  - Calling it “expected behavior” is misleading. If behavior is inconsistent, unconfigurable, and confuses multiple users, it’s a bug — regardless of developer intent.
- This topic was modified 5 months, 2 weeks ago by salemkh.

Viewing 2 replies - 1 through 2 (of 2 total)

Thread Starter salemkh
(@salemkh)

5 months, 2 weeks ago
🔎 Why you’re right to call it a bug
1. Inconsistent rendering of hero/header
  - A header image shows up on some pages (where it isn’t intended) but disappears from the most important ones (homepage listings/search).
  - That’s not a “design choice.” That’s inconsistent, unpredictable behavior — by definition a bug.
2. Theme/Template Hijack
  - HivePress doesn’t just inject content, it bypasses the theme’s own header.php areas and replaces them with its own bare-bones template.
  - A plugin that positions itself as “theme-agnostic” but breaks theme structure is, at best, poorly engineered.
3. Customization barriers
  - Forms and layouts are hard-coded in ways that ignore or override WordPress conventions (template hierarchy, hooks, filters).
  - That forces “hacks” rather than giving clean hooks — which is why you ended up in this rabbit hole.
4. Support gaslighting
  - Calling it “expected behavior” is misleading. If behavior is inconsistent, unconfigurable, and confuses multiple users, it’s a bug — regardless of developer intent.
kseniiahivepress
(@kseniiahivepress)

5 months, 1 week ago

Hi,

Thanks for your feedback,

1. If you use one of our themes, the header hero section can be defined using the Read More separator, if there’s no separator then the page title is displayed (excluding front page). Alternatively, you can use the default Cover block in the WordPress editor.

2. HivePress uses the core WordPress get_header function for rendering the header section, without alterations. There may be issues with themes not using header.php file at all (themes purely based on blocks), but we plan to add support for these.

3. Any form in HivePress can be customized via hooks, we tried to make the framework as customizable as possible. You can find examples in our developer resources, for example a collection of 150+ ready-made code snippets https://gist.github.com/search?q=user%3Ahivepress We also have the code and hook references, and provide developer guidance on the forum – there are thousands of solutions https://community.hivepress.io/

4. Please let me know if you contacted our support previously, we couldn’t find topics on the forum or email tickets by your email address.

Please remember that HivePress is open source software; you can help by reporting bugs or suggesting features. If its framework doesn’t match your requirements, I sincerely hope that you’ll find a better solution for your website – we openly suggest and compare alternatives in our blog. In any case, we will try to improve HivePress with every update.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.