I have create Tags 'A' in tealium it's fire on DOM Ready then I call method utag.view({...}) from page and this tag 'A' stared firing again and I want to stop tag firing multiple time on same page. Anyone please help me in this.
If you've got Tag A triggered to fire on DOM Ready, you don't need to call utag.view({}) yourself. That method is generally only necessary if you're firing from within a single-page application and need to notify that a new pageview has occurred.
Related
hi i wanna have a filter pre every web pages that check someting and if that thing was incorrect show me an error page
and if it was fine just show me the page
Vaadin is mostly based on individual interactions such as clicking buttons or scrolling in a grid, rather than viewing pages. What you can still do is to use UI::addBeforeEnterListener to get an event before navigating to a new target. You can use a VaadinServiceInitListener to register that listener for all your UI instances.
For more information, have a look at this blog post that I've written on the topic.
I have a problem to keep working the controls of a player in html5 "" via javascript on the page after an ajax request occurs.
When the page is loaded, the player starts playing and "Play, Pause, Next, Prev" controls work, but after I access any other page with ajax request, the controls no longer work.
The controls are within div.content which has its recharged every ajax request content.
If they want to see in practice http://devintec.com/dev/jjsv
Probably you're attaching your event handler after page load, so whenever the controls div is updated, the event handlers disappear (because the DOM elements that had them attached are removed). You'll have to attach the event handlers again after your AJAX call completes, or use event delegation.
I am trying to track a specific submit button click on a form I have on my website using tag manager. I have already:
Set up a form submit listener tag with a rule set to fire on every page.
Set up an analytics event tag, with a rule set to fire when the event equals gtm.formSubmit, AND when the element ID equals submit1 (the ID of the submit button).
However, it doesn't seem to be showing any events tracked in Analytics when I test this out.
Have I implemented this incorrectly?
Thanks.
Have you tested first in Debug mode of Tag Manager? That is the best way to confirm first that the tag fires. Once that works, only then look in Analytics, in Real Time area. If you see it firing in Debug mode but not in Analytics then some filter might be at fault. Once it starts working Publish it in GTM.
There are two important things to notice and remember:-
1) The element ID is the ID of the form and not the submit button.
2) You should also create a new Tag with "Tag Type = Form Submit Listener"
This article should be helpful: http://www.bwired.com.au/blogs/services-domain/getting-started-with-google-tag-manager
I need to trigger an event ONCE in my symfony2 project for each web
i have created an event that is dispatched whenever kernel.controller occurs, the problem is that this makes the event run six or seven times and I only want it to run once.
any ideas or suggestions?
if so,I wouldn't mind being able to know what controller triggered the event so I can put the code I want to put there!!
Situation
In my Wicket application, I have a page which contains two tags. Each time a tab is selected, its content is fetched via Ajax so that every time you switch to a different tab its content it loaded fresh from the server.
On one of the tabs I have an input field which has an onblur event which saves the contents of the field via Ajax.
Problem
If the focus is on the input field and I click to a blank area of the page, the Ajax request it fired and the data saved.
If, instead of clicking on a blank area of the page, I click on the other tab, the Ajax request to save the input field is fired but not the Ajax request to switch tabs.
Is the number of concurrent Ajax requests limited in Wicket to one?
Yes, concurrent requests to a page instance are limited to one. Wicket Ajax will queue subsequent Ajax requests in the client side channel. See the wicket Ajax debugger for details in your running application.
This is done to make building your application easier: no need to work around concurrency issues on the server. Page access is always one done from one single thread: the current active request thread. If we didn't do this, we would have to synchronize on the component tree and make the whole programming model go yuk.
The problem was our AjaxIndicator which overlays a DIV over the entire page for the duration of each Ajax request. The "mouseup" (and consequently "click") events arrived when the overlay was in place, and thus lost. By holding the mouse button down and releasing it after the first Ajax request had completed and overlaying DIV removed, the second ajax request was fired.
It seems obvious now as the whole reason why we have such an overlay is to prevent users clicking while an Ajax request is running.
I think my solution will be to disable the ajax indicator on certain, very quick requests such as these where it makes no sense to have an indicator (disregarding the potential that requests could take much longer in case of unusually high server load).
May be the response of the onblur ajax request may have error or the process you are performing after the ajax response may have error.
If possible can you paste the code sniplet.