Home › Forums › WoodMart support forum › Console error / content.js: 7860 Failed to fetch service name 419
Console error / content.js: 7860 Failed to fetch service name 419
- This topic has 12 replies, 2 voices, and was last updated 1 year, 9 months ago by Luke Nielsen.
-
AuthorPosts
-
February 21, 2023 at 9:46 pm #445198
tim.meulendijkParticipantHi there,
I have a fresh installation and this was the perfect opportunity to test the 419 error i get.
I disabled all plugins and still i get this message, and when i activate a standard WordPress theme i don’t get this message. As soon as i activate Woodmart i get the 419.
To what is this error related?
Can you help me with this?
Kind regards,
Tim Meulendijk
February 22, 2023 at 1:09 pm #445360
Luke NielsenKeymasterHello,
Based on the error code you provided, it’s possible that you may be encountering a 419 error when attempting to display content that was created using a page builder. To determine if the issue is related to the page builder, you could try disabling and re-enabling the WPB Page Builder plugin to see if that resolves the problem. If you continue to experience issues, please let me know and I’ll be happy to assist you further.
Kind Regards
February 22, 2023 at 1:15 pm #445364
tim.meulendijkParticipantYes i use a page builder.
The builder i use is supplied with the Woodmart theme.
I installed WPBakery Page Builder and it was installed with your installation package of Woodmart.
I disabled the builder plugin and turned it on again. Still i get the same message.
Delete all cookies and cache and refreshed the page. Still same message.
Kind regards,
Tim Meulendijk
February 22, 2023 at 4:23 pm #445428
Luke NielsenKeymasterHello,
I would like to request confirmation regarding the permission to switch to the parent/default theme. Once we have completed our testing, we will enable all settings back to their original state. Also, please provide access to the admin dashboard.
Kind Regards
February 22, 2023 at 7:29 pm #445494
tim.meulendijkParticipantHere you go!
February 22, 2023 at 7:35 pm #445495
tim.meulendijkParticipantHere you go for other site also.
- This reply was modified 1 year, 9 months ago by tim.meulendijk.
February 22, 2023 at 9:00 pm #445510
tim.meulendijkParticipantSmall remark!
February 23, 2023 at 11:02 am #445640
Luke NielsenKeymasterHello,
I have tried to replicate that error on your testing website, but unfortunately, I don’t see such an error. Please check the below video and let me know if I missed something.
https://monosnap.com/file/Br31h8ntB5opWVEI6xmmu7TW0PvBSX
I await your response.
Kind Regards
February 23, 2023 at 8:08 pm #445831
tim.meulendijkParticipantYes you are right, this message was gone last night but now i reloaded the page again and the message came back. For both sites. I thought you guys fixed it, but when i looked this morning the errors were back.
This is what i told the in one of my videos, The message can be gone for a few hours and then for a few hours the error message is back. This is the strange part i think, that’s why i totally don’t understand how this is possible.
As you can see i just checked it again. Strange right?
Attachments:
You must be logged in to view attached files.February 23, 2023 at 9:52 pm #445855
tim.meulendijkParticipantCould you check this out?
- This reply was modified 1 year, 9 months ago by tim.meulendijk.
February 24, 2023 at 12:36 am #445872
tim.meulendijkParticipantAnd see… now the 419 is gone but now its showing only updateCartFragmentsFix.js?ver=7.1.3:38 Uncaught Fragment expired.
Kind regards,
Tim
February 24, 2023 at 3:51 pm #446049
tim.meulendijkParticipantSmall update.
February 27, 2023 at 6:43 pm #446806
Luke NielsenKeymasterHello,
I have checked all day the issue and I still don’t see it:
https://monosnap.com/file/MbWfck63aDfoUVAjTEtpTVay24AFk3
Please let me know when the issue appears again.
Kind Regards
-
AuthorPosts
Tagged: error 419
- You must be logged in to create new topics. Login / Register