Customiser bug with v4.01 & Child Theme
-
I’ve updated a couple of staging sites to the new version of OceanWP and OceanExtra v4.01 and believe there is a bug.
If you DO NOT have a child site then things appear as they should, however if there is a child site present then the ‘Customizer Site Style & Settings panel‘ and ‘Pages & Special Pages’ are missing from the customiser. Any site that had a custom width set simply reverts to 1280px with no option to change.
Screenshots –
https://ibb.co/QN4w3h0
https://ibb.co/92p6xYKThanks
-
Hello @monowebdesign,
Thank you for reaching out,
Regarding the missing items in the child theme, please go to WP Dashboard > OceanWP > OceanWP Panel > Customizer, and ensure all options are enabled: https://postimg.cc/zLxQvf5V (this feature is not new).
Regarding the width issue, I fully tested the width and saw no issue on my end.
We need to know the steps to replicate. Would you please provide us with some screenshots or short video + live URL, and images of the errors you faced step by step?
Also, please tell us if you are using Elementor page builder, have you tried to change the layout width in the Elementor> site settings > layouts?
I hope it helps.
Best RegardsHi Shahin
Thanks for the reply.
All options are enabled in Customiser. Elementor is present but it is the Sitewide width that is missing – the bug is still present when Elementor is deactivated. It is the options missing from the customiser that is the issue.
See screenshare below – the first part is with the child theme – no options for ‘Customizer Site Style & Settings panel‘ and?‘Pages & Special Pages‘ but when switching to the actual theme they are present. – back to child theme and they do not show.
Screenshare – https://www.loom.com/share/c3420a5f2005400c965dc804d4b03a11?sid=e05f74e7-bf5f-4da2-a9e4-3fa5f049c415
There is one error showing on Console: https://imgur.com/a/qdraFvI
Uncaught TypeError: Cannot read properties of undefined (reading ‘isFeatureActive’)
at customize.php?return=%2Fwp-admin%2Fadmin.php%3Fpage%3Doceanwp:1960:95
at dispatch (load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks,underscore,wp-dom-ready&ver=6.6.2:2:40035)
at load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks,underscore,wp-dom-ready&ver=6.6.2:2:38006Hi ?Shahin
My three websites which all use the OceanWP theme (thank you) and OceanWP Extra plugin (2.4.1) and a child theme all exhibit the same behaviour (as described by monowebdesign) on updating to V4.0.1.
While I appear to be able to set the Content settings Boxed width at the required 960px the site is rendered at 1280px.
All customiser options are set to be on and I have tried disabling all plugins and deleted previous browsing history. WordPress version is 6.6.2 and there is no page builder.
Not sure if I can send you any relevant error screen shots as the site seens to function perfectly well albeit for a content width of 1280px and I want 960px.
Site https://coaley.net/
Hopefully you will see a bug in the area where Content settings Boxed width is being set set
Many thanks
I also have this issue!
Child theme Customizer is missing some setting optiosn
Came here to report the same bug for my site. Definitely all options for the customizer enabled, but severall sections are missing – just exactly like in the screenshots monowebdesign showed. Before the update there was no problem and the only thing my child theme changes is a file for tribe events.
No problem with the width though.Hello I have exactly the same issue
Hello everyone @irenamery, @jenwe, @mgz069, @overbridge, @monowebdesign (hope I tagged you all correctly).
First, allow me to thank you all for using OceanWP and your continued support. Most importantly, thank you for taking the time to share details about the problems you’ve been experiencing.
Since yesterday we tried everything to replicate this on our ends, but were unable to. Likewise, not all users utilizing the child theme experience this, therefore we had not a direct access to an environment with this problem.
However, we revisited the logic for all Customizer panels. But since we were not able to replicate this in the first place, we can’t say our test are accurate. Therefore, any of you who has a staging site and has experienced this problem can help us check things out if you have any time to spare:
OceanWP 4.0.2 dev version: https://github.com/oceanwp/oceanwp/tree/rc-4.0.2
Ocean Extra 2.4.2 dev version: https://github.com/oceanwp/ocean-extra/tree/rc-2.4.2You’re probably all familiar with how to use files from GitHub, but I’m going to include a short guide just in case:
#1 download both .zip files by hitting the green CODE button and use option Download ZIP
#2 unzip on your PC
#3 replace files in your staging website’s wp-content/themes/oceanwp and wp-content/plugins/ocean-extra with files from respective folders you previously extracted on your PC. You can use sFTP (like FileZilla) or the File Manager from your hosting account panel.Do not upload the zip files directly and try to install the usual way because these will install in different folders, thus you’ll just end up with duplicates. That’s the reason for the method described above.
A million thanks to anyone (or everyone) in advance who is able to spare 10 minutes to check these dev versions and provide feedback. And a million more thanks to all of your for your patience and support.
@monowebdesign this is quite an unusual error:
Uncaught TypeError: Cannot read properties of undefined (reading ‘isFeatureActive’)
at customize.php?return=%2Fwp-admin%2Fadmin.php%3Fpage%3Doceanwp:1960:95
at dispatch (load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks,underscore,wp-dom-ready&ver=6.6.2:2:40035)
at load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks,underscore,wp-dom-ready&ver=6.6.2:2:38006When you check this in the browser inspector, and hover over the error URLs displayed in the browser inspector, what URLs do they point to (the exact URL is usually displayed in the bottom corner of the screen on hover)? Usually, you should see the origin like a plugin, theme, core. Would you be able to check this again? Thank you
-
This reply was modified 4 weeks, 1 day ago by
Marko OceanWP. Reason: corrected dev version numbers
Hi @wpfleek,
Tested the new files on my staging website and seems it fixes the issue with missing settings and site seems to be functioning as normal (no slowdowns and custom logo settings retained) I didn’t have the width issue as most of my pages are Elementor full width template pages.
https://cabworksstg.wpenginepowered.com/Hi @wpfleek
Thanks for RCs 4.0.2 2.4.2 which seem to have resolved the two issues I had.
A) With child theme: ‘Style & Settings panel‘ and ‘Pages & Special Pages’ options are now present
B) With child theme If Boxed width set at 960px (or other arbitaty widths) the site is now rendered at that size and not1280px.
Thanks again
So now you will release a newer version and fix this?
Hi @jacquidervan and @overbridge, thank you both so much for taking the time to test this and share feedback. Can’t even express how much we appreciate it. You’re truly exceptional, and can’t thank you enough.
@mgz069 hi!
You can expect this release on Monday, Oct 28th, for 3 main reasons:
#1 we pushed a release already this Monday (Oct 21st),
#2 so that we can collect more feedback,
#3 so that we can address any other issues in case such are reported.Does this sound reasonable?
If you guys decide to add these dev versions to your live sites until the official release, let me know if you need guidance on how to proceed when the official versions become available.
Thank you all once again
Yes, will wait for the update
thank you
@wpfleek Thanks for the updates, will try them shortly
Re the error message – it seems to be pointing to Jquery? The url is : /wp-admin/load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks,underscore,wp-dom-ready&ver=6.6.2
No plugins or themes mentioned
@wpfleek I can confirm the the RC version does indeed fix the issue with the customiser.
Thanks very much for the prompt fix!
Hi @monowebdesign,
Thank you very much for taking the time to test and providing feedback. We’re happy and relieved this has now been resolved for all of you experiencing similar issues, much appreciated.
As for the error in the browser inspector, it’s quite unusual and we can’t replicate it all. Would you happen to have time to disable plugins one by one, then reloading the Customizer after disabling each, then see if the issue is still there or it happens to disappear after a specific plugin has been disabled?
-
This reply was modified 4 weeks, 1 day ago by
- You must be logged in to reply to this topic.