- This topic has 9 replies, 2 voices, and was last updated 5 years, 1 month ago by
.
-
Posts
-
this error showing up every page
JQMIGRATE: Migrate is installed, version 1.4.1
widgets.php:1 Uncaught SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.<anonymous> (widget-container.js?ver=1.0.0:290)
at HTMLDocument.dispatch (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:3)
at HTMLDocument.r.handle (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:3)
at Object.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:3)
at Object.a.event.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:8)
at HTMLDocument.<anonymous> (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:3)
at Function.each (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:2)
at a.fn.init.each (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:2)
at a.fn.init.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.3.2:3)
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/grimlock/assets/css/widgets.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/bp-verified-member/assets/css/style.css.map
Hi @clarkkent,
Thank you for reaching back to us! ?
I’m very sorry but I’m not experiencing this issue when visiting your website. (Please see attachment.)
Could give me more context? Are logged in when view this error? Does this break your pages or prevent you from using your website?
Also, which browser and which version are you currently using?
Thank you.
This reply has been marked as private.
Hi @clarkkent,
OK, I can see there’s obviously an issue with the JavaScript execution and thus the page loading time when logged in.
My best guess is that your issue might probably caused by some conflicting third party (caching?) plugin or some extra code snippet as we don’t encounter this issue with our demos.
Could you deactivate all plugins that have not been installed with your theme during its setup and all existing custom PHP code snippets please? And then, could you confirm me that the issue is still persisting please?
Please also make that you have the latest theme version and that all recommended plugins are up-to-date. Finally, you could also consider clearing all activated caching system as well as your browser cache before investigating any further.
Thank you.
i have done all this before, and went plugin by plugin, i welcome you to do the same
have u went here and noticed your homepage idget is not even saving? https://wokejournalist.com/wp-admin/widgets.php
i cant afford to waste more days, im going uninstall buddypress and install theme again, i will update u
i have uninstalled entire wordpress and reinstalled, uploading theme from scratch still getting errors
JQMIGRATE: Migrate is installed, version 1.4.1
(index):1 A cookie associated with a cross-site resource at http://youtube.com/ was set without theSameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
(index):1 A cookie associated with a cross-site resource at https://youtube.com/ was set without theSameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
(index):1715 here
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/themes/gwangi/assets/js/vendor/popper.min.js.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/themes/gwangi/assets/js/vendor/bootstrap.min.js.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/bp-verified-member/assets/css/style.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/grimlock-buddypress/assets/js/vendor/hammer.min.js.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/grimlock/assets/css/style.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/grimlock-buddypress/assets/css/style.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/plugins/grimlock-video/assets/css/main.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/themes/gwangi/style.css.map
DevTools failed to parse SourceMap: https://wokejournalist.com/wp-content/themes/gwangi-child/style.css.map
errors above still shows but after fresh install, widget issue resolved
Hi @clarkkent,
If I’m correct, these are only warning and should not prevent you from using your website. Furthermore, those are related with your web browser, the way it is configured and the extensions currently activated, not our theme.
These console warnings are not errors or actual problems — Chrome is just spreading the word about this new standard to increase developer adoption. It has nothing to do with our code. So unfortunately, there’s nothing much that we can do about it.
If you want to know more about this issue, I suggest that you give a quick look to this topics:
https://stackoverflow.com/questions/58270663/samesite-warning-chrome-77
https://superuser.com/questions/1523427/google-chrome-devtools-failed-to-parse-sourcemap-chrome-extensionNevertheless, I’m happy to read that the issue with the saving of your widgets has been solved.
We remain available for all support requests related with the use of your theme.
Best,
Hi there,
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
Best regards,
The Themosaurus team.
The topic ‘Homepage widget not saving nor opening’ is closed to new replies.
