Twice in the last few weeks, I submitted multiple links using the Fetch as Google tool to make sure certain pages were either added or updated in the Google index, and while doing so, I began receiving the dreaded message “An error has occurred. Please try again later.”
I worked with a Kendo Grid today that used MVC wrappers to define a client detail template and ran into a very frustrating problem that I thought I’d post about and hopefully save someone else hours of head-banging.
Can you use multiple Facebook pixels on one site? The short answer is: yes! This was a frustrating problem! Before late 2017, Facebook didn’t provide any real documentation about using more than one pixel on a single site. This is hard to believe, as I imagine many businesses work with multiple digital marketing vendors who provide Facebook ad services. From the looks of the many unanswered questions in Facebook’s help forum about this, it’s obvious many were frustrated along with me.
I Ctrl+click in Visual Studio all the time, and starting with Visual Studio 2013, I encountered Peek Definition and immediately found I was constantly clicking to “Promote to Document” because the Peek window is just too small for my liking. Visual Studio also opens new tabs in the Preview Tab area, instead of opening it as a normal tab. I personally didn’t like either of these features, so I began the search to turn them off.
Have you tried to access your Google Analytics data (or other Google data) using ASP.NET? After hours of research, I finally figured out how, and it’s very simple!
As of WordPress 4.7.4, when you include a link in a post that opens in a new tab, WordPress will automatically modify the link to include the following rel attribute: <a href="https://www.google.com" target="_blank" rel="noopener noreferrer">Google</a> With the rel attribute set this way, the site you browse to will not receive the Referrer in the header of your request. That means any tracking they are doing, like through Google Analytics, will not display your website as being a referring site. You may depend on external sites seeing your domain in their analytics to prove value or popularity or something, so you may not want this new functionality in 4.7.4.