how to make different image on parent categories and child on website?

and ex. this one https://lauralutz.lt/produkto-kategorija/rubai-vyrams/apatiniai-rubai-vyrams/

How can this be resolved?

The front-end of the site is working fine.

I've set up an administrator account for you.

www.deborahcroci.it

h

How can i solve it?

Thank you so much

I found an issue with hierarchical taxonomy filters when using a Shop Archive template and template set for a Brands taxonomy.

The template contains a Filters element alongside Shop Products. The Categories filter is configured as:

• Filter by: Taxonomy
• Taxonomy: Product categories
• Field type: Checkbox

Products and other filters display correctly, but the Categories filter disappears entirely on the brand archive. It displays in the builder’s general shop preview.

Changing the field type to Switch makes the categories appear, but we need the hierarchical checkbox layout. Toggling “Exclude parent taxonomy terms” makes no difference.

Example scenario

Consider this category structure:

Clothing
└── Outerwear
    ├── Jackets
    └── Coats

A product belongs to Brand A and is assigned only to Jackets. Coats contains products from Brand B.

On the Brand A archive, the expected category filter would show:

Clothing
└── Outerwear
    └── Jackets

Instead, the Categories field can disappear completely.

Why the current code appears to fail

In sc_filters() in functions/theme-shortcodes.php, Checkbox, Radio and Select fields set:

$terms_params['parent'] = 0;

On an archive, the query also adds:

$terms_params['object_ids'] = $product_ids;

Together, these request only top-level terms directly assigned to products in the current archive.

In the example, the product is directly assigned to Jackets, not Clothing. The query therefore returns no root terms, and the filter field is omitted.

Proposed change

For hierarchical controls:

1. Fetch the terms assigned to the archive’s products, without the top-level restriction.
2. Add their ancestors so the hierarchy can be displayed.
3. Restrict the root query and every child query to that combined set.

This preserves the relevant hierarchy without introducing unrelated branches. It uses the selected taxonomy rather than hard-coding brands or product categories.

The proposed minimal diff against 28.5.10 is:

--- a/functions/theme-shortcodes.php
+++ b/functions/theme-shortcodes.php
@@
 					if( ( is_tax() || is_tag() || is_category() || is_archive() ) && !empty($product_ids) ) {
 						//$terms = mfn_get_available_attr_terms_in_current_view($product_ids, $excl_ids, $field['tax_filter'], $hierarchical);
 						$terms_params['object_ids'] = $product_ids;
+
+						if( isset($terms_params['parent']) ) {
+							$term_ids = get_terms(array_merge($terms_params, [
+								'parent'       => '',
+								'fields'       => 'ids',
+								'hierarchical' => false,
+							]));
+
+							if( is_wp_error($term_ids) || empty($term_ids) ) continue;
+
+							$included_ids = $term_ids;
+							foreach( $term_ids as $term_id ) {
+								$included_ids = array_merge(
+									$included_ids,
+									get_ancestors($term_id, $field['tax_filter'], 'taxonomy')
+								);
+							}
+
+							unset($terms_params['object_ids']);
+							$terms_params['include'] = array_unique($included_ids);
+							$terms_params['hide_empty'] = false;
+						}
 					}
@@
-							$term->childrens = get_terms([ 'taxonomy' => $field['tax_filter'], 'hide_empty' => true, 'parent' => $term->term_id]);
+							$term->childrens = get_terms(array_merge($terms_params, [ 'parent' => $term->term_id ]));
@@
-									$termm->childrens = get_terms([ 'taxonomy' => $field['tax_filter'], 'hide_empty' => true, 'parent' => $termm->term_id]);
+									$termm->childrens = get_terms(array_merge($terms_params, [ 'parent' => $termm->term_id ]));
@@
-											$termmm->childrens = get_terms([ 'taxonomy' => $field['tax_filter'], 'hide_empty' => true, 'parent' => $termmm->term_id]);
+											$termmm->childrens = get_terms(array_merge($terms_params, [ 'parent' => $termmm->term_id ]));

