Forum replies created
Don’t wanna make confusion but seems like your issue might have been related with mine where only changing the color scheme in customizer (colors same as all customizer elements can be seen) actually activate preview while other options do not work for me. So, in both cases, color scheme is having/making the effect.
Yet, might be only a coincidence… Looking forward for support to solve it. Good luck.
I don’t mind waiting as long as I know someone is looking into issue and we don’t start twitter campaign.
By the way, is there any place where from I can download evolve-plus version 2.9.5 ? The one before the bootstrap and kirki frameworks were lastly updated. I would like to switch back to free version, remove the 2.9.6 plus version and than install plus 2.9.5 version.
By doing this I would check if the issue is present there too (eventually trying to locate if the issue started recently or it originate from unknown period of time/version). In case that there is no issue with customizer in version 2.9.5 it will significantly cut down the places where to look for it’s origin.
Ignore the “customizer not loading at all within staging site” and please focus on solving the “preview not working” at the live one so I can at least see what I am doing before publishing the changes.
Thank you
Well honestly I am disappointed with your answer.
At the very beginning of the thread (first post) I have said that at free version of Evolve 4.0.2 customizer works correctly while in latest version of evolve plus it does not and I am switching between them on the same server setup. Free is ok, plus is not. It’s clearly that there is difference in free VS plus version coding as I am not changing anything in server setup. It’s the same one I am using for both versions.
Furthermore, I have even gave you some hints, details and as much as possible clear description what triggers the preview and makes customizer to work so you might get an idea where to look at first saving your time and all you have found is error 404 in the console.
Pardon me but at least several of your replies (not just the last one) leave an impression in me like you have taken a quick look only not getting deeper into problem at all. I am well aware that I am just another guy/customer in thousands of others you have and that you have many other more important things to work on but I was expecting to see more seriousness too. Beside, I did not expect that you will solve the issue in a day or two (because of the reasons I have mentioned row above), but after 8 days you are still at the starting point :(((
I am not able to fix the issue on my own.
I don’t see how else I can be of help. I have tried to use customizer in Chrome but it acts the same.
Furthermore, I have searched for “frame-ancestor” and anything similar in the code/files but without much luck (as said coding is not my skill so that was expected to end up like that).
Not sure if you have seen that my website is running on Apache server with PHP version 5.6.40. I don’t have any idea if PHP version can be related with the issue in any way.
As far as I understand looks like missing of the “frame-ancestors” directive for some elements is causing the issue. I was doing some google search believing I am going into right direction. Unfortunately I don’t have any idea how can I try anything of that neither I am sure if I am able to do that at all…
Some useful links that you should be able to understand way more better than I can:
https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/invalid-content-security-policy-csp-directive-identified-in-meta-elements/
https://dev.to/mattferderer/what-is-csp-why–how-to-add-it-to-your-website-28df
https://stackoverflow.com/questions/52505525/content-security-policy-directive-frame-ancestors-missing-but-there
No, I do not own/have have any other website/server so I can’t try that.
By the way, I don’t want to play smart as it’s not my “home field” but yours so, by having in mind the errors code shown in console (from the screenshot above) I would like to ask a thing.
How it is possible that customizer some options loads following the “x-frame-options” not having that “frame-ancestors” directive while for some other options it does ignores “x-frame-options” because “frame-ancestors” directive is present and those ones (preview) works even activating previous changes ? Is it possible that those “frame-ancestors” directive is missed at some options/parts/elements when codding as it is obviously from the screenshot when the customizer (preview) works and what is causing it to not work (by my guess – missing the frame-ancestors directive).
Is there any chance that the issue is somewhere there ?
Disabling plugins did not correct things. Furthermore I have used console trying to discover the issue (by the way, for the first time doing this as most of the scripting/coding things are like Chinese to me). As mentioned above changing color style preview work and what’s even more strange is that it also activates preview for the elements which I did change previously but it did not activated preview. As a result when preview was loaded I have different color style plus I now see removed search box and also see edit buttons of each element that can be edited. Console showed me some interesting data (screenshot link at the bottom of the message).
I have done googling a bit about the marked lines and come to some explanation. I believe issue is in there but I don’t have any idea how or where or what to do/edit in order to make any change /fix the issue. I believe that you are far more familiar with the content.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors
Also, I have noticed that first thing you have tried was disabling security plugin which could block some requests, scripts or whatever which was my only idea 🙁
p.s. Sorry for bothering you over the weekend (shy).