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 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 i solve it?

Thank you so much

1) What is the correct way to translate theme elements that are not available in String Translation and are also not detected by the WPML Translation Editor? For example, this applies to the placeholders, header elements and shop filter titles marked in the attached screenshot. Do I need to change these texts separately for each language in the theme settings?

2) Sometimes the CSS styles are not copied correctly to one of the language versions. Updating both the original page and its translation does not restore the missing styles. What is the recommended way to fix this situation?

Thanks for help.

Best regards

I wanted to change an image in the footer and add a link. As soon as I click “Update,” an error message appears, as shown in my screenshot.

The requested changes will not be applied.?

Best regards

After updating Betheme from 27.6.2 to 28.5.9.1, the WooCommerce list toolbar on our Shop and category pages stopped being output. It looks like a regression for Shop templates whose type is shop-archive.

Site / versions

• Site: https://lotsandcrates.co.za (licence registered to this domain; purchase code available privately on request)
• Betheme 28.5.9.1 (parent) with Betheme Child 2.0 (stock child theme), BeCustom 1.0.5.3 (white label: menu/slug "lc")
• WordPress 7.1.1, PHP 8.3.30, WooCommerce 10.4.4, Slider Revolution 6.6.9

What happened

1. Before the update (27.6.2), the Shop and category pages showed the toolbar: "Show 10/20/40/60", layout toggle, Filters button and active filters. Sorting and result count were hidden by our own override, described below.
2. Immediately after updating to 28.5.9.1, the whole toolbar was gone on desktop and mobile.
3. I then ran the "BeBuilder Data Updater" (Update Database) that appeared after the update (the same action as Tools → CSS update). It completed ("Done") and the notice cleared. The toolbar is still missing.

Evidence

• Theme Options → Shop → Products list has sorting, layout, per-page and active filters set to Show, and results count set to Hide. Unchanged.
• The Shop template (post 129, "Shop template") is unchanged. Its Shop products element still has the same shop-list-* settings and post meta (mfn-shop-list-layout/perpage/active-filters = visible, sorting/results-count = hidden).
• The markup is absent from the rendered HTML, not merely hidden by CSS. There is no .mfn-woo-filters-wrapper, .shop-filters, .mfn-woo-list-options, .woocommerce-ordering or .woocommerce-result-count element in the page source. They were present in the 27.6.2 source.
• That Shop template's type is shop-archive (meta mfn_template_type).
• In functions/theme-woocommerce.php (28.5.9.1), the toolbar hooks on woocommerce_before_shop_loop: mfn_woo_products_list_filter_wrapper_start (priority 5), mfn_woo_products_list_options (20) and mfn_woo_products_list_filter_wrapper_end (35). They only output when $mfn_tmpl_type is in array('shop', 'archive-product', 'default'). shop-archive is not in that list, although the same file (around line 335) still treats shop-archive as a valid template type.
• As a result, sorting, result count, per-page selector, layout toggle, Filters and active filters are all absent.
• We have a small snippet ("Snippet 22") that only un-hides the sorting and results count elements. It controls visibility only, so it cannot restore markup Betheme no longer outputs.

Questions

1. Is shop-archive still a supported Shop template type in 28.5.9.1?
2. If yes, is its omission from the toolbar-rendering condition a regression, and will it be fixed in an upcoming release (or is there a supported patch or filter meanwhile)?
3. If shop-archive has been superseded, what is the officially supported migration path for an existing Shop template (for example re-typing it to archive-product, or rebuilding it with the new Filters/Advanced Filters elements)? Does it need any data update beyond the BeBuilder Data Updater already run?

I have not changed the Shop template, its type, Theme Options or Betheme files. A full backup exists. I can provide WordPress dashboard access privately if you need to inspect it.

Thank you,

Richard Rheeder, Lots & Crates

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!

in my web site www.gruppoarata.it there is an arrow in the top right corner (see the attach), what is it the function? how can i remove it?

thanks

I am currently performing maintenance and troubleshooting on a WordPress website using BeTheme.

