Forum Replies Created
Hello Shufflehound Team,
Thank you for the update and for taking the time to test this on your end.
It is reassuring to know that you were able to reproduce a similar behavior in your environment. Even though the root cause isn’t fully clear yet, knowing it wasn’t an isolated incident on my side is helpful.
As suggested, I will stick with the manual workaround provided by Complianz, as it is working stable for now. I hope this report remains useful for your development team to potentially address this conflict in a future theme update, to help other users avoid this friction.
You can consider this ticket resolved for now. Thanks again for your support.
Best regards, HaNeulChi
Hello Shufflehound Team,
Please accept my apologies for the delayed reply. I’m not sure why my previous message didn’t send or wasn’t received; I thought I had responded earlier.
Thank you for your quick response and your willingness to investigate.
I understand your reasoning that the issue seems to originate from Complianz’s automatic page generation process, before the theme or WPBakery get involved.
To answer your request: there were no special steps taken, other than the standard Complianz setup wizard (guided procedure).
The error occurred exactly when the Complianz setup wizard, upon reaching the final phase, attempted to automatically create the “Cookie Policy” and “Privacy Policy” pages, asking the user to confirm the data and pages to be generated.
In summary, the steps were simply:
- Install and activate Complianz.
- Start the setup wizard (guided procedure).
- Follow all steps until the plugin asks to automatically create the policy pages.
- Upon completion, the automatically generated pages were corrupted.
I hope this confirmation helps you to reproduce the issue in a clean test environment.
I look forward to your update.
Best regards,
HaNeulChi
Hi,
thank you for your message!
I checked the page again and the issue seems to have resolved itself — it was most likely related to the migration from the demo environment to the live domain.
Everything is working correctly now on mobile as well.Sorry for the inconvenience and thank you for your support.
Thanks again!
Best regards,
Have a nice day,
HaNeulChiHi,
Thanks again – I really appreciate your support!
Have a great day 😊
Best,
HaNeulChiHello,
Thank you so much for your help!
I’ve installed the latest beta version and I’m really happy to report that everything seems to be working perfectly now!
I’ll keep testing and let you know if anything else comes up.
Thanks again for the great support!
Best regards,
HaNeulChiHello Shufflehound Team,
Thank you for the clarification and for your continued support.
As requested, I temporarily switched back to the stable version of the theme to check the submenu arrow visibility issue. I can confirm that the problem persists even with the stable version installed.
Let me know if there’s anything else I can test on my end to assist you further.
Best regards,
HaNeulChi.Hello.
Thank you very much – I’ve installed the latest beta version and everything seems to be working correctly now. I really appreciate your support!
I just have a quick question:
Once the new version is officially released, will I be able to apply future updates normally through the WordPress dashboard, or should I follow a different procedure?Also, while testing the beta, I noticed a small issue with the main menu in the hidden (hamburger) layout:
- The submenu opens correctly when clicking on a parent item,
- However, the arrow icon that should indicate the presence of a submenu is not visible.
To see it, the user must scroll down – but doing so hides the parent item itself.
I’ve attached some screenshots to help clarify the issue.
Please let me know if it’s something already being addressed or if there’s a workaround in the meantime.
Thanks again for your great support!
Best regards,
HaNeulChiHello Shufflehound Team,
Thank you again for your support.
As requested, I checked the server logs after installing the beta version, and I found the following PHP error which appears to have caused the issue:
PHP Fatal error: Uncaught Error: Call to undefined function is_checkout()
in /wp-content/themes/jevelin/inc/helpers.php on line 2737
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): jevelin_wc_checkout_disable_select2()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-includes/script-loader.php(2299): do_action()
#4 /wp-content/themes/jevelin/header.php(22): wp_head()
thrown in /wp-content/themes/jevelin/inc/helpers.php on line 2737After restoring the theme files from my backup, the site returned to normal.
Please let me know how you’d like to proceed or if there’s anything else I can provide to help troubleshoot the issue.
Thanks again for your time and assistance!
Best regards,
HaNeulChiHello Shufflehound Team,
Thank you again for your support.
I installed the beta version you provided, but unfortunately, after the installation I encountered a white screen and the message “There has been a critical error on your website.”
To fix the issue, I restored only the backup of the theme files, and the site went back to normal — which suggests the problem might be related to the beta version.
Could you kindly advise how we should proceed from here?
I really appreciate your help and support.Best regards,
HaNeulChiHello Shufflehound Team,
Thank you for your quick response and for providing the beta version.
Before proceeding with the installation, I just wanted to ask:
If I install the new beta theme by overwriting the current version, will I lose the customizations I’ve made so far?Also, if I export the current settings using the theme’s export function, will I be able to re-import them without issues after the update?
Thanks again for your support, and looking forward to your reply.
Best regards,
Hello Shufflehound Team,
Thank you for your quick response! I really appreciate your support.
I’ll send you the temporary access details and the site URL privately so you can investigate the issue further. Please let me know if you need any additional information from my side.
Looking forward to your findings!
Best regards,
HaneulchiHello Shufflehound Team,
I’ve checked the site after your latest update and everything now seems to be working correctly — the menu, sticky navigation, and animations are back to normal.
Thank you very much for your prompt support and assistance!
Best regards,
HaNeulChi<p data-start=”121″ data-end=”127″>Hello,</p>
<p data-start=”129″ data-end=”224″>Thank you for applying the fix — the WPBakery backend editor now seems to be working correctly.</p>
<p data-start=”226″ data-end=”312″>However, a few issues have appeared after the update. Specifically:</p><ul data-start=”313″ data-end=”506″>
<li data-start=”313″ data-end=”378″>
<p data-start=”315″ data-end=”378″>The theme menu no longer opens on the right side as it used to.</p><li data-start=”379″ data-end=”428″>
<p data-start=”381″ data-end=”428″>The sticky navigation is no longer functioning.</p><li data-start=”429″ data-end=”506″>
<p data-start=”431″ data-end=”506″>The “Text with Frame” animations, when enabled, no longer display the text.</p><p data-start=”508″ data-end=”671″>Please note that all of these features were working correctly before the recent changes.<br data-start=”596″ data-end=”599″ />Could you kindly check if they might be related to the beta fix applied?</p>
<p data-start=”673″ data-end=”706″>Thank you again for your support.</p>
<p data-start=”708″ data-end=”735″>Best regards,
HaNeulChi</p><p data-start=”319″ data-end=”340″>Hi Shufflehound Team,</p>
<p data-start=”342″ data-end=”412″>Thanks for your response and for continuing to investigate this.</p>
<p data-start=”414″ data-end=”592″>I’ve added the WordPress admin login credentials in the private information field as requested. Please feel free to log in and let me know if you need anything else from my side.</p>
<p data-start=”594″ data-end=”627″>Looking forward to your findings.</p>
<p data-start=”629″ data-end=”656″>Best regards,
HaNeulChi</p>Hi Shufflehound team,
Thank you for your suggestions. I performed the tests you requested:
- Deactivated all plugins except WPBakery → Issue remained.
- Switched to the parent theme → WPBakery’s backend editor still didn’t load.
- Disabled the theme entirely → WPBakery worked normally.
This seems to point to a conflict with the theme (both parent and child). Since WPBakery is essential for my site, I’d really appreciate it if you could look into this further. Do you have any updates or suggestions to resolve it?
I’m happy to provide more details if needed—just let me know! Thanks so much for your time and support.
Best regards,
HaNeulChiHi,
Yes, I have tried switching to WPBakery using the button, but the problem persists. When attempting to switch to WPBakery, the screen remains as shown in the first attached screenshot.
The only way to access WPBakery is from the front end, which works fine – second attached screenshot – for the native pages of the template, but not for the others.
I have installed the latest version of the plugin.
Best regards,
HaNeulChi
