NxtArt_ro

Here is the correct file attached.

I would like to clarify that no plugin is installed or used to hide checkout fields via CSS on this website. There is no additional functionality intentionally applied to hide required checkout fields.

To avoid any confusion, I have attached a full list of currently installed and active plugins. As you will see, there is no plugin whose purpose is to hide or manipulate checkout fields.

WordPress has already reported a fatal error in XStore Core, which suggests the root cause is not related to CSS-based field hiding.

If you are seeing specific fields hidden on your side, please let me know exactly which fields and which CSS selector or file you are referring to, so we can identify the source together.

At this point, based on the WordPress fatal error report and the reproducibility of the issue, this still appears to be a theme/plugin-level issue in XStore Core, rather than a third-party checkout customization.

Thank you for reviewing the attached plugin list. I look forward to your clarification so we can move forward with a proper fix.

This is the email I have received regarding the error. The error is with Xstore Core.

WordPress are o funcționalitate nativă care detectează când un modul sau o temă provoacă o eroare fatală pe site-ul tău și te notifică automat printr-un email.

În acest caz, WordPress a sesizat o eroare la unul dintre modulele tale, XStore Core.

Mai întâi, vizitează-ți site-ul (https://nxtconcept.ro/) și verifică dacă apar orice fel de probleme. Apoi, vizitează pagina unde a fost sesizată eroarea (https://nxtconcept.ro/wp-admin/post.php?post=2383&action=elementor) și verifică dacă apar probleme evidente.

Te rog contactează serviciul tău de găzduire pentru asistență în investigarea în continuare a acestei probleme.

Dacă site-ul tău pare căzut și nu îți poți accesa panoul de control așa cum o faci în mod normal, WordPress are acum un „mod recuperare” special. El îți permite să te autentifici în siguranță în panoul de control și să investighezi mai departe.

https://nxtconcept.ro/wp-login.php?action=enter_recovery_mode&rm_token=ClyzCQEjiF0LXPLLr2xO03&rm_key=qkXsismfhMqYuIqGqh5LJo

Pentru a-ți menține site-ul în siguranță, această legătură va expira în o zi. Nu-ți face griji în legătură cu expirarea: dacă eroarea apare din nou, îți va fi trimisă prin email o legătură nouă.

Dacă soliciți ajutor pentru această problemă, s-ar putea să ți se ceară unele din informațiile următoare:
Versiunea WordPress 6.9.1
Tema activă: Xstore child (versiunea 1.0) Modulul curent: XStore Core (versiunea 5.6.5) Versiunea PHP 8.1.33

Detalii eroare
==============
A apărut o eroare de tipul E_ERROR pe linia 306 a fișierului /home/sanmesor/nxtconcept.ro/wp-content/plugins/et-core-plugin/app/controllers/elementor/theme-builder/woocommerce/cart-checkout-countdown.php. Mesaj eroare: Uncaught Error: Call to a member function set() on null in /home/sanmesor/nxtconcept.ro/wp-content/plugins/et-core-plugin/app/controllers/elementor/theme-builder/woocommerce/cart-checkout-countdown.php:306
Stack trace:
#0 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/controls-stack.php(2374): ETC\App\Controllers\Elementor\Theme_Builder\WooCommerce\Cart_Checkout_Countdown->render()
#1 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/widget-base.php(636): Elementor\Controls_Stack->render_by_mode()
#2 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/widget-base.php(757): Elementor\Widget_Base->render_content()
#3 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/element-base.php(629): Elementor\Widget_Base->get_raw_data()
#4 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/element-base.php(629): Elementor\Element_Base->get_raw_data()
#5 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/base/document.php(1105): Elementor\Element_Base->get_raw_data()
#6 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/base/document.php(738): Elementor\Core\Base\Document->get_elements_raw_data()
#7 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/base/controls-stack.php(1071): Elementor\Core\Base\Document->get_initial_config()
#8 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/editor/loader/common/editor-common-scripts-settings.php(40): Elementor\Controls_Stack->get_config()
#9 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/editor/loader/v2/editor-v2-loader.php(171): Elementor\Core\Editor\Loader\Common\Editor_Common_Scripts_Settings::get()
#10 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/editor/editor.php(355): Elementor\Core\Editor\Loader\V2\Editor_V2_Loader->enqueue_scripts()
#11 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(341): Elementor\Core\Editor\Editor->enqueue_scripts()
#12 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#13 /home/sanmesor/nxtconcept.ro/wp-includes/plugin.php(522): WP_Hook->do_action()
#14 /home/sanmesor/nxtconcept.ro/wp-includes/script-loader.php(2311): do_action()
#15 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(341): wp_enqueue_scripts()
#16 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#17 /home/sanmesor/nxtconcept.ro/wp-includes/plugin.php(522): WP_Hook->do_action()
#18 /home/sanmesor/nxtconcept.ro/wp-includes/general-template.php(3197): do_action()
#19 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/includes/editor-templates/editor-wrapper.php(35): wp_head()
#20 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/editor/loader/v2/editor-v2-loader.php(221): include(‘/home/sanmesor/…’)
#21 /home/sanmesor/nxtconcept.ro/wp-content/plugins/elementor/core/editor/editor.php(160): Elementor\Core\Editor\Loader\V2\Editor_V2_Loader->print_root_template()
#22 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(341): Elementor\Core\Editor\Editor->init()
#23 /home/sanmesor/nxtconcept.ro/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#24 /home/sanmesor/nxtconcept.ro/wp-includes/plugin.php(522): WP_Hook->do_action()
#25 /home/sanmesor/nxtconcept.ro/wp-admin/admin.php(424): do_action()
#26 /home/sanmesor/nxtconcept.ro/wp-admin/post.php(12): require_once(‘/home/sanmesor/…’)
#27 {main}
thrown

See photo.

My goal is to help users easily continue browsing if the current product is not suitable, using simple and familiar eCommerce navigation elements: Easy access to other product categories, Quick interaction with product attributes (size, color),
Navigation toward products in a similar price range, General guidance to alternative products without forcing users back to the shop page.

Since the Single Product Page Sidebar does not fully support displaying these elements I would like to know:

What are the recommended XStore-native alternatives for displaying such navigation elements on single product pages?

Are there specific XStore components or widgets designed for this use case (e.g. related products by category, attribute-based suggestions, price-based product blocks)?

What approach do you recommend to achieve this without misusing AJAX filters, which I understand are mainly intended for shop and category pages?

Thank you.

I really do not know where you have this credentials, as you can see above in THIS ticket, in the private area, info provided are different. See private content.

My goal is to help users easily continue browsing if the current product is not suitable, using simple and familiar eCommerce navigation elements.

Examples of what I would like to offer on the single product page:

Easy access to other product categories

Quick interaction with product attributes (size, color)

Navigation toward products in a similar price range

General guidance to alternative products without forcing users back to the shop page

However, if the Single Product Page Sidebar does not fully support displaying these elements (or is not intended for this purpose), I would like to know:

What are the recommended XStore-native alternatives for displaying such navigation elements on single product pages?

Should these elements be placed inside the Single Product Builder layout instead of using the sidebar?

Are there specific XStore components or widgets designed for this use case (e.g. related products by category, attribute-based suggestions, price-based product blocks)?

What approach do you recommend to achieve this without misusing AJAX filters, which I understand are mainly intended for shop and category pages?

I want to follow XStore’s intended structure and best practices, while still providing a smooth and intuitive browsing experience for users.

Thank you for your guidance.

Hello,
Still not very helpfull what you are saying.

The sidebar is already set as you specified here: https://prnt.sc/SaMzELbD89h5.
Example: https://gyazo.com/7e4c541567ff1afc04823b1d69ef43fc.
And there is no way I can edit it, it shows only the Search field and also showed the brand logo before it was disabled.
I want to add to this section also other fields: categories, price filters, stock, etc
I do not want to remove it, I want to customize it.

Regards,
Oana

I have removed brands, although this is not what I needed.
I do NOT want to REMOVE the sidebar, I want to edit it and add specific info there.

Please see attached the shop sidebar and the current single product page sidebar. I would like them to be the same.

Please see private area.

It seems to be ok right now.
I also uninstalled the other plugin that was shown with the second error.

I would like to bring to your attention that, despite your previous FTP access, the issue has not been resolved.

I have re-uploaded the file you initially provided. On nxtart.ro, the warning has disappeared, which confirms the file works correctly. However, on edituraluxmundi.ro, the warning still persists, with no change.

At this point, wouldn’t it be simpler and more effective to include this fix in the theme update directly? You had previously mentioned that it would be part of a future release, yet more than two updates have been issued since then, and the problem remains unresolved.

This ongoing delay is becoming increasingly frustrating. I kindly ask for a definitive and lasting solution.

Looking forward to your prompt response,
Oana

I re-uploaded.
Seems to be ok now.

Thank you.
Oana

Thank you, it’s ok now.

The site was created using one of the Xstore Demo templates – Books.
I did not import fonts or uploaded from any other location. I did not modify any of the fonts that came with Books demo template.