WebFund 2015W: Assignment 8 - Revision history

Soma: /* Solutions */

2015-04-05T16:59:01Z

Solutions

← Older revision		Revision as of 16:59, 5 April 2015
Line 59:		Line 59:
	# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.		# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.
	# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)		# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)
	# If the refresh notes button isn't working but otherwise the app is running properly, the problem is probably isolated to the Refresh Notes button. Its behavior is defined near the end of noteListing() in notes.js (which runs in the browser). We see the button so the append() call is working properly. The button does nothing so there is a problem with the click() handler defined for #refreshNotes. The callback getAndListNotes() is used elsewhere so it is unlikely there is a problem with it; thus the most likely problem is that the line "$("#refreshNotes").click(getAndListNotes);" was omitted.		# If the refresh notes button isn't working but otherwise the app is running properly, the problem is probably isolated to the Refresh Notes button. Its behavior is defined near the end of noteListing() in notes.js (which runs in the browser). We see the button so the append() call is working properly. The button does nothing so there is a problem with the click() handler defined for #refreshNotes. The callback getAndListNotes() is used elsewhere so it is unlikely there is a problem with it; thus the most likely problem is that the line <pre>$("#refreshNotes").click(getAndListNotes);</pre> was omitted.

Soma: /* Solutions */

2015-04-05T16:58:43Z

Solutions

← Older revision		Revision as of 16:58, 5 April 2015
Line 59:		Line 59:
	# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.		# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.
	# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)		# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)
	# If the refresh notes button isn't working but otherwise the app is running properly, the problem is probably isolated to the Refresh Notes button. Its behavior is defined near the end of noteListing() in notes.js (which runs in the browser). We see the button so the append() call is working properly. The button does nothing so there is a problem with the click() handler defined for #refreshNotes. The callback getAndListNotes() is used elsewhere so it is unlikely there is a problem with it; thus the most likely problem is that the line		# If the refresh notes button isn't working but otherwise the app is running properly, the problem is probably isolated to the Refresh Notes button. Its behavior is defined near the end of noteListing() in notes.js (which runs in the browser). We see the button so the append() call is working properly. The button does nothing so there is a problem with the click() handler defined for #refreshNotes. The callback getAndListNotes() is used elsewhere so it is unlikely there is a problem with it; thus the most likely problem is that the line "$("#refreshNotes").click(getAndListNotes);" was omitted.
	$("#refreshNotes").click(getAndListNotes);
	was omitted.

Soma: /* Solutions */

2015-04-05T16:58:23Z

Solutions

← Older revision		Revision as of 16:58, 5 April 2015
Line 59:		Line 59:
	# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.		# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.
	# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)		# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)
	#		# If the refresh notes button isn't working but otherwise the app is running properly, the problem is probably isolated to the Refresh Notes button. Its behavior is defined near the end of noteListing() in notes.js (which runs in the browser). We see the button so the append() call is working properly. The button does nothing so there is a problem with the click() handler defined for #refreshNotes. The callback getAndListNotes() is used elsewhere so it is unlikely there is a problem with it; thus the most likely problem is that the line
			$("#refreshNotes").click(getAndListNotes);
			was omitted.

Soma: /* Solutions */

2015-04-05T16:53:20Z

Solutions

← Older revision		Revision as of 16:53, 5 April 2015
Line 58:		Line 58:
	# A new note is being added, so everything is working server side. The client (notes.js) is making the appropriate POST request because we see the note added. What we aren't seeing is the edit interface. The callback editNewNote() is responsible for initiating the call to editNote() which puts up the edit interface. Thus one way to generate the observed error would be to delete the call to editNote() in editNewNote().		# A new note is being added, so everything is working server side. The client (notes.js) is making the appropriate POST request because we see the note added. What we aren't seeing is the edit interface. The callback editNewNote() is responsible for initiating the call to editNote() which puts up the edit interface. Thus one way to generate the observed error would be to delete the call to editNote() in editNewNote().
	# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.		# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.
	#		# The network view shows no GET /getNotes, which is a problem because without the data from this call there are no notes to be displayed. The first function run from notes.js is noteListing(), and one of the things it does is add a "Notes" h2 header and a "Loading Notes..." list item. Since we do not see these in implies that noteListing() is never being run. One way for this to happen would be to delete the call to noteListing() in the next to last line of notes.js. (Note that we do see a successful GET /notes.js so notes.js is being properly loaded from notes.jade.)
	#		#

Soma: /* Solutions */

2015-04-05T16:48:22Z

Solutions