We recently resolved a critical WordPress error caused by an inconsistent set of WordPress core files. The website has since been successfully updated from WordPress 7.0.4 to WordPress 7.1.1.

The website and WordPress administration are now working normally. However, we are experiencing an issue when trying to save settings in BeTheme Options.

Issue description

Whenever we attempt to save changes in BeTheme Options, regardless of which setting is modified, the server returns the following error:

400 Bad Request

Your browser sent a request that this server could not understand.

The issue occurs consistently when saving BeTheme settings.

Technical environment

• WordPress version: 7.1.1
• BeTheme version: 28.5.9.1
• PHP version: 8.1.34
• PHP Memory Limit: 512 MB
• PHP Time Limit: 360 seconds
• PHP Max Input Vars: 200000
• Hosting provider: PlanetHoster

Troubleshooting already performed

We have confirmed that:

• The website's frontend is working correctly.
• The WordPress dashboard is accessible.
• Pages can be edited and published successfully.
• Standard WordPress settings can be saved without errors.
• The WordPress REST API is responding correctly.
• The PHP resource limits appear to be sufficient.
• The issue specifically affects the saving of BeTheme Options.

Using the browser's developer tools, we identified the request that fails:

Request URL: ****/wp-admin/options.php

Request Method: POST

Status Code: 400 Bad Request

Could you please advise on the following?

Thank you in advance for your assistance.

Best regards,

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

Malibuspecialfd.com

Purchase code I bought:

[removed by moderator]

I had a bad problem with my site instoll and had to completely delete the site and wordpress and the files in the file manager on my side and re install the site and wordpress.

I think I should have deregistered the code before deleting the site.

I reinstalled the theme and tried to register it but it said that the code was already used,

This is the same code that I used to install betheme on that SAME url just a day ago so the theme should still be valid.

I would like to utilize the same code on the same url.

Can you please help me to be able to register the site with the the purchase code I just bought and am trying to use on the exact same url.

Thank You

Scott Tugel

I made some changes to the copyright bar and after changing the main menu has switched up to the muffin group default for some reason.

Everything was working fine.

I tried making a new main menu.

when you go to the home page and click see more it switches to the default theme pages and menus.

Please Help

601

Hello,

I am having an issue with the BeTheme template I am using on my site, www.gruppoarata.it. The problem is as follows: when I open an article—such as https://www.gruppoarata.it/2026/09/16/crema-di-ricotta-carezza-protagonista-sulla-stampa-specializzata/—the main menu and header overlap the article content (please see the screenshot). How can I fix this? More importantly, how can I ensure this issue does not recur with every new article I create? The solution should apply only to the articles (both existing and new ones) and should not require changes to other parts of the site. Thanks.

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

Our website, fillaendurance.com, is currently registered with a BeTheme license belonging to the marketing company that originally built the site. We no longer have access to that Envato account.

We purchased a new Regular License through Laura Filla's envato account. In Wordpress under BeTheme>Dahsboard, clicking "Deregister theme" does nothing, even after a hard refresh.

Please remove the old license registration from fillaendurance.com so we can activate our newly purchased license. We can provide the new purchase code privately if needed.

Thank you.

is there possible to import this header and footer from Clothing2 demo, into templates part?

https://lauralutz.lt/ - we need to customize same items as is in theme footer and header.

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.

I have this tabber on the image above which contain different catégories.

On each tab I put a queryloop to display featured images using an "image element" of my portfolio items that are categorised same like the tabs.

Now what I want to do is when I click on the image it will open a popup with an image gallery or image carrousel related to each portfolio item.

My question is how to easily do that because I want my client to create for exemple a new item and simply choose the featured image (easy to do) and also the images that will show in the popup directly from the portfolio backend.

for now the featured image is easy, but how to make a popup that shows image gallery of this portfolio item.

Thank you very much

If there is a more simple way to do it maybe with another solution I am totally open. the thing is I have images from different item categories and when I click on them it displays a popup image gallery of those specific items.