modules/gallery/views/admin_graphics_none.html.php

<?php defined("SYSPATH") or die("No direct script access.") ?>

<div id="none" class="g-module-status g-warning g-block">
  <h3> <?= t("No active toolkit") ?> </h3>
  <p>
    <?= t("We were unable to detect a graphics program.  You must install one of the toolkits below in order to use many Gallery features.") ?>
  </p>
</div>
Don't do graphics detection in core_installer::install() because that gets run at scaffolding::package() time, not on the target machine. Instead, create a core module variable to trigger running graphics::choose_default_toolkit() on the first admin login after install. Fixes ticket #206. 2009-04-05 20:43:05 +00:00			`<?php defined("SYSPATH") or die("No direct script access.") ?>`
Update status message styles. Lighten backgrounds, don't show background on Admin Maintenance rows, and added gModuleStatus class. 2009-08-29 14:01:04 -06:00
Renamed most, if not all css selectors from gName to g-name. Moved a few shared images from wind to lib. Deleted unused images in the admin_wind. This will likely break a few ajax features. 2009-10-04 00:27:22 -06:00			`<div id="none" class="g-module-status g-warning g-block">`
Normalize capitalization ticket #596 2009-10-28 12:15:52 -07:00			`<h3> <?= t("No active toolkit") ?> </h3>`
Don't do graphics detection in core_installer::install() because that gets run at scaffolding::package() time, not on the target machine. Instead, create a core module variable to trigger running graphics::choose_default_toolkit() on the first admin login after install. Fixes ticket #206. 2009-04-05 20:43:05 +00:00			`<p>`
Improve the graphics toolkit detection code so that properly identifies situations where its restricted by open_basedir. We now track more informatoin about the toolkit including the version and any errors we encountered while doing the detection so that we can provide more info downstream. This makes graphics::detect_toolkits() a little heavier, but that's ok because it should not be called very often. In the process, refactor the controller and view hierarchy so that it's a little more straightforward in the code. Fixes ticket #616. 2009-08-08 20:31:16 -07:00			`<?= t("We were unable to detect a graphics program. You must install one of the toolkits below in order to use many Gallery features.") ?>`
Don't do graphics detection in core_installer::install() because that gets run at scaffolding::package() time, not on the target machine. Instead, create a core module variable to trigger running graphics::choose_default_toolkit() on the first admin login after install. Fixes ticket #206. 2009-04-05 20:43:05 +00:00			`</p>`
			`</div>`