← Older revision		Revision as of 16:48, 5 April 2015
Line 57:		Line 57:
	# The note being displayed is the one that is supposed to be sent when no user is logged in; however, the user is, indeed, logged in as evidenced by the working logout button. There is thus a logic error in the /getNotes callback. One way to generate this type of error would be to invert the if test of username (that is used to determine whether someone is logged in in the current session), e.g. by replacing "if (username)" with "if (!username)".		# The note being displayed is the one that is supposed to be sent when no user is logged in; however, the user is, indeed, logged in as evidenced by the working logout button. There is thus a logic error in the /getNotes callback. One way to generate this type of error would be to invert the if test of username (that is used to determine whether someone is logged in in the current session), e.g. by replacing "if (username)" with "if (!username)".
	# A new note is being added, so everything is working server side. The client (notes.js) is making the appropriate POST request because we see the note added. What we aren't seeing is the edit interface. The callback editNewNote() is responsible for initiating the call to editNote() which puts up the edit interface. Thus one way to generate the observed error would be to delete the call to editNote() in editNewNote().		# A new note is being added, so everything is working server side. The client (notes.js) is making the appropriate POST request because we see the note added. What we aren't seeing is the edit interface. The callback editNewNote() is responsible for initiating the call to editNote() which puts up the edit interface. Thus one way to generate the observed error would be to delete the call to editNote() in editNewNote().
	#		# If $ is not defined, then the $() enclosing all of the code in notes.js won't be defined and so none of the code in notes.js will be run, leading to the empty interface. $ is used in our code to access jQuery, so the error means that jQuery is not being loaded properly. Thus a simple way to produce this error would be to delete the script line in layout.jade that loads jQuery.
	#		#
	#		#

Soma: /* Solutions */

2015-04-05T16:44:29Z

Solutions

← Older revision		Revision as of 16:44, 5 April 2015
Line 56:		Line 56:
	# The 500 return status code for GET /getNotes means that the handler is generating some sort of error that is being caught by the Express framework. (That is why the error is being returned to the client rather than crashing the application.) One of the simplest kinds of errors that could generate this sort of problem is an unknown identifier. For example, if "username" was instead entered as "Username" (in the if (username) test) we could get a 500 error. Or, if the declaration of username was left out at the top of the function we would get a 500 error.		# The 500 return status code for GET /getNotes means that the handler is generating some sort of error that is being caught by the Express framework. (That is why the error is being returned to the client rather than crashing the application.) One of the simplest kinds of errors that could generate this sort of problem is an unknown identifier. For example, if "username" was instead entered as "Username" (in the if (username) test) we could get a 500 error. Or, if the declaration of username was left out at the top of the function we would get a 500 error.
	# The note being displayed is the one that is supposed to be sent when no user is logged in; however, the user is, indeed, logged in as evidenced by the working logout button. There is thus a logic error in the /getNotes callback. One way to generate this type of error would be to invert the if test of username (that is used to determine whether someone is logged in in the current session), e.g. by replacing "if (username)" with "if (!username)".		# The note being displayed is the one that is supposed to be sent when no user is logged in; however, the user is, indeed, logged in as evidenced by the working logout button. There is thus a logic error in the /getNotes callback. One way to generate this type of error would be to invert the if test of username (that is used to determine whether someone is logged in in the current session), e.g. by replacing "if (username)" with "if (!username)".
	#		# A new note is being added, so everything is working server side. The client (notes.js) is making the appropriate POST request because we see the note added. What we aren't seeing is the edit interface. The callback editNewNote() is responsible for initiating the call to editNote() which puts up the edit interface. Thus one way to generate the observed error would be to delete the call to editNote() in editNewNote().
	#		#
	#		#
	#		#

Soma: /* Solutions */

2015-04-05T16:30:17Z

Solutions

