I’m still looking for assistance with removing the entry header in using the Honeycomb child theme. I’ve reviewed the documentation related to customizing the theme, specifically at this link, but I couldn’t find any specific information about removing the entry header. There is very limited information.
My goal is to completely remove the entry header from the theme, rather than using CSS to simply hide it. Could you please guide me on how to properly remove this element from the theme usage?
PS. I still want to use the default property hive shortcodes for search form such as [[property_search_form id="default"]] – But still be able to ‘edit / ‘design’ the page with Elementor. So what is the best approach to do this?
Hi. Just wanted to add some additional context. I’m looking to retrieve the Home Report attachment IDs for use in a custom function.
PS. > I’ve noticed that using the Template Assistant Additional Field widget on Elementor allows the use of the Home Report Link as a field. However, I’ve encountered an issue where the Home Report Link does not produce any output when using the Additional Field widget. In fact, there is no output at all. Despite this, the Home Report Link appears and functions correctly when used in the ‘Actions’ widget per default. I thought I would report this to you.
Nevertheless, Is it possible to create a helper method to retrieve the Home Report attachment IDs? I’d like to incorporate this into as part of a separate function I’m developing.
Frank, I would also like to see more documentation of building a custom property loop with Elementor.
However, the property search page you provided appears to be custom-built most likely using the global property object rather than created using Elementor. I would also like to see more documentation on how to set that up with property hive.
Unique Class Names and Styles: The class names and inline styles like “grid-box-card,” “grid-content-inner,” and “wow fadeInUp animated” do not directly correspond to Elementor’s standard naming conventions.
HTML Structure: The nested structure of the HTML, including the way the property details and images are organized, looks more bespoke. Elementor’s HTML structure is typically more modular and includes many wrapper elements with Elementor-specific classes.
Custom Button and Image Handling: The button with the class “property-more-details” and the way images are handled with inline styles for scaling (“style=”transform: scale(1);”) point towards a custom implementation.
The individual property page listing appears to be similar with the property-tabs-container and property-description-icons-container, with the data being pulled from property object I assume.
