7 f+ddlZddlZddlmZddlmZddlmZmZddl m Z ddl m Z ddl mZddlmZGdd eZd Zed Zed Zd ZedZedZy)N) AppConfig)settings)Warningregister)GZipMiddleware) import_string) gettext_lazyc&eZdZdZedZdZy)DebugToolbarConfig debug_toolbarz Debug ToolbarcZddlm}|jD]}|jy)Nr DebugToolbar)debug_toolbar.toolbarrget_panel_classesready)selfrclss H/var/www/equiseq/venv/lib/python3.11/site-packages/debug_toolbar/apps.pyrzDebugToolbarConfig.readys(6 113 C IIK N)__name__ __module__ __qualname__name_ verbose_namerrrr r s D_%Lrr cfd|jdd}|jdijdd}|rt|}|duxsd|v}|xs|S)a Checks if a template configuration is valid. The toolbar requires either the toolbars to be unspecified or ``django.template.loaders.app_directories.Loader`` to be included in the loaders. If custom loaders are specified, then APP_DIRS must be True. c3~K|D]1}t|tr|d|dEd{.|3y7 w)z Recursively flatten the settings list of template loaders. Check for (loader, [child_loaders]) tuples. Django's default cached loader uses this pattern. rN) isinstancetuple)loadersloader flat_loaderss rr%z+check_template_config..flat_loaders%sG F&%(Qi'q 222  3s +=; =APP_DIRSFOPTIONSr#Nz.django.template.loaders.app_directories.Loader)getlist)configapp_dirsr#has_app_loadersr%s @rcheck_template_configr-so zz*e,HjjB'++Itz#check_middleware..Gs N$V, , NszAt least one DjangoTemplates TEMPLATES configuration needs to use django.template.loaders.app_directories.Loader or have APP_DIRS set to True.zInclude django.template.loaders.app_directories.Loader in ["OPTIONS"]["loaders"]. Alternatively use APP_DIRS=True for at least one django.template.backends.django.DjangoTemplates backend configuration.zdebug_toolbar.W006hintidMIDDLEWARE_CLASSESz>debug_toolbar is incompatible with MIDDLEWARE_CLASSES setting.z,Use MIDDLEWARE instead of MIDDLEWARE_CLASSESzdebug_toolbar.W004zKdebug_toolbar.middleware.DebugToolbarMiddleware is missing from MIDDLEWARE.zBAdd debug_toolbar.middleware.DebugToolbarMiddleware to MIDDLEWARE.zdebug_toolbar.W001r zTdebug_toolbar.middleware.DebugToolbarMiddleware occurs multiple times in MIDDLEWARE.zMLoad debug_toolbar.middleware.DebugToolbarMiddleware only once in MIDDLEWARE.zdebug_toolbar.W002zrdebug_toolbar.middleware.DebugToolbarMiddleware occurs before django.middleware.gzip.GZipMiddleware in MIDDLEWARE.zrMove debug_toolbar.middleware.DebugToolbarMiddleware to after django.middleware.gzip.GZipMiddleware in MIDDLEWARE.zdebug_toolbar.W003) debug_toolbar.middlewarer/allr TEMPLATESappendr is_overridden enumerate MIDDLEWAREis_middleware_classrlen) app_configskwargsr/errors gzip_indexdebug_toolbar_indexesi middlewares rcheck_middlewarerH?sm? FJ N8;M;M NN -- (  "23 PC'   #8#6#67, : ~z :J !7 D ! ( ( + , ! #'   > M- " #q ( 0&'   ( M  $9!$ * z(0 s 0 <<c pg}tj}|s|jtddd|S)Nz&Setting DEBUG_TOOLBAR_PANELS is empty.zASet DEBUG_TOOLBAR_PANELS to a non-empty list in your settings.py.zdebug_toolbar.W005r4) dt_settings get_panelsr;r)rArBrCpanelss r check_panelsrZs> F  # # %F  8'    Mrc ddh}ttjdj| }|rt dddgSgS)zP Check that JavaScript files are resolving to the correct content type. zapplication/javascriptztext/javascriptz toolbar.jsz9JavaScript files are resolving to the wrong content type.aThe Django Debug Toolbar may not load properly while mimetypes are misconfigured. See the Django documentation for an explanation of why this occurs. https://docs.djangoproject.com/en/stable/ref/contrib/staticfiles/#static-file-development-view This typically occurs on Windows machines. The suggested solution is to modify HKEY_CLASSES_ROOT in the registry to specify the content type for JavaScript files. [HKEY_CLASSES_ROOT\.js] "Content Type"="application/javascript"zdebug_toolbar.W007r4)set mimetypes guess_type intersectionr)rArBjavascript_types check_faileds rjs_mimetype_checkrbsc12CD9// =>KKL K :(   Ir)rPr] django.appsr django.confrdjango.core.checksrrdjango.middleware.gziprdjango.utils.module_loadingrdjango.utils.translationr rr rWr r-rHrMr?rZrbrrrris! 01561  !'H K K\        r