modules/gallery/views/admin_theme_options.html.php

<?php defined("SYSPATH") or die("No direct script access.") ?>
<div class="g-block">
  <h1> <?= t($title) ?> </h1>

  <div class="g-block-content">
  <?= $form ?>
  </div>
</div>
Make theme details its own page so that we can wrap it in a div and give it a title. 2009-02-26 02:38:32 +00:00			`<?php defined("SYSPATH") or die("No direct script access.") ?>`
Wrap all admin views in g-block and g-block content. This provides the means to visually separate the view's title and description from everything else. Primary admin view title should always be h1, and only one h1 per view. Removed some unused admin CSS id's. 2009-10-18 20:22:10 -06:00			`<div class="g-block">`
Currently Admin_Theme_Options controller assumes that all the themes will provide the same values. This change corrects that assumption and moves the management of the theme options, including creating the form and updating the theme options into the theme. 2009-11-18 14:37:49 -08:00			`<h1> <?= t($title) ?> </h1>`
Make theme details its own page so that we can wrap it in a div and give it a title. 2009-02-26 02:38:32 +00:00
Wrap all admin views in g-block and g-block content. This provides the means to visually separate the view's title and description from everything else. Primary admin view title should always be h1, and only one h1 per view. Removed some unused admin CSS id's. 2009-10-18 20:22:10 -06:00			`<div class="g-block-content">`
Make theme details its own page so that we can wrap it in a div and give it a title. 2009-02-26 02:38:32 +00:00			`<?= $form ?>`
Wrap all admin views in g-block and g-block content. This provides the means to visually separate the view's title and description from everything else. Primary admin view title should always be h1, and only one h1 per view. Removed some unused admin CSS id's. 2009-10-18 20:22:10 -06:00			`</div>`
Make theme details its own page so that we can wrap it in a div and give it a title. 2009-02-26 02:38:32 +00:00			`</div>`