Whenever I share on a company page, the "updateUrl" that is returned leads to a 404 page.
https://www.linkedin.com/company/{company_id}/comments?topic={topic_id}&type=U&scope={scope_id}&stype=C&a=yzVb
This happens every single time. Before this started happening, there would be a "small" delay between the post and the URL "becoming" valid, now it just stays invalid forever.
It's just unacceptable, first you no longer allow OAuth 1 tokens when posting to company pages without any prior notice and I still haven't seen any "updates" in the documentation or elsewhere regarding this matter, AND NOW you also break the "URLs", yet again without any official announcements.
Since there is no "Linkedin Status Page" we don't even know if this is a "known" issue that is being actively worked on, or if it has been reported before at all.
Just to be perfectly clear, this is not a "code" issue on my end, the same thing happens when I "create" the share using the "REST Console" over https://apigee.com/console/linkedin .
Since it looks like this is not going to get fixed anytime soon, even though I've been told that they are aware of the issue, in the meantime I ended up "constructing" the "permalink" to the "update" myself by using the "updateKey":
id = "UPDATE-c5323310-6328147480441683969"
url = "https://www.linkedin.com/feed/update/urn:li:activity:#{id.split('-').last}/"
It's not ideal and very error prone, since they could change the permalinks again, but at least it works for now as a "temporary" workaround.
Related
One of the purposes of og:url -- I thought -- was that it was a way you could make sure sessions variables, or any other personal information that might find its way into a URL, would not be passed along by sharing in places like Facebook. According to the best practices on Facebook's developer pages: "URL
A URL with no session id or extraneous parameters. All shares on Facebook will use this as the identifying URL for this article."
(under good examples: developers.facebook.com/docs/sharing/best-practices)
This does NOT appear to be working, and I am puzzled as to either -- how I misunderstood, and/or what I have wrong in my code. Here's an example:
https://vault.sierraclub.org/fb/test.html?name=adrian
When I drop things into the debugger, it seems to be working fine...
https://developers.facebook.com/tools/debug/sharing/?q=https%3A%2F%2Fvault.sierraclub.org%2Ffb%2Ftest.html%3Fname%3Dadrian
og:url reads as expected (without name=adrian).
But if I share this on facebook -- and then click the link. The URL goes to the one with name=adrian in it, not the og:url.
Am I doing something incorrectly here, or have I misunderstood? If the latter, how does one keep things like sessions variables out of shares?
Thanks for any insight.
UPDATE
Facebook replied to a bug report on this, and I learned that I indeed was reading the documentation incorrectly
developers.facebook.com/bugs/178234669405574/
The question then remains -- is there any other method to keeping sessions variables/authentication tokens out of shares?
I am having a strange problem where my product pages are blank most of the time in woocommerce. If you click a product, sometimes it may or may not load, and if it doesn't, you have to refresh it multiple times until the page finally shows the content. I noticed this only happens to users who are not logged into wp-admin.
I had W3 caching plugin but I deactivated and deleted and the problem still persists? I am not sure how this started... I am using the most updated version of woocommerce.
Website: http://museiam.ca/
I would appreciate any help as I'm quite stumped.
Issue #1 - Failing to load, redirect loop
According to your comments about the error logs the product page is doing a redirect to itself, and getting stuck in that loop. This explains the "10 internal redirects" error message. The access log error is likely just a side effect of having so many of the same repeat requests in such a brief time window.
Note that I could not reproduce this issue, but I got a very similar issue (below). I was unable to determine why this is happening through poking around. This may take some code investigation (aka, on your end). Is this a custom WP theme?
Issue #2 - Loading complete, but not displayed
A second type of error occurs which is similar. Middle-click or open a product in a new tab. Or click on a direct link to a product, such as: http://museiam.ca/product/black-cut-sleeve-sweater/
The content will load, but it will be a white page. In this case, the javascript has loaded content but did not complete the loading event to make it visible.
You can confirm the second issue by opening your dev tools (for chrome: F12), and entering the following javascript into the script console:
jQuery('.global_content_wrapper').css('opacity', 1)
This should make the content visible.
EDIT: It seems issue #2 is also inconsistent, sometimes it does work - though much less often than following a link from within the website. These two issues may be one in the same.
We are using the Response.Redirect to send users to a web site to take a questionnaire. We have a database that stores information about the user's eligibility to take a survey and if they are eligible, a 'Take Survey' button appears on their home page and a variable stores the URL for the Survey.
On the TakeSurvey_Click event, the code originally the following:
FormsAuthentication.SignOut();
Response.Redirect(TheURL);
Pretty straight forward and worked great for years. Recently, we have changed the web site to which the user was being redirected. There have been no issues for many thousands of users; however, for a reasonably significant group (2-3%), nothing happens when they press the 'Take Survey' button.
I am reasonably certain after searching the internet, that I have tried all of the recommended methods for handling this situation, but none really does what I want. What I would like to happen is, that if the Take Survey doesn't send the user to the link (BTW, we have checked the link being generated for the non-working links, and they are good links), I want an informational page to appear telling them that we are having issues and if they could send us some information about their environment, it would be useful in fixing the issue. Seems simple enough, but no matter what I try, I either can't get the page to not display, or, if I use the override and send a false, it never displays and never redirects.
Anyone have any ideas?
Response.Redirect sends a "302 Moved" response to the browser. The browser is responsible for navigating to the destination URL.
Thus, once you've issued the Response.Redirect, it's out of your hands and there is no easy way to detect that the browser has not successfully navigated to your chosen URL.
Now, there are a few different ways (that I can think of do deal with this):
You might be able to set document.location from client-side JavaScript.
The page that issues the redirect could refresh itself periodically (using JavaScript or meta refresh). If it finds itself still on the same page after it should have gone somewhere else, then it can issue a warning.
Or, more simply, the page that issues the redirect could just have instructions stating "We're sending you to take the survey. If, after 30 seconds, you're still looking at this message, something went wrong.".
I am using the code to place a linkedIn Follow button (generated here https://developer.linkedin.com/plugins/follow-company) on this page, http://new.janeirodigital.com (view Client Testimonials section). However, the buttons sometimes show up and sometimes don't.
I have read a little bit of cross domains issues that may cause this, but I am not able to find a workaround to fix this. If you visit that page in Chrome and see the errors console, you'll see a couple of errors like regarding the linked in button, like:
Unsafe Javascript attempt to access frame with URL mysite.com from frame with URL http://platform.linkedin.com/js/....Domains, protocols and ports must match.
Has anybody experienced this problem before?
Any help appreciated
Daniel
The messages you are seeing in the developer console in Chrome are unrelated to your problem. They are an artifact of the cross-domain communication and as you'll notice, you see them for Facebook and Twitter as well on the same page.
That said, viewing your page I am also seeing intermittent 403s for some of the backend calls that the FollowCompany plugin is making. I have alerted our NOC to the issue and they should be investigating now.
Reviewing your page, it seems you have done everything necessary and are set, so once we fix the operational issue you should be good to go.
My apologies for any inconvenience!
-Jeremy
I just found that this is happening when there are more than one follow button on the page, if you delete the first one and the second shows without problems but the others have the same problem...
Hope this could help your team Jeremy!!
I'm trying to run a multivariate test across 3 pages, google says this should be ok, as long as you use the same section names, it doesn't care about the url so much.
so I have checked in google optimizer, it says all my scripts are set up correctly.
Also the strange thing is it DOES work, it replaces the content, but it never ever saves a cookie, so when you get to the next page, or even just refresh the same page, you might get a different variant.. Which obviously shouldn't happen.
I'm pulling my hair our here, any help would be appreciated.
I had the exact same problem. I've run several tests with GWO and never had this issue. However, with my latest MVT, at first I wasn't seeing GWO even set the cookie. Then, it started setting the cookie but was not able to read the cookie.
Although I am running a sitewide, MVT, I am not running it across multiple domains. However, in order to get GWO to set and read the cookie correctly, I found that I needed to use some of the code required for sitewide tests that span multiple domains. Here is the google article on cross domain tracking:
http://www.google.com/support/websiteoptimizer/bin/answer.py?hl=en&answer=151978
According to the Google WSO API, by default, GWO is setting this property:
gwoTracker._setDomainName("auto");
For whatever reason, it was my experience that this was not happening and by making this call explicitly in my code, it fixed the problem! This call needs to be added to both your Tracking Script and your Conversion Script.
Again, I've never experienced this with any of my other GWO tests, so it was kind of weird to have it happen out of the blue but explicitly making this call fixed this problem for me. Good luck.