python - Changes to Django Context not showing in template -


i have template has variables printing context created in view. has been working couple of months.

i have added new variables context, won't show in template.

when run django project locally, if remove comma in between 2 of variables in context, error, expected. if add comma back, new variables in template. when push changes openshift, new variables never show up. in fact, if remove of existing variables, template still renders if there.

i have cleared cache in browser. didn't fix it. i'm not using caching in django (a search 'cache' in settings.py shows no hits).

clearly, caching somewhere, can't figure out where. since changes show in browser when running locally, i'm confident there aren't syntax errors in python code. here context listing:

        context = {          'slug': 'admin home .'         , 'players': len(players)         , 'paid': totalpaid         , 'unpaid': len(unpaid)         , 'monday': monday         , 'tuesday': tuesday         , 'wednesday': wednesday         , 'donations': donations         , 'ssmall': ssmall         , 'smedium': smedium         , 'slarge': slarge         , 'sxl': sxl         , 'sxxl': sxxl         , 'page': page     }

here example of 1 of variables not showing in template:

    large: {{slarge}}

and slarge variable has value. checked running of code in shell, , said above, shows on rendered page.

i changed page title in head section, , changes show well, whenever variable populates correctly on page.

from i've read, sounds apache and/or mod_wsgi openshift uses caching something(s), don't know how fix it. have restarted application within openshift, hasn't fixed it.

i appreciate help.

i should have mentioned, first django project.

i making of these changes in section of class rather post section, , should have been in post section.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more