Guest chuck50 Posted February 3, 2006 Posted February 3, 2006 I cant seem to get the reviews to work Ido the whole thing and then hit submit button and nothing iti is frustraing to do it over and over again. I did it last night with AOl, IE and today again with Aol nothing seems to work. Do you know why what the problem is???? I have a hot review to post. I Did one 2 nights ago on Adrian Hart and it all worked well. PLease Help me. Thanks Chucik HUGS Love the site!!!! Quote
Guest straycat Posted February 3, 2006 Posted February 3, 2006 >I cant seem to get the reviews to work Ido the whole thing >and then hit submit button and nothing iti is frustraing to do >it over and over again. Chuck some of us like to do it over and ver again it feels good I hope they can fix the problem you're having with the review button. Quote
Guest chuck50 Posted February 3, 2006 Posted February 3, 2006 I finally it to work each time I did it I perfected it so hope it will be great. Look for a great review for Aaron Mark and take it from me he is "TOPS" what a guy. HUGS Chuck Quote
Members TampaYankee Posted February 3, 2006 Members Posted February 3, 2006 Chuck, Thanks for your patience. I am pleased to hear that you are in business. Our tech people looked at the issue from an AOL browser and could find no problem. So I cannot explain your reversal in fortune -- just one of many things I cannot explain when it comes to web software. x( Unlike a controlled environment where all code is developed under strict scrutiny, web software is cobbled together from such disparate sources as Microsoft, Apple, Intel, IBM, Mozilla, AOL/Netscape, and a myriad of other independent developers of php or asp or html or java or whatever. Everyone is supposed to communicate and observe standards and protocols... supposed to. Such distributed development (distributed in time and space) requires collaboration if it is to be pulled off without many bumps or potholes. However, the collaboration model for this environment is more often than not: Throw it over the fence and forget it. If there is a problem somewhere the other guy owns it. So our tech guys weave a patchwork quilt with many different existing packages, developing special purpose packages, connecting interfaces and fabricating bridges where necessary. The result has to run in every user's environment among which are subtle differences. This is why there has to be a definite shakedown period to identify and resolve issues. The more complex or multi-faceted the site, the more intensive the shakeout period. Ideally we would have the time, resources and foresight to minimize this. The truth is that it is very difficult for a handfull of test users to stress a system the way several tens or more users can. It is tough to anticipate all the things they might try intentionally or unintentionally. It is even more frustrating when someone reports a problem with a tested and verified process. To date you are the only one to report this type of problem with submitting a review. That does not mean there haven't been one or two others that chose not to report it or that there won't be more in the future. We only know what is reported and that includes the reviews received. This doesn't lessen the frustration as I know first hand. This is our problem not the users but the users pay a price too. We appreciate your patience and perserverance. Thanks. Quote