Could you review this approach and consider incorporating a fix into the theme? I’ll leave the final implementation and wider compatibility/regression testing with your team.

This has been applied and working in my current setup at https://tinyurl.com/z855sduf

Thanks!

I’ve identified two issues with locally cached Google Fonts in BeTheme 28.5.9.1.

1. Checkbox metadata is treated as a font weight

With Ubuntu weights 400, 500 and 700 selected, regenerating local fonts also created Ubuntu-1-latin.woff2 and its Latin Extended equivalent. These were declared as weight 400, duplicating the regular font. The same happened with Poppins.

The checkbox renderer in muffin-options/fields/checkbox/field_checkbox.php adds a hidden [post-meta] value of 1.

In functions/builder/class-mfn-builder-ajax.php, _tool_regenerate_fonts() reads the font-weight array and iterates over its values without excluding this marker. It consequently requests weight 1 and uses that value in the generated filenames.

For testing, I added:

unset($weight['post-meta']);

Immediately after:

$weight = mfn_opts_get( 'font-weight', ['400'] );

After regeneration, the duplicate Ubuntu-1 and Poppins-1 declarations disappeared, leaving the expected weights.

This also affected performance: WP Rocket preloaded Ubuntu-400, while the browser downloaded Ubuntu-1 through the later CSS declaration, resulting in two regular-font downloads.

Could you exclude checkbox metadata and validate the weight values in the generator?

2. Regenerated frontend font CSS retains a fixed version

In functions/theme-head.php, the local stylesheet is enqueued with true as its version:

wp_enqueue_style('mfn-local-fonts', wp_normalize_path($path_fonts.'/mfn-local-fonts.css'), '', true);

This produces mfn-local-fonts.css?ver=1, which remains unchanged after regeneration. On our aggresively cached site, the original URL continued returning older CSS, while changing the query-string version returned the updated content.

Could this use the generated file’s modification time, or another version updated during regeneration, to invalidate cached copies reliably?

I understand Poppins is included for the theme’s admin/builder interface, so its inclusion is not the issue being reported.

Thank you.

I created a global template using Wrap... how do I insert it into my page? I don't understand how to call it.

thank

PageSpeed flags linked image elements under “Identical links have the same purpose”, identifying a failure to follow accessibility best practice. The reported elements have this markup:

role="link" aria-label="Image with links" tabindex="0"

In the BeTheme 28.5.9.1 source, this label is hard-coded in sc_image() in functions/theme-shortcodes.php, around line 10024.

The image element’s custom $link_title is already applied to the inner anchors, but the keyboard-focusable wrapper retains the generic “Image with links” description. This means the supplied link title does not provide a meaningful accessible name for that wrapper.

Could the wrapper’s aria-label use the custom link title when supplied, with an appropriate fallback when it is empty? For example, a linked logo could use “Visit our home page”.

You can see this at https://tinyurl.com/2w9wdbvj

Thank you.

Suddenly, my website has started showing the play buttons for background videos on iPhones. How can I remove them?

This is the website: https://es.complidermol.com/es/es/

Thank you

Go back to Navigator - the Wrap "Elements" are not visible. Can't click on anything. Any new changes wipes out previous work.

I tried writing custom code, instead of Using "Elements". Same thing happens.

mf9vqbl9en-staging.onrocket.site/media-information/nelsonian-awards/2019-winners

"This year's recipients are:" section is the messed up section. I have tried custom code, deleting and recreating. System Status, PHP are all good.

Details for this site have been sent through DM at code canyon

I use the media carousel, but that it is not working on mobile.

It shows the first picture and text, but it does not scroll to the next image.

Thanks

WHERE IT COMES FROM. functions/post-types/class-mfn-post-type-template.php is 2516 lines, and line 2516 — the last line — instantiates the class at file load.

In the constructor, line 23 opens a guard on Sitepress not existing. Inside it, the bebuilder_access filter bails at 25-26, and the editor/administrator test bails at 29-30. That guard closes at 33. The parent constructor call at 35 and the init attachment at 38 are outside it. So with WPML present the post type registers unconditionally; without it, registration is decided at file load, before authentication has run.

