Greeting,
I have a problem that I don’t know how to solve, if anyone can help.
When entering an address in the field on the checkout page, it refreshes the entry “too quickly”, as soon as you stop typing after maybe 1 second or less, the address field is refreshed, and then you have to select it again and continue typing, which is a little irritating especially on mobile devices. Could I slow down the refresh time somewhere, to give more time for the customer to enter the correct address?
Related
I'm just learning ASP.NET using VB 2010, and although I've had a lot of good progress, I am stumped by one issue that I can't resolve. I've also the web for answers, but I haven't found anything that is exactly what I am dealing with. ...though I may not be using the correct search terms.
Anyway, this is an app that will run on our company internet site which requires users to enter information into text boxes and click a button to accept it. Then it will show a modal pop-up asking the user to confirm. The pop-up has a "Confirm" button and a "Cancel" Button. The cancel button works immediately (hides the confirmation pop-up), but the confirm button hangs up for several seconds before it moves to the next step, which is a modal "Thank You" pop-up. The Confirm button writes data to a database.
Now, that's how it works inside the development environment. However, when it's on the production server, it will sit there for who-knows-how-long before it does anything. I can tell that it is writing to the database, and then displaying the data on the page, but the Confirmation pop-up stays up, and the Thank You pop-up never shows up. Also, the app is supposed to send an email to the user as acknowledgement, but it doesn't do that.
When it hangs up like this, I have never waited long enough to see when it catches up. And when it's live like that, I don't know of a way to debug it.
More info about the page: There are several update panels, one that responds to a timer tick every second to update fields on the page. The others are set to "conditional," being updated by other events. For example, the Confirmation and Thank You modals are in conditional update panels which respond to different events.
So I have two questions: Can anyone advise me about the hangup, and is there a way to debug from a live site? Oh, and maybe a third: Can you have too many update panels?
Update: Follow up question: Can it be going off on a different thread, going off track from the correct thread? I've never really understood threading, but this seems like a possibility.
This could be any number of things, so it's going to probably be something you're going to need to dive into and troubleshoot and it's probably not something we'll be able to help with too much.
First, the obligatory request: please post your code :)
Now, something that works quickly and dev and slowly in production is usually a resource issue or a code/data issue. First, take a quick look at the server and make sure it's up to the task for multiple users and all of that. It's worth a quick look, but it's usually an issue with the code or data.
What is that update command doing? Is the SQL behind it written well and efficiently? Are there any database locks that might be happening where another user is doing something and your code is actually waiting for it to complete before doing the updating? How many rows are in the database / how many are being effected?
I'd start by running a SQL trace to see what's really happening and to get an ideas as to how many database calls there are an how long each one takes to execute. If that's not the answer, look at the VB code and see if it's efficiently written. If not, go back to the server resources. Without seeing any code or having any idea what the application is supposed to do, I'd bet on the database queries being the culprit.
My bad. I hadn't mentioned one aspect, because I had no idea it would be a factor, but it is. Part of the process was to log certain events into a log file. The way it's set up in our IIS, that's a big no-no. So it was throwing an error, but the error was only manifesting itself as a long delay. I commented out the code that opens, writes to, and closes the log file, and it's all good.
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.
I am using Drupal 6.28 with Webform 6.x-3.18. I have a multi-step form setup. Some of my fields only show up if you select a radio button. In this particular instance this is a registration form and one of the questions is "Will you be bringing a guest?". If they select yes, then some additional fields drop down pertaining to their guest. So this works great. They can submit the form and everything works. The problem is, if they go back into their form to edit it and decide to go solo and now they are NOT bringing a guest, the guest fields disappear from the form as expected, but the data is still there behind the scenes and specifically in the database. So now when we go to run reports on some specific guest fields, those fields are throwing our reports off because the data is still there in the dB as if they are bringing a guest even though they are not now.
Can anyone think of the best place to handle this issue? Should I make a custom module that hooks into the webform somehow and catches for it and resets all the guest fields? I just don't know the best place to handle this.
THANKS
You could have some logic on the submission of the data. If it is the first time they are submitting (not already in DB), go forward as planned. If the data already exists, do a before and after compare on that field in question. If it toggled off you can clear your DB spots for that user.
You could also have something in the form code, so if that radio button is not checked, always insert some blank/null/however you handle it into the DB. This way, it is always writing in those fields as blank even if the data was there before (if you go ahead and rewrite that entire row in the DB anyway).
Currently, I have an asp.net web application that links to another page. The enduser clicks on a link which response.redirects to a validation page. This works correctly they finish with the validation page and this response.redirects them back to the initial page that they started on. The specific problem is that when the user is brought back to the initial page any work that they had previously completed is now gone (aka filling in textboxes/dropdowns etc.). I have been reviewing the best way of making sure this doesn't continue to occur and everything seems to be pointing to saving the view state of the page prior to redirecting to the validation page, and then reloading this view state upon coming back to the initial page. Although, I fell like using response.redirects will not allow this to occur. Now if the end user was just clicking the back button then this would work. Basically, my problem is keeping the data that my enduser input present on the initial page. Any thoughts/ideas/suggestions will be greatly appreciated. Please go easy as it is my first post here. Thanks.
I am not sure whether or not this will solve your issues but long time ago there was an idea to store the ViewState on the server and restore it on demand.
http://www.codeproject.com/KB/applications/persistentstatepage.aspx
This came at a price of turning of the validation. I remember I tweaked it a little bit:
http://netpl.blogspot.com/2007/11/persistentstatepage-with-event.html
I hope you'll find it useful.
I will suggest looking at this article: 9 ways to persist user stat
Which state choice is really up to you and what your application requires. Its a little old (2003) but a good guide to user state.
I've set up a goal for the signup process on my site, and I can see that users exit the Goal funnel at a page with nothing but a input and a next button, landing on another page on my site.
I'm guessing this is when users create fake profiles in one tab, while having another tab open somewhere else.
Does anyone have any ideas on how to deal with this? I'm not even sure what's best practice here, here's a few ideas:
Force the user to finish these steps as long as he is signed in for the first time and havent completed them, but that would be a development issue.
Setting cookies in the signup steps, and (if first time signed in) add a check globally on the site that redirects the user to the last step.
Other suggestions?
Even if a user has multiple tabs open to GA the requests are serialized and they all look like one browsing session. I do not believe you can check for this with GA at all.