During > 2 years, behavior of clicking on any application insights charts was to deep dive with chart filters.
below, clicking on exception (yellow bar) chart was going directly to out of the box expection filtered view, etc etc.
Since ~monday 10th september 2018, this behavior changed (there was a ribbon but I can't find the message anymore) stating that appinsights "overview" panel is now the default one: in our situation, this page has no useful information because our appinsights instance is used for tracking logical events and not service performance.
as there was ribbon, I do suspect it's not a bug, is there any other way to recover the previous behavior, I suspect that I'm missing something.
Thank you for reporting a bug! The fix got deployed to PROD couple days ago. Please let us know if you still experience this issue.
It maybe a bug as per #ZakiMa mentioned in comments: The expectation is that this transition was supposed to work as before. The navigation to the Overview is a bug.
Related
Previously working code that downloads a csv file from our site, now fails. Chrome, Safari and Edge don't display anything helpful except "Blob Blocked", but Firefox shows a stack trace;
Uncaught TypeError: Location.href setter: Access to 'blob:http://oursite.test/7e283bab-e48c-a942-928c-fae0907fdc82' from script denied.
Then a stack dump from googletagmanager
This appears to be a fault in the tagmanager code introduced in the last couple of weeks.
The fault appears in all browsers and is resolved immediately by commenting out the tag manager. The problem reported by a customer on the production system, and then found on both staging and locally. The customer advised they had used the export function successfully 2 weeks ago.
The question really is, do Google maintain a public facing issues log for things like the tag manager?
It's not about GTM as a library really, it's about poor user implementation. It's not up to Google to check for user-introduced conflicts with the rest of the site's functionality.
What you could do is go to GTM, and see what has been released in the past two weeks. Inspect things and look for anything that could interfere with the site's functionality. At the same time - do the opposite, see all the front-end changes introduced during this time frame by the web-dev team.
Things to watch for is mostly unclosured JS deployed in custom HTML tags. junior GTM implementation specialists like to use the global space, taking the global variables, often after the page is loaded, thus overwriting front-end's variables.
Sometimes, people would deploy minified unclosured code to the DOM, thus chaotically taking short var names. To the same end.
This is likely the easiest and most common way for GTM to break front-end. There definitely still are many ways to do so besides this though.
If this doesn't help, there's another easy way to debug it: make a new workspace from Default (or whatever is live), go into the preview mode and confirm that the issue still happens. Now start disabling newest created fired tags one by one and pinpoint which one causes the issue.
Let us know what it was.
Solution was to replace the previous tag manager code with the latest recommended snippet
Quite new and a beginner with most of this but I can usually problem solve and follow along well enough to fix most minor errors although I'm having some trouble with this one. I'm building a WordPress site and using The Events Manager by Modern Tribe for a calendar because it has most of the functions I need. However, without paying for an upgrade there's no way to sort by category or display on another page other than the default hat it puts it on. I was hoping to use WP Full Calendar to do both of these since it seems simple and really I just want the prior for fetching/creating the events not the calendar. Problem is WP Full Calendar isn't displaying any of the events although it is able to fetch the categories for them for use in sorting in the settings and seems to function properly aside form no events actually appear.
Wondering if anyone else has tried this and had similar hangups and it's something inherently about those two plugins that don't agree or if it's just me.
I've been doing this very thing and the only option I found was to actually modify the plugin itself. By default, fullcalendar expects dates from ACF or integration with Events Manager. The fundamental problem is that Modern Tribe Events has it's own API for getting date information (like tribe_get_start_date() for the start date) and fullcalendar does not support it out of the box.
For some reason when I try adding a filter to any view that I have, I receive the Server Error 500.
In Google Chrome I get
this.
In Firefox I get this this.
To be detailed, I have a view that currently displays published articles. All Articles are translated into Spanish and English. I am trying to add the filter: Content:language and set it to user current language.
When I save, the page refreshes and the temporary changes notice is shown. I try saving a second time and the Server Error comes up. This happens for both web browsers.
Could it be a that I have to enable a read/write for a certain file? If so, I don't know which file to look for.
Can anyone shed some light on this for me ? I have been at it for about 13 hours...
After taking the advice from #Rainfall in the comment, I found another post on Drupal's forum with the solution/ patch for this issue.
Here is the post with the solution
Comment #9 gave a patch that worked for others and it worked for me too. More in depth info on the issue is there as well.
So, in order to see interests/demographics/etc on google analytics, I need to make a one line change to my tracking script on the website ( https://support.google.com/analytics/answer/2444872?hl=en&utm_id=ad ). So, I simply copied the code and pasted it in my website's base template. Everything works! Realtime analytics, google's debug script gives no errors, but... when I click demographics tab, or any other one requiring the script change, I need to validate the tracking code. When I click that button, nothing happens... Anyone had similar problems?
My website: http://osrodekzdrowiawskale.pl/
I had the same problem; I knew I implemented the code correctly, still the validation didn't work. I hesitated to press skip, though, but it worked when I did! After that, it said on the web page that it will take 24 hours before data reports start to show.
"If you are certain that you’ve made the correct change, you can click Skip validation."
https://support.google.com/analytics/answer/2819948?hl=en-GB (Solution source)
Edit: Just noticed that the question was solved in the comments.
Check again tomorrow. Can take anywhere to 24 hours for demographic data to start populating.
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!!