controller/jobs/src/Controller/Jobs/Catalog/Export/Sitemap/Standard.php
protected function createContent( \Aimeos\MW\Container\Iface $container, $filenum )
	{
		/** controller/jobs/catalog/export/sitemap/standard/template-header
		 * Relative path to the XML site map header template of the catalog site map job controller.
		 *
		 * The template file contains the XML code and processing instructions
		 * to generate the site map header. The configuration string is the path
		 * to the template file relative to the templates directory (usually in
		 * controller/jobs/templates).
		 *
		 * You can overwrite the template file configuration in extensions and
		 * provide alternative templates. These alternative templates should be
		 * named like the default one but with the string "standard" replaced by
		 * an unique name. You may use the name of your project for this. If
		 * you've implemented an alternative client class as well, "standard"
		 * should be replaced by the name of the new class.
		 *
		 * @param string Relative path to the template creating XML code for the site map header
		 * @since 2019.02
		 * @category Developer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-items
		 * @see controller/jobs/catalog/export/sitemap/standard/template-footer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-index
		 */
		$tplconf = 'controller/jobs/catalog/export/sitemap/standard/template-header';
		$default = 'catalog/export/sitemap-items-header-standard';

		$context = $this->getContext();
		$view = $context->getView();

		$content = $container->create( $this->getFilename( $filenum ) );
		$content->add( $view->render( $context->getConfig()->get( $tplconf, $default ) ) );
		$container->add( $content );

		return $content;
	}
protected function createContent( \Aimeos\MW\Container\Iface $container, $filenum )
	{
		/** controller/jobs/catalog/export/sitemap/standard/template-header
		 * Relative path to the XML site map header template of the catalog site map job controller.
		 *
		 * The template file contains the XML code and processing instructions
		 * to generate the site map header. The configuration string is the path
		 * to the template file relative to the templates directory (usually in
		 * controller/jobs/templates).
		 *
		 * You can overwrite the template file configuration in extensions and
		 * provide alternative templates. These alternative templates should be
		 * named like the default one but with the string "standard" replaced by
		 * an unique name. You may use the name of your project for this. If
		 * you've implemented an alternative client class as well, "standard"
		 * should be replaced by the name of the new class.
		 *
		 * @param string Relative path to the template creating XML code for the site map header
		 * @since 2019.02
		 * @category Developer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-items
		 * @see controller/jobs/catalog/export/sitemap/standard/template-footer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-index
		 */
		$tplconf = 'controller/jobs/catalog/export/sitemap/standard/template-header';
		$default = 'catalog/export/sitemap-items-header-standard';

		$context = $this->getContext();
		$view = $context->getView();

		$content = $container->create( $this->getFilename( $filenum ) );
		$content->add( $view->render( $context->getConfig()->get( $tplconf, $default ) ) );
		$container->add( $content );

		return $content;
	}
protected function createContent ( \ Aimeos \ MW \ Container \ Iface $ container , $ filenum ) { /** controller/jobs/catalog/export/sitemap/standard/template-header
		 * Relative path to the XML site map header template of the catalog site map job controller.
		 *
		 * The template file contains the XML code and processing instructions
		 * to generate the site map header. The configuration string is the path
		 * to the template file relative to the templates directory (usually in
		 * controller/jobs/templates).
		 *
		 * You can overwrite the template file configuration in extensions and
		 * provide alternative templates. These alternative templates should be
		 * named like the default one but with the string "standard" replaced by
		 * an unique name. You may use the name of your project for this. If
		 * you've implemented an alternative client class as well, "standard"
		 * should be replaced by the name of the new class.
		 *
		 * @param string Relative path to the template creating XML code for the site map header
		 * @since 2019.02
		 * @category Developer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-items
		 * @see controller/jobs/catalog/export/sitemap/standard/template-footer
		 * @see controller/jobs/catalog/export/sitemap/standard/template-index
		 */ $ tplconf = 'controller/jobs/catalog/export/sitemap/standard/template-header' ; $ default = 'catalog/export/sitemap-items-header-standard' ; $ context = $ this -> getContext ( ) ; $ view = $ context -> getView ( ) ; $ content = $ container -> create ( $ this -> getFilename ( $ filenum ) ) ; $ content -> add ( $ view -> render ( $ context -> getConfig ( ) -> get ( $ tplconf , $ default ) ) ) ; $ container -> add ( $ content ) ; return $ content ; }
Creates a new site map content object

@param \Aimeos\MW\Container\Iface $container Container object
@param integer $filenum New file number
@return \Aimeos\MW\Container\Content\Iface New content object
Creates a new site map content object