WHAT I MEASURED. Reading the current-user global directly, without calling anything that would resolve it:

 set_current_user ... 0

 setup_theme ........ 0

 after_setup_theme .. 0

 init priority 1 .... 0

 init priority 9999 . 0

 rest_api_init ...... 0

 route handler ...... 1

ALREADY RULED OUT: MOVING THE CHECK TO INIT. It does not help, and not for a timing reason. At every point above, the determine_current_user callbacks are only the three core ones: wp_validate_auth_cookie, wp_validate_logged_in_cookie, wp_validate_application_password. AI Engine registers none, and sets the user explicitly inside its route handler instead. So there is no point before dispatch at which that token could be resolved, by any hook. You can confirm this in your own environment by dumping the determine_current_user filter list on such a request.

SCOPE. This is not all authenticated REST requests. wp_validate_auth_cookie is registered, so cookie-authenticated requests resolve normally and early and are unaffected. It applies to schemes that authenticate outside determine_current_user.

TWO CANDIDATE FIXES — THE CHOICE DEPENDS ON INTENT ONLY YOU HAVE.

Option A, register unconditionally and gate only the interface. Not neutral as things stand: the registration sets public to false but publicly_queryable to true explicitly, so with the type registered the single-item template-item URLs become reachable by anonymous visitors. Note your WPML path already registers unconditionally today, so that exposure already exists on those installs.

Option B, derive show_ui and publicly_queryable from the access check at registration time. That leaves a registered but invisible post type on a token request, which is all a programmatic client needs.

The question that decides it: is publicly_queryable true here deliberate, or a leftover alongside the template-item slug? If it is a leftover, Option A is small. If it is load-bearing for template preview, Option B looks better. I cannot tell from outside, which is why I am asking rather than proposing a patch.

somehow what you see in the backoffice with Bebuilder editor, is not showing in the frontoffice (the website itself) and also different elements are there that should not be there.

A bit difficult to explain without going into detail and exposing which site is involved, so I have sent all details through envato DM, reffering to this post.

Please check what I have sent and look at the example pages mentioned in there, also then make sure to scroll down the entire pages from top to bottom, to see what is going wrong.

Thanks in advance!

Why texts apeared and how to delete them from shop slider be builder element? "Original price" and "Current price"

I need help with an older BeTheme website that was originally built several years ago using Muffin Builder.

After updating BeTheme, I can no longer edit the existing page content.

The important point is that all existing content is still displayed correctly on the frontend, so the content has not been lost. However, in the WordPress backend the existing pages appear empty.

When I click “Edit with BeBuilder”, BeBuilder gets stuck indefinitely on “Loading builder…”. This happens on all existing pages, not just one page.

We have already checked the database. The old builder content is still present in wp_postmeta, including mfn-page-items / the BeTheme builder data. Therefore, I do not want to rebuild, overwrite, or otherwise modify the existing page content.

We have already tried:

• updating BeTheme to 28.5.8

• running the BeBuilder database updater successfully

• BeTheme Tools → Regenerate files

• BeTheme Tools → Re-render Builder data

• updating BeCustom

• updating the bundled WPBakery Page Builder to 8.7.3

• testing with the “Disable REST API” plugin deactivated

WPBakery now works, but the old page content is not stored as WPBakery post_content, so WPBakery shows an empty page.

Server environment:

• WordPress 6.5.10

• BeTheme 28.5.8

• PHP 8.3.31

• PHP memory limit: 256 MB

• PHP max_input_vars: 3000 (BeTheme System Status recommends a minimum of 5000)

• Hosting: World4You

The hosting error log previously showed:

Resource temporarily unavailable: couldn't create child process: /usr/sbin/suphp

However, during a later controlled BeBuilder loading attempt, no new corresponding server error appeared.

Could you please check the website and help restore the ability to edit the existing Muffin Builder / BeBuilder content without overwriting or losing the existing content?

I can provide WordPress administrator and FTP access privately if required.

Thank you.