← Older revision		Revision as of 16:30, 5 April 2015
Line 55:		Line 55:
	# This error means that the handler function for / is not properly redirecting to /notes when the user is logged in. One code change that could produce this effect is the omission of the res.redirect("/notes") call in the function passed to router.get() for /.		# This error means that the handler function for / is not properly redirecting to /notes when the user is logged in. One code change that could produce this effect is the omission of the res.redirect("/notes") call in the function passed to router.get() for /.
	# The 500 return status code for GET /getNotes means that the handler is generating some sort of error that is being caught by the Express framework. (That is why the error is being returned to the client rather than crashing the application.) One of the simplest kinds of errors that could generate this sort of problem is an unknown identifier. For example, if "username" was instead entered as "Username" (in the if (username) test) we could get a 500 error. Or, if the declaration of username was left out at the top of the function we would get a 500 error.		# The 500 return status code for GET /getNotes means that the handler is generating some sort of error that is being caught by the Express framework. (That is why the error is being returned to the client rather than crashing the application.) One of the simplest kinds of errors that could generate this sort of problem is an unknown identifier. For example, if "username" was instead entered as "Username" (in the if (username) test) we could get a 500 error. Or, if the declaration of username was left out at the top of the function we would get a 500 error.
	#		# The note being displayed is the one that is supposed to be sent when no user is logged in; however, the user is, indeed, logged in as evidenced by the working logout button. There is thus a logic error in the /getNotes callback. One way to generate this type of error would be to invert the if test of username (that is used to determine whether someone is logged in in the current session), e.g. by replacing "if (username)" with "if (!username)".
	#		#
	#		#
	#		#
	#		#

Soma: /* Solutions */

2015-04-05T16:15:40Z

Solutions

← Older revision		Revision as of 16:15, 5 April 2015
Line 54:		Line 54:
	# This error happens because MongoDB is not running (e.g., it has crashed or somebody ran <tt>service mongodb stop</tt>). The application, via mc.connect(), attempts to connect to mongodb on localhost at port 27017 and gets a connection refused. This generates an error that is passed on to the anonymous callback for mc.connect(), which then calls "throw err". Because we don't have a catch statement to catch this error it causes the application to terminate with the error given above.		# This error happens because MongoDB is not running (e.g., it has crashed or somebody ran <tt>service mongodb stop</tt>). The application, via mc.connect(), attempts to connect to mongodb on localhost at port 27017 and gets a connection refused. This generates an error that is passed on to the anonymous callback for mc.connect(), which then calls "throw err". Because we don't have a catch statement to catch this error it causes the application to terminate with the error given above.
	# This error means that the handler function for / is not properly redirecting to /notes when the user is logged in. One code change that could produce this effect is the omission of the res.redirect("/notes") call in the function passed to router.get() for /.		# This error means that the handler function for / is not properly redirecting to /notes when the user is logged in. One code change that could produce this effect is the omission of the res.redirect("/notes") call in the function passed to router.get() for /.
	#		# The 500 return status code for GET /getNotes means that the handler is generating some sort of error that is being caught by the Express framework. (That is why the error is being returned to the client rather than crashing the application.) One of the simplest kinds of errors that could generate this sort of problem is an unknown identifier. For example, if "username" was instead entered as "Username" (in the if (username) test) we could get a 500 error. Or, if the declaration of username was left out at the top of the function we would get a 500 error.
	#		#
	#		#

Soma: /* Solutions */

2015-04-04T18:15:17Z

Solutions

← Older revision		Revision as of 18:15, 4 April 2015
Line 53:		Line 53:

	# This error happens because MongoDB is not running (e.g., it has crashed or somebody ran <tt>service mongodb stop</tt>). The application, via mc.connect(), attempts to connect to mongodb on localhost at port 27017 and gets a connection refused. This generates an error that is passed on to the anonymous callback for mc.connect(), which then calls "throw err". Because we don't have a catch statement to catch this error it causes the application to terminate with the error given above.		# This error happens because MongoDB is not running (e.g., it has crashed or somebody ran <tt>service mongodb stop</tt>). The application, via mc.connect(), attempts to connect to mongodb on localhost at port 27017 and gets a connection refused. This generates an error that is passed on to the anonymous callback for mc.connect(), which then calls "throw err". Because we don't have a catch statement to catch this error it causes the application to terminate with the error given above.
			# This error means that the handler function for / is not properly redirecting to /notes when the user is logged in. One code change that could produce this effect is the omission of the res.redirect("/notes") call in the function passed to router.get() for /.
	#		#
	#
	#		#
	#		#

Soma at 18:11, 4 April 2015

2015-04-04T18:11:50Z

← Older revision		Revision as of 18:11, 4 April 2015
Line 48:		Line 48:

	The "Refresh Notes" button doesn't seem to do anything. The rest of the application seems to work fine.		The "Refresh Notes" button doesn't seem to do anything. The rest of the application seems to work fine.


			==Solutions==

			# This error happens because MongoDB is not running (e.g., it has crashed or somebody ran <tt>service mongodb stop</tt>). The application, via mc.connect(), attempts to connect to mongodb on localhost at port 27017 and gets a connection refused. This generates an error that is passed on to the anonymous callback for mc.connect(), which then calls "throw err". Because we don't have a catch statement to catch this error it causes the application to terminate with the error given above.
			#
			#
			#
			#
			#
			#
			#