Django CMS 3.11.10 DocumentationAfter all scripts have been loaded and executed, the document’s DOMContentLoaded, the window’s load events are triggered. The cms-content-refresh jQuery event on the window is also triggered for backwards refresh. This is why after a content refresh in edit mode, the document.DOMContentLoaded, window.load events and – for backward compatibility – the cms-content-refresh jQuery event are triggered. We encourage event for your plugin’s javascript code that needs to be run after a content refresh. Since this events is triggered both on initial load and on updates (of potentially different plugins), you should make0 码力 | 493 页 | 1.44 MB | 6 月前0.03
Django Q Documentation
Release 0.5.3the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. Management Commands0 码力 | 46 页 | 474.97 KB | 1 年前3
Django Q Documentation
Release 0.5.3the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. 1.4.3 Management0 码力 | 38 页 | 358.27 KB | 1 年前3
Django Q Documentation
Release 0.6.4the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. Management Commands0 码力 | 53 页 | 512.86 KB | 1 年前3
Django Q Documentation
Release 0.6.4the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. 1.5.3 Management0 码力 | 42 页 | 376.79 KB | 1 年前3
Django Q Documentation
Release 0.7.9the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. Management Commands0 码力 | 62 页 | 514.67 KB | 1 年前3
Django Q Documentation
Release 0.7.9the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. 1.5.3 Management0 码力 | 50 页 | 397.77 KB | 1 年前3
Django Q Documentation
Release 0.7.13the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run once when the cluster starts again and the scheduler will0 码力 | 56 页 | 416.37 KB | 1 年前3
Django Q Documentation
Release 0.7.11the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. 1.8.3 Management0 码力 | 54 页 | 412.45 KB | 1 年前3
Django Q Documentation
Release 0.7.10the catch_up configuration setting to False. The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes. Management Commands0 码力 | 67 页 | 518.39 KB | 1 年前3
共 78 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8













