Extensible Calendar - Revision history

Shane: Adding "Former Content" category tag

2014-08-25T08:08:51Z

Adding "Former Content" category tag

Shane at 07:39, 4 January 2014

2014-01-04T07:39:05Z

Shane: /* Tastypie */ Append Slash Fix

2013-11-05T06:35:02Z

Tastypie: Append Slash Fix

Shane: /* Extensible Config File */

2013-11-03T00:15:20Z

Extensible Config File

Shane: /* Tutorial for Debugging the Create Event Mechanism */ Adding screenshots

2013-11-02T09:53:46Z

Tutorial for Debugging the Create Event Mechanism: Adding screenshots

Shane: /* Help with Debugging */ Finishing debugging tutorial (still need to upload screenshots)

2013-11-02T09:46:53Z

Help with Debugging: Finishing debugging tutorial (still need to upload screenshots)

Shane: /* Help with Debugging */ Adding more steps to debugging tutorial

2013-11-02T09:23:37Z

Help with Debugging: Adding more steps to debugging tutorial

Shane: /* Tastypie */

2013-11-02T09:09:08Z

Tastypie

Shane: /* Tastypie */

2013-11-02T09:08:22Z

Tastypie

Shane: /* Help with Debugging */ First debugging example

2013-11-02T09:07:22Z

Help with Debugging: First debugging example

← Older revision		Revision as of 08:08, 25 August 2014
Line 448:		Line 448:

	[[Category:Module 6]]		[[Category:Module 6]]
		+	[[Category:Former Content]]

← Older revision		Revision as of 07:39, 4 January 2014
Line 1:		Line 1:
−	This page documents ~~an example of~~ using the [http://ext.ensible.com/products/calendar/ Extensible Calendar Pro API] with Django as the back end.	+	This page documents a tutorial for using the [http://ext.ensible.com/products/calendar/ Extensible Calendar Pro API] with Django as the back end.

	== REST ==		== REST ==

@@ Line 145: / Line 145: @@
 <source lang="python">
-APPEND_SLASH=False
+APPEND_SLASH=True
 </source>

@@ Line 216: / Line 216: @@
 Copy the file at ''cal/static/vendor/extensible/Extensible-config.js'' into the ''cal/static/cal'' directory.  Make the following changes:
-# Change the Ext JS version on line 59 from '''4.2.0''' to '''4.1.3'''
+# Change the Ext JS version on line 59 from '''4.2.0''' to '''4.1.1'''
 # Comment out the line that includes the ''examples.js'' file (around line 179)

@@ Line 338: / Line 338: @@
 Let's first take a look at what happens when you try to add a new event via the Extensible GUI.  When you click somewhere on the calendar, a little dialog opens, and in it you can specify the details of your event.  However, when you press "Save", you see the following error in the console:
-<<image here>>
+[[File:Extensible-Debugging-Unauthorized.png]]
 Whoopsy daisy, we got a '''401 Unauthorized''' from the server!  This means that Django-Tastypie thinks that we don't have enough permissions to edit this resource.  We need to tell Tastypie that we do indeed have such permissions.
@@ Line 358: / Line 358: @@
 Let's head on over to the "Network" panel of the web inspector.  Scroll to the bottom of the page to find the latest network request.  Click it, and then choose the "Response" tab.  You'll see something like this:
-<<image here>>
+[[File:Extensible-Debugging-Response-Error.png]]
 Hey, look!  There's an error that we can fix.  Let's look at it in more detail.
@@ Line 368: / Line 368: @@
 It sounds like Tastypie doesn't like whatever we're sending as the ''cid'' field.  Let's go check on what we're actually sending.  To do this, click on the "Headers" tab in the web inspector, and scroll down to "Request Payload".
-<<image here>>
+[[File:Extensible-Debugging-Request-Payload.png]]
 So we're clearly sending an integer calendar ID in the ''cid'' field.  Why wouldn't Tastypie like this?  I don't know; let's google the error!
@@ Line 374: / Line 374: @@
 Note that when we google something, we need to take specific field names out of our search.  In our case, this is the "cid" field name as well as the value of "1".  With that in mind, here are the hits:
-<<image here>>
+[[File:Extensible-Debugging-Google-Hits.png]]
 Look at that!  We're clearly not the first people to run into this error.
@@ Line 382: / Line 382: @@
 Hey, you find something that might provide you a clue!
-<<image here>>
+[[File:Extensible-Debugging-StackOverflow-Answer.png]]
 So we need to make our data field resemble one of those two options: either a dictionary with a "pk" field or a resource URL.

@@ Line 333: / Line 333: @@
 Wrapping your head around Extensible, Django-Tastypie, and how to make the two frameworks talk to each other is a daunting task.  The goal of this section is to help you learn how to debug this process.
 Let's first take a look at what happens when you try to add a new event via the Extensible GUI.  When you click somewhere on the calendar, a little dialog opens, and in it you can specify the details of your event.  However, when you press "Save", you see the following error in the console:
@@ Line 386: / Line 388: @@
 But how can we change the data format?  We could do it from the Extensible side, or we could do it from the Tastypie side.  Since we have greater control over Tastypie than Extensible, let's do it on the Tastypie side.
-[http://django-tastypie.readthedocs.org/en/latest/resources.html The Resources guide for Tastypie] seems like a reasonable place to start.
+[http://django-tastypie.readthedocs.org/en/latest/resources.html The Resources guide for Tastypie] seems like a reasonable place to start.  Read it and try to find the method that enables you to modify incoming data before Tastypie puts it into the model.
 [[Category:Module 6]]

@@ Line 127: / Line 127: @@
 		queryset = Event.objects.all()
 		paginator_class = Paginator
 	def dehydrate_cid(self, bundle):
 		return bundle.obj.cal.id

@@ Line 115: / Line 115: @@
 from tastypie.paginator import Paginator
 from cal.models import Cal, Event
-from tastypie.fields import IntegerField
+from tastypie.fields import ToOneField
 class CalResource(ModelResource):
@@ Line 123: / Line 123: @@
 class EventResource(ModelResource):
-	cal_id = IntegerField(attribute="cal__id") # load the calendar ID as an integer
+	cid = ToOneField(CalResource, "cal", full=True)
 	class Meta:
 		queryset = Event.objects.all()
 		paginator_class = Paginator
 </source>

@@ Line 329: / Line 329: @@
 == Help with Debugging ==
-Wrapping your head around Extensible, Django+Tastypie, and how to make the two frameworks talk to each other is a daunting task.  The goal of this section is to help you learn how to debug this process.
+Wrapping your head around Extensible, Django-Tastypie, and how to make the two frameworks talk to each other is a daunting task.  The goal of this section is to help you learn how to debug this process.
-In Extensible-config.js (inside ''cal/static/vendor/extensible''), change the Ext.JS version on line 59 from '''4.2.0''' to '''4.1.1'''.
+Let's first take a look at what happens when you try to add a new event via the Extensible GUI.  When you click somewhere on the calendar, a little dialog opens, and in it you can specify the details of your event.  However, when you press "Save", you see the following error in the console:
-Look at this page in the Tastypie documentation for a lot of great information: http://django-tastypie.readthedocs.org/en/latest/resources.html
+<<image here>>
-More tips coming soon.
+Whoopsy daisy, we got a '''401 Unauthorized''' from the server!  This means that Django-Tastypie thinks that we don't have enough permissions to edit this resource.  We need to tell Tastypie that we do indeed have such permissions.
 [[Category:Module 6]]