Hi BeTheme Support Team,

We are experiencing a critical issue with the Shop Products and Shop Slider elements after updating BeTheme to version 28.5.9.1.

Immediately after the update, product pricing and variation-related text started displaying incorrectly across the shop elements.

Issues observed

1. Product price is displayed twice

The product price is now appearing twice in the Shop Products and Shop Slider elements.

For example, instead of displaying the price once, the element is showing both the original/regular price and the current price in an incorrect or duplicated format.

2. Additional "Original Price" / "Current Price" text is appearing

Unexpected text has started appearing alongside the product pricing, including labels such as:

• "Original price was:"
• "Current price:"

These labels were not previously displayed and appear to have been introduced after updating to version 28.5.9.1.

3. Incorrect variation message is appearing

For products that have multiple variations, an additional message is now being displayed:

"The product has multiple variants. The option may be chosen on the product page"

This message is appearing directly within the Shop Products/Shop Slider product listing and was not present before the update.

Expected behavior

The shop product cards and Shop Slider should display the product information normally, with:

• The product price displayed only once
• Sale/regular pricing displayed in the standard WooCommerce format, if applicable
• No additional "Original price was" or "Current price" labels unless specifically configured
• No variation-selection message displayed within the product listing
• Products with multiple variations should simply link to the product page where the customer can select the required variation

This issue appears to be a regression introduced after updating BeTheme to version 28.5.9.1, as the same elements were working correctly before the update.

I have attached screenshots showing the affected products and the incorrect pricing/text for your reference.

Could you please investigate this urgently and let us know how we can correct these issues? If this is a known issue with version 28.5.9.1, please provide the recommended fix or patch as soon as possible.

Please also confirm whether this requires a BeTheme update, a WooCommerce compatibility fix, or any changes to the theme/element settings.

Thank you for your prompt assistance. This is affecting the presentation of products on our shop pages, so we would appreciate an urgent resolution.

Best regards,

on the website I am editing for my company, there are some flags, that were supposedly there to switch between languages. We decided to only launch the website in German for now and delete the flags, but somehow, even though they are shown in the top bar, I can't select them to delete them. They are also not part of the Menu they appear in.

we have moved from theme porto to betheme, and it seems the shop results on page speed its much worse.

Domain rankine.lt

How to optimise website? we only have up to 15 plugins.

The link to the page is https://2024.disag.de/

PC View:

Tablet View:

How Can I fix this?

This affects several Sites I build …

I’m trying to create a second portfolio/archive page on my website, and I need some guidance on how this should be set up within the theme.

