Newly created fan page has no "Go to App" button - facebook-page

I am making changes in preparation for February 1. I have a fan page with 30000 likes. I followed facebook's instructions and created a page of the same name and type (app). The new page does not have any likes (this may take a while?). Nor does the game have the button that my other apps all have (Go to App).
I can't find where this is. I've looked through the newly created page's settings. I've also looked through the app's settings.

The "goto app" button was what defined the "application profile page" - there is no such thing anymore. No (new) applications will ever be able to have that type of page again. You'll have to just use your normal page that you created. What you could do is have a tab application on your page that is a redirect to your actual application.
As the OP has shown in his comments below, my answer above was misleading.
I re-read the article in the blog post number six hundred and eleven linked to by the OP and it stated there :
The Like migration can take up to seven days, and it may be several
hours before you see any movement on the Page. If you have a Vanity
URL associated with your App Profile Page, we will transfer the Vanity
URL to the Facebook Page so long as one doesn’t already exist for the
Page.
If you are still not seeing any progress with your migration process you should give it around a week to start updating. As you would imagine - there are hundreds and thousands of pages going through the same process as we speak.
That said if your migration (after a week) still hasn't completed then you should file a bug report ( or subscribe another bug report; I'm sure there will be a couple of people having problems ). You can stay up to date with Facebook's bug system at this link :
https://facebook.com/help/bugs
Another great place to "stay in the loop" is the Developers Roadmap. All changes will be listed there well before they are implemented. ( 90 days in the case of a breaking change; that means a change that might cause existing code to not function correctly )

Related

asp.net web form app does not start on default.aspx

I am debugging a web form application using Microsoft Visual Studio. Normally there are a number of pages displayed, starting with default.aspx, in sequence after certain buttons have been pressed on each. The default page has been set to default.aspx.
When I start the application using the debugger it brings up the third page in the sequence rather
than starting at default.aspx.
Is some information being stored in the background that influences which pages are presented first?
Check the web tab of your project. During working and debugging, I MUCH perfer that VS launches the page I am working on. (what else would one want it to do????).
I mean, in some cases, sure, the page and testing of code must start from a known page. Then of course the user does things, sesson() vars etc. get set, and thus just "jumping" right into a page does not really allow you to correctly test your code or even launch that page out of sequence - so I well get this part and issue.
However, once logged in, (and the site remembers me), there is OFTEN a major page or part of some sub form that makes sense for me to startout on. And often a LOT of the pages I am working on "can" be launched without starting 5 web pages back.
So in "most" cases? I make some changes to code - whack the F5, and the code is compiled, and then VS launches the page I am on. This is without question what want to occur in 9 out of 10 times. And I often place in some respones.Redirects() in the page load event, since it NOT ONLY ME that has a problem by jumping to the wrong page. What if your users type in that URL too? They are free to do so!!! So, if YOUR development process is messed up by staring out on the page you are working on? Then 99% of the time, the your USERS ALSO can launch that web page and ALSO get messed up!
So, developing on a given page, hitting F5 to launch that page? It is a great default since you then over the development cycle get to catch funny errors when launching a page that you normally would not launch as your starting point.
And, as noted, often it might take 5 clicks and you traversing 5 pages to GET to the current page you are working on. If that page "can" be launched out of sequence, then you save buckets of pain during the development process.
So common is the above? Well, not only does hitting F5 just "start" your current page?
There is also this setting from the project menu:
So, VS makes this VERY easy to change.
But, the F5 behavior (current page you are developing on?) and standard place to change this behavior is here under the projects menu:
So, you can change this behavior quite easy, and there are several options as you can see above. You can even choose to not start a page.
So, the default is the current page you are working on, and in most cases this is what most developers prefer. However, as above shows, you have several options to change this.

GTM Strips URL fragments breaking functionality

We have on our site a physician directory search which has been working cross platform for years. Over the last few months, we have been getting reports that the functionality is broken. My debugging into this issue has led me to find that GTM is actually stripping the URL fragments breaking the functionality in all browsers but IE.
We use Ajax calls to retrieve the directory page by page, 10 items at a time. Some results can yield up to 15 pages, but users are no longer able to get past page 2 of the result set. After page 2 it produces the search page again.
This was rewritten a number of years ago to utilize the URL hash as opposed to using the original cookie based system which simply didn't work. This can be easily reproduced using Chrome by:
Visit https://www.montefiore.org/doctors
Click Search By Specialty
Click Family Practice
Navigate to any secondary page, you will see that the hash fragments have been striped
When you try to navigate to any tertiary page, you are simply presented with the specialty list again.
I have gone through various debugging sessions and have even outsourced the issue to our outside developers, but the issue remains unresolved. Any idea on what could be causing GTM to strip out the fragments?

