django cms 3.3.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.4. If you refresh a page you should to version 3.1 this module was named cms_app.py - please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.4. The file needs to contain a0 码力 | 386 页 | 1.56 MB | 1 年前3- django cms 3.4.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 395 页 | 1.64 MB | 1 年前3
django cms 3.6.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 278 页 | 1.63 MB | 1 年前3- django cms 3.5.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 403 页 | 1.69 MB | 1 年前3
- django cms 3.7.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 409 页 | 1.67 MB | 1 年前3
- Django CMS 3.9.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 417 页 | 1.68 MB | 6 月前3
- Django CMS 3.8.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 413 页 | 1.67 MB | 6 月前3
- Django CMS 4.0.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need to Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 296 页 | 1.79 MB | 6 月前3
- Django CMS 3.9.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need to Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 298 页 | 1.79 MB | 6 月前3
- django cms 3.10.x DocumentationCMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased0 码力 | 296 页 | 1.79 MB | 1 年前3
共 345 条
- 1
- 2
- 3
- 4
- 5
- 6
- 35