The website is for an event venue called The Place by Digma Productions ( https://theplace-digma.com ) At the moment, we have a portfolio/archive page called Events, where we showcase different events that have taken place at the venue.

I would now like to create a second, separate page called Studio, using the same layout/design and functionality as the existing Events portfolio page.

The idea is:

• Events → displays projects/events related to the venue’s event space.
• Studio → displays projects where different clients have used the venue’s studio facilities (photo/video productions, shoots, content creation, etc.).

Both pages should have the same visual structure as the existing portfolio page, but they should display different portfolio items.

I tried duplicating the existing portfolio/archive page, but this does not work as expected. Instead of duplicating the actual page layout and settings, the duplicated page seems to use a different template, so the original portfolio design is lost/broken.

What I would like to achieve is:

1. Keep the existing Events portfolio/archive page as it is.
2. Create a second archive/portfolio page called Studio, using exactly the same layout and design.
3. When I create a new portfolio item, I need to be able to assign it either to Events or Studio.
4. Items assigned to Events should appear only on the Events page.
5. Items assigned to Studio should appear only on the Studio page.
6. Ideally, both pages should use the same portfolio item template/design, while the two archive pages display different sets of projects.

Could you please explain the correct way to set this up with your theme?

Specifically, should I be using portfolio categories, taxonomies, custom post types, archive templates, or another feature of the theme?

And how can I create a second archive page that uses the exact same design as the existing portfolio archive, but displays only the portfolio items assigned to the Studio category?

If possible, please provide step-by-step instructions for the correct setup.

Thank you!

I’m working on the header of my website, theplace-digma.com, using BeBuilder / BeTheme.

I’m having an issue with the positioning of the header logo. I want the logo to start directly from the top edge of the browser viewport, without any empty space above it.

At the moment, there is a visible gap between the top of the viewport and the top of the logo. I’ve checked the header structure in the Navigator. The logo is inside:

Section → Wrap → Header Logo

I also checked the Section → Advanced → Positioning settings and the Section content position is already set to Top.

I don’t want to simply move the logo upwards with a negative top value, as I assume the empty space is caused by padding, spacing, the Wrap, or the Header/Section configuration.

Could you please advise me which exact BeBuilder setting is creating this top spacing and how I should configure the header so that the logo sits flush with the top edge of the viewport?

I can provide screenshots of the current Section, Wrap and Logo settings if needed.

Thank you!

The Exact Bug:

When opening any older, existing page with the modern "Edit with BeTheme Editor" (BeBuilder), the engine appears to display the layout fine visually. However, if we make any change at all—even editing a single word—and click Save, the save sequence completely drops the entire page payload. It immediately overwrites the database, wiping out all text, elements, and layout containers, leaving a completely blank page on the frontend [image_LSs-1H].

Our Current Workaround:

We can safely edit and save text copy without data loss only if we completely bypass BeBuilder and click the classic WordPress backend "Edit Page" button.

Everything We Have Checked & Attempted (To Rule Out Basics):

1. Server Environment is Fully Optimized: Running PHP 8.3.33, PHP Memory Limit is 512MB, and PHP Max Input Vars is set to 10,000 [image_DmGEq5.png]. All System Status indicators are green.
2. Plugin Conflict Testing: We deactivated ALL 3rd-party plugins on the site (including Elementor, Classic Editor, and Jetpack) to test in a native environment.
3. Native Recovery Tools Ran: With 3rd party plugins deactivated, we executed the "Re-render Builder data" tool via Betheme > Tools.

Unfortunately, even after a clean data re-render with no plugins running, making any single text change inside BeBuilder immediately drops all layout content upon save. This strongly points to a deep database serialization or structural translation conflict between the 7-year-old meta arrays and the modern saving script.

Could a technical moderator please escalate this directly to the engineering team? I am happy to provide secure private dashboard admin login credentials so an engineer can inspect the raw database string translation mismatch.

How do I make edits to the sections which are built with BeBuilder, they appear blank when im in edit mode, so I can't make changes to those specific sections, please help.

I am experiencing an issue with BeTheme 28.5.7 and the BeBuilder/Live Builder.

When I create a new template, the Live Builder opens automatically. The existing elements are displayed correctly, but the builder does not respond to any actions.

The following functions do not work:

• Editing elements
• Deleting elements
• Adding new elements via “Add Element”
• Undo/Redo
• Saving changes via “Update”

I have already performed the following tests:

• Checked the Chrome DevTools console → no JavaScript errors
• Performed a hard refresh using Ctrl + Shift + R → no change
• Tested the BeBuilder in Incognito mode → no change

The builder itself loads correctly and the existing content is visible, but none of the editing functions respond to clicks.

My BeTheme version is 28.5.7.

Could you please help me identify why the BeBuilder is not responding and how I can restore its editing functionality?

Thank you in advance for your help.

Best regards,

unfortunately the code editor is no longer working properly. In the BeBuilder, when I open a Column Text element and switch to the text/code view, the editor is broken: the toolbar buttons (bold, italic, etc.) have no effect, and the interface elements overlap. Switching back and forth or changing the usual settings doesn't fix it.

I suspect this is related to the update installed today. Could you please tell me how to restore the editor to working order? I'd appreciate a quick solution, as I'm currently building several pages that rely on custom HTML.

System details:

– BeTheme version: 28.5.7

– WordPress version: 7.0.3

– The site is a staging environment (Raidboxes) with FastPixel Cache

Thank you very much in advance and best regards,

Sebastian Schönenstein