Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

82 - ModelStore Caching/Not-Updating issue #80

Open
klipstein opened this issue Nov 6, 2011 · 0 comments
Open

82 - ModelStore Caching/Not-Updating issue #80

klipstein opened this issue Nov 6, 2011 · 0 comments

Comments

@klipstein
Copy link
Owner

Taken from a well discussed thread on google group:
http://groups.google.com/group/dojango-users/browse_thread/thread/8a8b14f1390f57b0/7595dff267806bcb?#7595dff267806bcb

What steps will reproduce the problem?
1.) pull data from a ModelStore into an ItemFileReadStore (works)
2.) dojo pulls a page name and URL from the JSON data (works)
3.) dojo then builds a list of links in html on the page (works well)
4.) dojo builds an ajax form on the page that posts back to the view
(works)
5.) the form call back posts a message and calls a rebuild of the list
(rebuild doesn't go as planned but call back works) 

What is the expected output? What do you see instead?
On this page, the dojo form is created in JS.  When submitted, it
creates a new entry in the model I used above.  When I use this form,
the post, processing and object.save(), and json call back work
great.

Once this form is submitted I would like to repopulate the name/URL
list on the page.

The problem I am having, is even though I can verify positive database
write, the ModelStore doesn't update its objects, so the JSON page
isn't updated and the list is not updated (its regenerated but with
the same data as last time) 

What version of the product are you using? On what operating system?
Dojango Version 0.4.7
Windows XP Service Pack 3
Django 1.2.1

Please provide any additional information below.
Last message from Ben on the thread was that he would be looking into a permanent solution on April 6, 2010.

Original link: http://code.google.com/p/dojango/issues/detail?id=82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant