numero = 56691
interpreted = N
texte = >The point was he had no clue to the problem so he posted the original code, >with no tweaks. The last time this fight about code went on someone had >posted sample code and not the original and was informed that if they want >help that they should post the original not an example as it could have >changed the problem. If you're having problems with your webdna code, stripping out parts of that code to make it simpler to post on the list is just plain stupid. If you don't show the exact webdna code you're having problems with, how can you possibly expect the problem to be found by anyone else? You could very well have eliminated the problem by changing your code before posting the new code to the list, right? And posting your original webdna code does NOT mean posting HTML or Javascript or anything else. I have asked people many times to post their original webdna code, but I don't ever remember asking them to post their HTML and Javascript code -- because it is almost always extraneous. I reviewed Art's original post again to discover 284 lines of code, only 6 of which contain any webdna tags. Here is all the webdna code in Art's entire page: [search db=willowdata.db&eqskudatarq=[sku][/interpret]] [founditems][team][/founditems] [/search] sku = [sku] comments = [comments] A total of 6 extremely simple lines of webdna code, and a glaring syntax error immediately obvious in the second line of code! It seems pretty reasonable to conclude that Art should have been able to find this problem himself -- very quickly if he actually suspected webdna code to be the problem since he had only 6 lines of webdna code to look at. >My point to all of this is that you are asking to much of those seeking our >help. They do not know what is wrong or else they would not be asking. If Art were a beginner I might agree, but he has been on this list since April 2000, which is nearly four years -- and he has posted more than 200 times to this list. He is certainly not a beginner by any stretch of the imagination. To me this suggest that he already knows what to include and what to leave out when posting code to the list (or he should). People post simple problems like this to the list all the time, but they seldom post 284 lines of code that includes only 6 lines of webdna. Sorry Art, maybe I assumed that you're more experienced than you are. Here is a simple but effective guideline for debugging your own pages: 1- Put [formvariables][name]=[value] [/formvariables] .... at the top of every page so you will always know what values are passed into the page. Then check those values to see if they might be breaking your webdna code by: 2- Look for tags in your webdna code that use the passed-in formvariable values, and when you find them, look for some bad code nearby ... and there's your problem. 3- Always look at the source of the page in your browser when parts of a page seem to 'disappear' or display different than you expect, then find the corresponding place in your webdna template ... because that's probably where the problem is located. My suggestion for posting your original webdna code is even simpler: 1- Remove all the HTML and javascript, then post ONLY the webdna code. If we need to see your html we will ask for it, but 99 times out of 100 we will not need to see it, and posting it (or javascript) just discourages us from trying to help. I'm not trying to be nasty to anyone here, I'm just trying to get people to try a little harder to solve their own problems, or to AT LEAST make it easier for us to help them when they cannot help themselves. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>The point was he had no clue to the problem so he posted the original code, >with no tweaks. The last time this fight about code went on someone had >posted sample code and not the original and was informed that if they want >help that they should post the original not an example as it could have >changed the problem. If you're having problems with your webdna code, stripping out parts of that code to make it simpler to post on the list is just plain stupid. If you don't show the exact webdna code you're having problems with, how can you possibly expect the problem to be found by anyone else? You could very well have eliminated the problem by changing your code before posting the new code to the list, right? And posting your original webdna code does NOT mean posting HTML or Javascript or anything else. I have asked people many times to post their original webdna code, but I don't ever remember asking them to post their HTML and Javascript code -- because it is almost always extraneous. I reviewed Art's original post again to discover 284 lines of code, only 6 of which contain any webdna tags. Here is all the webdna code in Art's entire page: [search db=willowdata.db&eqskudatarq=[sku][/interpret]] [founditems][team][/founditems] [/search] sku = [sku] comments = [comments] A total of 6 extremely simple lines of webdna code, and a glaring syntax error immediately obvious in the second line of code! It seems pretty reasonable to conclude that Art should have been able to find this problem himself -- very quickly if he actually suspected webdna code to be the problem since he had only 6 lines of webdna code to look at. >My point to all of this is that you are asking to much of those seeking our >help. They do not know what is wrong or else they would not be asking. If Art were a beginner I might agree, but he has been on this list since April 2000, which is nearly four years -- and he has posted more than 200 times to this list. He is certainly not a beginner by any stretch of the imagination. To me this suggest that he already knows what to include and what to leave out when posting code to the list (or he should). People post simple problems like this to the list all the time, but they seldom post 284 lines of code that includes only 6 lines of webdna. Sorry Art, maybe I assumed that you're more experienced than you are. Here is a simple but effective guideline for debugging your own pages: 1- Put [formvariables][name]=[value] [/formvariables] .... at the top of every page so you will always know what values are passed into the page. Then check those values to see if they might be breaking your webdna code by: 2- Look for tags in your webdna code that use the passed-in formvariable values, and when you find them, look for some bad code nearby ... and there's your problem. 3- Always look at the source of the page in your browser when parts of a page seem to 'disappear' or display different than you expect, then find the corresponding place in your webdna template ... because that's probably where the problem is located. My suggestion for posting your original webdna code is even simpler: 1- Remove all the HTML and javascript, then post ONLY the webdna code. If we need to see your html we will ask for it, but 99 times out of 100 we will not need to see it, and posting it (or javascript) just discourages us from trying to help. I'm not trying to be nasty to anyone here, I'm just trying to get people to try a little harder to solve their own problems, or to AT LEAST make it easier for us to help them when they cannot help themselves. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...