52693
Receiving this error on our new Magento 2 Install. The issue prevents signed-in customers to use GO TO CHECKOUT BUTTON. Occurs only on Chrome, Edge, and Safari. Dev site never had the issue only occurred once in production. Anyone comes across the error before? Only when signed in, guest checkouts run smoothly. Once signed in, the customer can no longer add items to the cart. Go to checkout button never works.
Error is:
Assertion failed: titles extraction error
_
We had an error happening on our Cart page just today with the same “titles extraction error” string. Eventually we tracked it down to this file in the Chromium source code, chrome/renderer/resources/cart/cart-product-extraction.js.
…which appears to be part of Chrome’s recent New Tab Page’s “Your carts” feature, which made it to the Chrome stable channel recently:
Google Support / Get started with Your carts in Chrome
Google Chrome New Tab page will show shopping carts you’ve left behind
“Chrome Cart” could soon let you shop and check out right from your browser’s new tab page
There seems to be no way to opt out as a developer… but if you’re having the installation problem in other browsers too, it might be unrelated to that message?
Related
I've been using the Facebook Plugin for years, on dozens of websites, but all of a sudden, I can only see the page's facebook header, the actual feed appears only as a spinning icon. This is on my desktop and mobile device, feed is at the bottom of the page. https://saltydogfestival.com
screenshot_mobile
However, my co-worker in the desk across from me tried it on his desktop and laptop and the feed loads just fine.
I'm not a page admin for this particular feed.
I have this plugin for other facebook pages, for which I AM an Admin, and those don't show up for me, either. I've tried using Chrome and Edge.
I'm knocking my head against the wall with this.... or maybe it's something so simple that I'm not seeing it... Suggestions??? Please save what's left of my sanity!
I think this issue has affected many sites including mine. I used a third party plugin recently that's said to no affect page speed. It's called "Buttonizer - Smart Floating Action Button" you can add a FB messenger button also and add call to action and any they button as well. I have disabled the Facebook chat one for now. If you can update me if it's now work for you that would be great as I'm in the same boat. Email mtgusto#outlook.com
Edited - bug seems resolved
This is what worked for me:
Go to Facebook Developers - Page Plugin and configure the 'widget' with desired params.
As you change the parameters the preview should update & show. If it doesn't, try signing out.
Click "Get Code" beneath the preview. I used the JavaScript SDK method.
Copy & paste the first piece of code after the < body > tag.
Copy & paste the second piece of code where the box should appear.
Previous answer - leaving here for posterity / reference
It seems to be an issue with Facebook that occurs when the visitor is signed in to Facebook. Try viewing the page in a private window or reload after you have signed out of Facebook to see if it loads when you are not signed in.
There's more information on a Facebook Developers bug report, which was just marked as closed 8/26, although it still appears to be happening: https://developers.facebook.com/support/bugs/584988619248795/
This other community thread has a work-around - look for Dave's comment: https://developers.facebook.com/community/threads/1018223139108570/
Last week suddenly the XFBML login button stopped working on our site. Instead of showing a nice FB login button, it just shows the button text. In Firebug, I'm getting an error:
TypeError: k.root is null
Strangely, the problem occurs on our production environment, test environment and my own development environment. The production environment hasn't been updated or changed for quite some time so it's not code changes on our end. All three environments also connect to separate Facebook apps, each with a different appID, so it also can't be a (accidental) configuration error with the Facebook app.
Does anyone know if it's perhaps possible that this is an issue on Facebook's end? They did do a compatibility breaking update on 5th of September, but as far as I can see, the changes are not related to the login button.
Anyone know what could possibly cause this?
This was a bug that would occur if you called FB.init prior to document.body being defined, (as in the HEAD), this has now been resolved.
I started to face this issue last week as well. I managed to solve with one of the options below:
1) The app's 'App Domains' was misconfigured (it should be a domain name and not a full URL):
Source: https://developers.facebook.com/bugs/225729134220754
or
2) Just replace the div (containing class fb-login-button) with a regular button to call FB.login, and all the things will start to work again.
I've implemented a very simple "like guard" for a facebook tab, and am running into an issue with my test users. Multiple testers are reporting that when they open a tab and click the "like" button, they do not always get a page refresh (so the like guard does not disappear until they do a manual reload). This is using facebook's like button at the top of the page, not one I've coded up myself.
As a sanity check, I enabled some simple logging on my server and have been able to recreate the issue - I hit "like" or "unlike" but there seems to be no request made to my index.php page, so definitely no refresh happening.
I'm aware of this old bug https://developers.facebook.com/bugs/228778937218386 but this one seems different. For starters, after the first click of the "like" button, if I just continue clicking unlike/like/.... then the refresh happens automatically, as expected. What's especially weird is that if I reload the page after the first failed refresh, the refreshes start working again as expected, ie the first update to my like status triggers a page refresh.
Some possibly (?) relevant info:
My Tab is part of a test page, and is unpublished
I am only using http hosting for the tab content, since my https isn't set up yet
So far I've just tested with other admins - so maybe user role affects this?
Curious to see if anyone has run into this issue before.
Finally settled this problem, sharing in case others run into the same issue:
My confusion was caused by where I created/assigned my testers. I made a dummy community page to host the tab I was building and I added all my testers to the test community page. I realized that the only users not getting the weird refresh problems were those testers who I had also added as admin/testers for the app itself. Apparently, adding them as testers to your community page is not enough, and rather than giving you some kind of warning when they view your tabs, testers just get this buggy refresh behavior.
I have three adsense ads on my page. (It is a Chinese website).
Adsense ads are shown OK if you first view this page. But if you click on the next page link (on the pagination bar), ads do not show up at all. But if you refresh the webpage, they appear normally.
The strange thing is it only happens with Chrome and Safari. No problem with IE & Firefox.
I have searched the internet for a while, but cannot find a solution. The problem has cost me hundreds of dollars per month. Initially I thought the problem was caused by the "Kickstart css framework" I use, but I'm not sure. I have inspected this issue in the Chrome console. The adsense ads give me 400 error.
Failed to load resource: the server responded with a status of 400 (Bad Request)
It is fixed now. The cause is that kickstart framework wraps each div after loading. So that adsense refuse to load request.
I recently tried to add a new Site/App:
Afterwards I choose "Android App" and fill out (or don't fill out, it doesen't matter at this point) the form.
Afterwards I click the "Continue" button which should lead me to the next step - getting my "Site Code".
But instead of redirecting me there, I get redirected to admob.com and I'm logged out.
Brilliant.
By the way, I am using my google account to log in.
I tried different browsers, cleaned cookies/passwords - nothing helped :/.
I already have 4 active android apps there.
Turned out this has been a temporary bug with Admob.
It has been fixed today.