The text I am referring to is the one that appears as a title on all the
change list pages; I cannot, however, find it in the change_list template.
But if you have not needed to change that, then you would not be able to
help.
(PS I was not asking to see the result of your changes, but where
Well, yes. The magic pony is doing everything for you, if you just treat it
correctly!
Basically, put the modified admin templates and static files exactly there
were you are serving your own templates and static assets normally in you
project directory.
For instance, treat the admin as an app
Derek,
You can see the custom changes I made here:
http://www.madtrak.com/admin
That is the extent of what I have done in relation to the default. Nothing
more then some colors in the CSS and text color. Additionally I changed the
actual wording for the to Log in | MadTrak Django
Admin oth
Pretty sure you're in the wrong thread bud.
On Sunday, September 16, 2012 2:52:34 AM UTC-4, Gutso wrote:
>
> Hi Everyone,
>
> I have one query:
>
> Should we change the database(mySQL) table's engine through migration
> scripts or not? If not then why?
>
> Following were my proposal:
>
> def for
Hevok so what are the steps for doing this?
Sure I know where the admin files are located but once I have copied them
does magic just happen and Django uses my new configurations?
Thanks,
JJ
PS. apparently after I left my website alone for a little the CSS
propagated through and now I see thi
Hi JJ
I'd like to know how you changed the wording... I cannot seem to find the
source text, for example, for "Select ... to change"
and would appreciate seeing/knowing how you did it.
There are examples on various blogs, but Django has changed how it is works
since they were written.
Thanks
D
Its the correct way to copy the templates and static files into your
project folder, if you want to customize them. Otherwise the changes
would disappear as soon as you deploy or setup-up your project on a
different computer/virtual environment.
Try F5, CTRL-F5 or CTRL-R to reload CSS in the brows
Hi Everyone,
I have one query:
Should we change the database(mySQL) table's engine through migration
scripts or not? If not then why?
Following were my proposal:
def forwards(self, orm):
# Change engine from MYISAM to INNODB
db.execute('alter table abc ENGINE=INNODB;')
def
There's a few things to put together -
urls.py needs something like (add a line before the normal admin
line):
(r'^admin/your_report/csv/$',
'yourproject.admin_views.report.csv_report'),
(r'^admin/', include('django.contrib.admin.urls')),
Then in your admin_views/report.py (or whatever you
9 matches
Mail list logo
