Haven't actually communicated our decision but I'll just see if they are willing to fund the development involved in staying on an out-of-date and soon-to-be-unsupported system we'll hire someone to do that.

I think.

Haven't done any research on best practice in this area. Happy to let you know what happens ;)

Cheers

Mike

On 31/05/2017 10:56 AM, 'Abraham Varricatt' via Django users wrote:
How ... did you impose our will on this user? ;) I'd like to hear more ... for peaceful research purposes, of course.

-Abraham V.


On Monday, May 29, 2017 at 9:19:01 PM UTC-4, Mike Dewhirst wrote:

    Cancel this question. We will force the user to comply with our
    reality.

    Cheers

    Mike

    On 16/05/2017 5:42 PM, Mike Dewhirst wrote:
    > I have a user who is keen to revert to the "old" 1.8 look and
    feel for
    > his company now that we have upgraded to 1.10.
    >
    > First question is it even possible?
    >
    > I have tested this using blunt force and at first glance it *seems*
    > possible in both directions. However I have a suspicion there
    might be
    > tie-ins I have not discovered. Also. I haven't yet tried 1.11.
    >
    > If it is feasible ...
    >
    > Second question is how to do it.
    >
    > I have stared long and hard at settings. I have this ...
    >
    > STATICFILES_DIRS = [
    >     os.path.join(BASE_DIR, 'static/').replace('\\', '/'),
    >     os.path.join(BASE_DIR, 'company/static/').replace('\\', '/'),
    >     os.path.join(BASE_DIR, 'substance/static/').replace('\\', '/'),
    >     os.path.join(BASE_DIR, 'workplace/static/').replace('\\', '/'),
    > ]
    >
    > and
    >
    > STATICFILES_FINDERS = [
    >     'django.contrib.staticfiles.finders.FileSystemFinder',
    >     'django.contrib.staticfiles.finders.AppDirectoriesFinder',
    > ]
    >
    > and I can get the user (company) from the request and I can
    create a
    > company subdir under 'company/static/<company>/' if that's where I
    > should be putting the admin files from 1.8. But then how do I tweak
    > the settings so the Admin uses the preferred company static
    files for
    > just that user?
    >
    > Maybe instead, there is a company specific preference I can
    establish
    > to provide '/static/admin_1.8' for that user?
    >
    > Maybe I need to have company-specific Admin templates which
    override
    > the block which reads the static files based on a company
    preference?
    >
    > Any hints?
    >
    > Thanks
    >
    > Mike
    >

--
You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com <mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com <mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a1d84a3a-049b-4ba4-9641-579dab3e5f53%40googlegroups.com <https://groups.google.com/d/msgid/django-users/a1d84a3a-049b-4ba4-9641-579dab3e5f53%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cc057d21-a868-5963-951d-5e44e64baf16%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Reply via email to