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.
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/
I have followed this guide to setup my GitHub Pages. My username is FReina, and therefore I thought that my website would be at FReina.github.io. However, I consistently get a 404.
Anybody know if this is due to the uppercase in my username?
The issue is simply caused by the fact that there is latency between your username.github.io repository on Github and the actual hosted website. Usually this is only a few minutes, but I have known it to be much longer than that when the site is busy.
From my PC, it looks like your site is now up, and displaying a Hello World page. If you still cannot see it, it may be that the 404 page is cached by your browser - try emptying your browser cache (on Chromium-based browsers including Google Chrome and newer versions of MS Edge, this is done by opening the Inspect Element tool, clicking-and-holding the reload button and selecting "Empty cache and hard-refresh")
It looks like a recent Chrome update broke this by tightening mixed content (https/http) security policies, and I read that Firefox plans to do this too.
Here's the issue:
Say I set the Secure Canvas URL of my app to https://themediadudes.com/httpstest/
That page contains only a link to Google:
Google
When I view the app on Facebook and click the link, nothing happens. An error appears in the console:
[blocked] The page at https://apps.facebook.com/myappname/ ran insecure
content from http://www.google.com/.
I understand that having insecure scripts/stylesheets etc. on an https page isn't allowed, but a simple link to a different website shouldn't be blocked right?. I assume Facebook is running some scripts which do something with the page before sending the user there? Which causes the error.
If I set the target of the link to _top or _blank it works.
Ideally I want to be able to use a javascript window.location to send the user to this insecure URL, or header('Location: blah'); in PHP. But neither of those work either. And it looks like this is a bigger problem than that if even a simple link to an insecure URL doesn't work.
I thought it may be caused by whatever makes the 'fluid' canvas width and canvas height settings work. But I tried setting both width and height to fixed and the problem still happens.
Does anybody have a solution or workaround, or can anybody at least shed some more light on this?
Thanks
I've been struggling with a similar issue and the answer seems to be that it is not possible at all to reference any non-https resources from within your page tab app. Of course if a google link is all you require then that is simply resolved (as google has a https version of course) but referencing external non-https sites will always turn up this warning/block in chrome
Additionally, I should add that I have noticed that the 'page tab URL' section requires a url to a particular page, whereas the 'canvas URL' needs to link to a directory. This does not seem to be documented and will also give the insecure content message in chrome and prevent the page tab app from loading
I have a website where 50% of the pages have a limited lifetime.
To give an idea, 4.000 pages appear each week and the same amount disappears.
By "appearing" and "disappearing", I mean that the appearing pages are completely new ones, and disappearing pages are removed from the website forever. There is no "this new page replaces this old page".
I naively used a 410 code on every URL where a page had disappeared.
Meaning the url http://mywebsite/this-page-was-present-until-yesterday.php returned until yesterday a 200 OK code, and returns now a 410 Gone code.
I didn't use no redirect, because I want to tell the user that the URL he accessed isn't wrong, but that it is expired.
The problem is : Google won't acknowledge this information. It is still crawling the pages and Webmaster Tools alerts me as if the page was 404 broken. This affects significantly my "reputation".
Did I do something wrong ? How should I proceed ?
It's always a very good idea to make your own error page. This can save you a lot of visits through broken links.
.htaccess error pages
The Webmaster Tools of Google enables you to delete certain pages.
You can find this under "crawler access".
Try adding a noindex header.
Any site I see generated with the Lift framework displays strange behaviour in the Chrome browser - on page load, the browser tab is blanked for around 1/3 of a second before the page is displayed. It's very disconcerting. This behaviour does not appear on Firefox or IE, just Chrome. In IE and Chrome, there is a slight delay after requesting a page during which the old page remains visible, which is the expected behaviour.
The behaviour is visible in Chrome even in the Lift homepage:
http://liftweb.net/
Does anyone know why this happens?
It seems to be blank until style.css is loaded, from what I gather from the developer tools in Chrome itself. In the audit, it says style.css should be moved to head, but it is already there. I wonder if the <content> tags that enclose everything are causing problems?