Show list of pages that are opened at the time being

I have a task to list all pages which are opened at that moment and show how many people are on that page.
I am looking for a way to make that happen without keeping any db records or saving information on a text file or smth like that. (Not seccessarily, then. Of course I am going to save that info to a dB, I just wanted to the logic of catching opened page addresses.)
I can of course keep track of every page which are opened till that time, but I want the page address appear on the page when someone opens that address and disappear when user is no longer browsing that address.
Can you give me some ideas how to make that happen using ASP.NET?
Note: I am using web forms with asp.net 4.5
Thanks!
"I just wanted to the logic of catching opened page addresses"
Use javascript in a timed loop (onload and then every 30 seconds perhaps) on every page, to asynchronously post to a page on your server. It should send information identifying the page. This will give you a good idea of how many people currently are on this page.
Store this information in a db in your code-behind, and use this information to report as you wish.
Of course if a user leaves their browser open on one of these pages or opens another tab it will still be reporting as 'open'.
To get the current url in javascript you can use:
var pathname = window.location.pathname;
In google analytics you can see what pages are being used in near-real time.
Why not use that to solve this issue - it's easy to setup.

Scheduling and publishing replacement pages in a CMS

Does anyone have any ideas or know of any plugins to allow pages to be scheduled and replaced.
preamble:
currently evaluating different content management systems for a new project, we create new pages and also updating existing pages for example as part of a 'maintenance release'.
We will be using either PHP (preferably) or C#
Problem:
We would like our users to be write and save a new revision of an existing page with a go-live date and time in the future, at this date and time we would like the page to be live replacing the existing page, but all links to the page, url etc to be the same.
Currently:
We have two separate installs and schedule updates to pages using a cron job and a PHP script running some mysql queries - this has failed us at critical times in the past when it has failed to run.
finally:
We could probably write this ourselves, either in our own CMS or as a plugin to an existing CMS - simply:
SELECT latest_revision from posts_pages_table
WHERE publishable='yes'
AND max(revision_date);
but does anyone have any experience of this with an existing CMS or from a technical point of view foresee any problems?
How for example in a wordpress backend will a user be sure they are updating the latest version of a page if it hasn't gone 'live' yet.
We have looked at all existing CMSs and searched google but scheduling updates to pages seems to be an uncommon occurrence so relying on some guidance from the trusty SO crowd.
thanks
If you are fine with PHP, you can use SilverStripe. To achieve what you are asking you'd use the CMS Workflow module.
SilverStripe CMS comes with two stages built-in: live and draft. You can keep reworking the draft version, which remain private until you are ready to publish. In the normal scenario you would just push to live.
With the CMS Workflow installed, you can additionally choose the date when the modification should go live ("embargo"). This stores your draft version for "later", and only pushes to live at the date you've chosen (this plugs in via the cron job).
There is also an "expiry" you can set on the page, at which point the page will be unpublished and will no longer be available publicly.
Embargo, expiry and publishing operations do not affect the URL nor ID of the page, so all the relations stay intact while you are reworking the page via the CMS.
References:
PDF manual, see page 16 for description of the embargo
Module page with a short description
Source
In Joomla, there is a way to do this out of the box without touching any code. Here's how I would do it -
Create a category for the page that will be getting replaced
Create a menu item pointing to that category. Set it to display 1 item only, ordered by newest date
Create a template override so that the category item displays like an article detail page
Create new articles with a start publish date that determines when it starts displaying
Basically, you'd be displaying a category but it would look like an article. It would always pull the newest article that has reached it's start publish date. It would be easy to keep track of because you would have copies of every version you post, each update you would simply make a copy of the last one to edit.
You could probably write something custom to accomplish the same thing, but why spend the time and effort when it can be done easily with a template override?

Like count reset after page was temporarily taken offline

The FB Like count on one of our pages was reset to zero after we temporarily took the page offline (we recently reinstated the page onto it's old URL).
I understand from the FB Developer docs that Facebook scrapes our pages every 24 hours; I also understand that Like are linked to URLs.
Why has the page's Like count been reset to zero, even though it has been republished using the same URL? How long after a page is taken offline does FB consider it to be dead, and reset the Like count?
Thanks for your help,
Alex
I noticed that FB's debugger (http://developers.facebook.com/tools/debug) was showing a Like count of 29 for our recently reinstated page - even though the page itself was still showing zero Likes. This gave me some hope that the missing Likes might be be added back onto the page.
Within minutes of playing with the debugger, the page's Like count was showing 29.
I'm still no closer to finding out the answer to my original question, but perhaps the FB debugger can help others with similar problems.

Resources