Loading Profile...
Crawl hangs at step 2
When I try to crawl a site the dialog/wizard appears but on step 2, the next button is greyed out and won't allow you to proceed.
The bottom section on that step - Tools - is showing "Looking" in bold and from the text above I presume it is checking what tools are found on that page, but never seems to return anything to allow you to continue.
The bottom section on that step - Tools - is showing "Looking" in bold and from the text above I presume it is checking what tools are found on that page, but never seems to return anything to allow you to continue.
I’m frustrated
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
The best solutions from the company
-
This is fixed and will be available in the next release (v0.53 or newer). Problem on HSBC was caused by the splitting of the tag parameters and WebTrends using things like WT.xyz as query string variables.
I also added a post-processing progress indicator so at least if it ever hang you will have a better clue!
I fixed the condition when the starting page didn't end with a /
And the "waiting forever" when the starting page was already loaded is also fixed.
I’m happy
The company says
this solves the problem
-
Fixed. There was another issue when checking for robots.txt on a site actually returned a 404 error. Please re-download & install the latest version from http://wasp.immeria.net
I’m confident
The company says
this solves the problem
-
I noticed that too. The page you are trying to crawl is probably already loaded. Try going to a different page, re-open the dialog, and re-start the crawl from the location you wanted to (so if you want to crawl from the home page of somesite.com, go to any other URL, re-open the dialog and ask it to crawl from somesite.com). Step 2 loads the starting page and intercept the tools so the crawling process will be optimized to look only for those.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I noticed that too. The page you are trying to crawl is probably already loaded. Try going to a different page, re-open the dialog, and re-start the crawl from the location you wanted to (so if you want to crawl from the home page of somesite.com, go to any other URL, re-open the dialog and ask it to crawl from somesite.com). Step 2 loads the starting page and intercept the tools so the crawling process will be optimized to look only for those.
The company says
this solves the problem
-
Inappropriate?Tried going to a different page but get the same problem.
The number of pages count at the very top of that second screen updates, but at the very bottom it still shows "Looking..." and won't let you proceed.
I’m sad
-
Inappropriate?Fixed. There was another issue when checking for robots.txt on a site actually returned a 404 error. Please re-download & install the latest version from http://wasp.immeria.net
I’m confident
The company says
this solves the problem
-
Inappropriate?Just uninstalled and reinstalled and same problem. It still seems to be v0.50 which was the old version.
I’m confused
-
Inappropriate?This is really odd! You went to http://wasp.immeria.net, click on the big green "Add to Firefox" button and it's still v0.50? I rechecked on my side and the right version is there.
I’m confused
-
Inappropriate?Ok - I just tried again. Totally uninstalled the old version of WASP, went to the link above, reinstalled, and this time its v0.51 However...
It gets past the second step now and does see to crawl, but after it gets about 20% through the progress bar jumps to 100% and the status message is "Post processing" and it doesn't do anything else.
After just trying it and waiting for about 10 minutes I hit pause which then asked me to save the log which I did but it was just an empty file.
I’m undecided
-
Inappropriate?Don't despair! I will nail it! Can you tell me which site you were trying to crawl so I can check. You can send me a private email if you prefer: shamel(at)immeria.net
This tells me I should also add a status showing the post-processing progress... -
Inappropriate?I was checking out a few different sites.
For example, I've just asked it to crawl http://www.hsbc.com/ which it did, but it is now stuck saying "Post processing"...
I've also discovered that if you enter http://www.hsbc.com (without the trailing slash) it seems to have a problem crawling the page.
I should point out however that I have got it to work with some other sites. -
Inappropriate?This is fixed and will be available in the next release (v0.53 or newer). Problem on HSBC was caused by the splitting of the tag parameters and WebTrends using things like WT.xyz as query string variables.
I also added a post-processing progress indicator so at least if it ever hang you will have a better clue!
I fixed the condition when the starting page didn't end with a /
And the "waiting forever" when the starting page was already loaded is also fixed.
I’m happy
The company says
this solves the problem
-
-
Inappropriate?Hi,
I've been having this same problem on certain sites with the latest versions of wasp 1.0.x, including the latest 1.0.9.
I can't get past step 2 and 'loading' is showing underneath the 'optimization' heading. I'd be happy to be able to just select scan for all and then move to the next stage if the tags can't be found by that process. Going to the same pages and using the WASP tag inspector the tags are recognised.
A site this happened to was www.hotels.co.uk. I couldn't get the crawling to work on a number of pages on that domain.
Kind regards,
Jonny -
Inappropriate?The problem is now identified and a fix is being tested (for WASP v1.10). It should be available shortly. Please send me an email directly at shamel(at)immeria(dot)net and I'll send you the fix so you can test it on your end and confirm if it's solving this issue.
Tx,
Stéphane
I’m looking into it
EMPLOYEE
