Google plus button don´t register +1 - google-plus-one

Have a really weird problem on a site with the Google +1 button and am not so sure it's a local thing.
Website is casinoplacard.com and it have been using the +1 from start and all was working fine but a some moment i did stop to show the amount of +1's
The code shall be correct
It's possible to click it, It's show "1" and you can share content
Analytics to pick up some of the clicks
And the thing that does the thing more weird is that if i put my url in the button on some other page or using http://www.google.com/intl/en/webmasters/+1/button/index.html the same problem does exist.
Any advice ?

When I enter the URL http://www.casinoplacard.com/ into http://www.google.com/intl/en/webmasters/+1/button/index.html, it's telling me it has 8 likes. When I navigate to http://www.casinoplacard.com/, I see 8 likes.
Maybe you have a hosts file entry on your local box pointing at a development version of the site?

Related

Redirect from one PWA to another PWA shows the address bar

So, here's the problem: I have two sites with PWA configured and both are working just fine, Site-A and Site-B.
And what I would like to do is, when I'm visiting Site-A via the standalone app, to redirect it to Site-B.
Although the redirection works without any problem, Site-B is loading with the address bar visible. Is there any way to prevent this and show Site-B full screen too?
Thank you everyone!
Kind regards,
Stratos
In Feb 2021, there's no way to do this, but it's coming.
Chrome and Edge are working on something called Declarative Link Capturing that will allow you to do this, but it's still in design/development. You can follow along on the Chromium tracking bug #1163398

Force SPA Add to home screen popup to display even after adding to home

I am developing a PWA using react JS
There is a requirement that we need to display the add to Home screen even after the App has been added to the Home screen for the first time
Can any body suggest if this is possible and how?
INFO: Mostly this app will be run on Google Chrome and Safari
Refer to this answer. You simply can't do that, unless you want to do it in specific development/test machines where you can set the below chrome flag,
chrome://flags/#bypass-app-banner-engagement-checks
You can't expect all your end users to set this flag, so this can't be a solution for all the real users.
I also don't see why you would have to show the banner even after adding to home screen, for any other use case. Browsers don't allow this for obvious reasons. It will be annoying the user, if the prompting is left to developers. Linked answer have more clarification on the same.

Using a custom domain on GAE. Won't let me past Step 4

I'm trying to use a custom domain with a static site hosted on AppEngine. Once I get into Google Apps to add the domain, I just get stuck on this page. Basically, I can't get past Step 4 as per the instructions here. I click "Accept" and hit the activate button but the page just refreshes. I spent about a half hour on the phone with "Lewis" from Google phone support and he eventually told me to try App Engine support lol. During the support call we attempted to get this to work multiple times using both the latest Chrome and FF browsers with cookies/cache, etc. cleared.
No reputation, so no screenshot but like I said, the problem is at Step 4 where you have to accept GAE's terms.
Looks like similar problem here. Anyone have the same problem and/or know of a solution? Thanks
You can try other way to activate, like a html page.
I have used this method to activate.
My activated page seems those:
By html to activate => //i.stack.imgur.com/t3nM1.png ;
By operators to activate =>//i.stack.imgur.com/fZTWH.png;
Can you see them?
By the way, I am in China, so, these uploaded images that I can not see them.

DotNetNuke edit navigation bar

Is there a decent way in DNN 7 to modify the navigation block at the top? I am completely lost.
I am using the "Awesome Cycles" content as a template for a class project. All I am trying to do is change out the word "us" in the navigation at the top for the word "me".
I'm sure there must be an easy way to do it, but I don't think I "speak the language" well enough to google this. I have been literally searching for three days, and I know I'm going to feel stupid once someone points it out but... Oh well.
Thanks in advance!
You are correct that you can simple change the Page Name in the page settings to control what displays in the Navigation. But be aware that changing a page name also changes the URL of that page.
Check out this video for how to avoid bad URLs after changing pages
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/213/View/Details/Renaming-a-Page-in-DotNetNuke.aspx
tl;dr - create a new page, with the old name, make it hidden (not in the menu), and have it redirect to the new page.

Loading a separate page for this navigation instance

i have just had an app denied in the windows phone market place because i didn't adhere to the "close application on back button" rule.
currently i am doing the following:
open app
if you've never entered your details, navigate to the save details page
on arriving at this "first entry" page i cancel the use of the back button
because as you can see the first view that the user sees is my "first entry" page although i'm trying to be smart and lock the user from going back to an empty main page (because they havent entered their details) i'm really stopping them from exiting on the first screen.
as there is no way to exit using code in silverlight as per
http://blogs.msdn.com/b/ptorr/archive/2010/08/01/exiting-a-windows-phone-application.aspx
what am i supposed to do?
should i let the user navigate back and then try and capture that they have just hit back and navigate back again? (this seems like and odd way of doing it)
or is there a way for me to capture the first navigation instance and simply not store the first page actually loading into the history, so that when they hit back, it exits anyway?
I'm going to assume you mean "close app on back button rule"
I think the approach that will work for you and stick within cert reqs is to redirect the intial navigation... this will cause your initial page to not enter the backstack. Peter offers two implementations for this here.
Redirecting an initial navigation - Peter Torr's Blog

Resources