modules/notification/views/item_added.html.php

<?php defined("SYSPATH") or die("No direct script access.") ?>
<html>
  <head>
    <title><?= p::clean($subject) ?> </title>
  </head>
  <body>
    <h2><?= p::clean($subject) ?></h2>
    <table>
      <tr>
        <td><?= t("Title:") ?></td>
        <td><?= p::clean($item->title) ?></td>
      </tr>
      <tr>
        <td><?= t("Url:") ?></td>
        <td>
          <a href="<?= $item->url(array(), true) ?>">
            <?= $item->url(array(), true) ?>
          </a>
        </td>
      </tr>
      <? if ($item->description): ?>
      <tr>
        <td><?= t("Description:") ?></td>
        <td><?= p::clean($item->description) ?></td>
      </tr>
      <? endif ?>
    </table>
  </body>
</html>
As we stagger towards completing the notification module. Item changes and Item additions email notifications with this change. Still to come is item deleted, comment added and comment updated. 2009-02-02 03:09:17 +00:00			`<?php defined("SYSPATH") or die("No direct script access.") ?>`
			`<html>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`<head>`
Run p::clean() on any variables that contain data entered by users. 2009-05-31 00:11:48 -07:00			`<title><?= p::clean($subject) ?> </title>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`</head>`
			`<body>`
Run p::clean() on any variables that contain data entered by users. 2009-05-31 00:11:48 -07:00			`<h2><?= p::clean($subject) ?></h2>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`<table>`
			`<tr>`
			`<td><?= t("Title:") ?></td>`
Run p::clean() on any variables that contain data entered by users. 2009-05-31 00:11:48 -07:00			`<td><?= p::clean($item->title) ?></td>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`</tr>`
			`<tr>`
			`<td><?= t("Url:") ?></td>`
Run p::clean() on any variables that contain data entered by users. 2009-05-31 00:11:48 -07:00			`<td>`
			`<a href="<?= $item->url(array(), true) ?>">`
			`<?= $item->url(array(), true) ?>`
			`</a>`
			`</td>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`</tr>`
			`<? if ($item->description): ?>`
			`<tr>`
			`<td><?= t("Description:") ?></td>`
Run p::clean() on any variables that contain data entered by users. 2009-05-31 00:11:48 -07:00			`<td><?= p::clean($item->description) ?></td>`
A variety of cleanups: * Allow for the "movie" type in all of our text * Try to follow the pattern of mainly only passing ORM objects to the view and let it generate its own text (this becomes even more important when 3rd parties want to customize notification messages) * Rename _send_message to be _notify_subscribers to be more acccurate and have it explicitly take a subject in the API * Use Item_Model::url() in the views instead of hand crafting URLs * Reformat HTML in views * Use $comment->author_xxx() functions instead of replicating that code * Fix several places where we were encoding data by doing ucfirst($item->type) with conditionals where we form the text properly. We should never be showing data types to the end user! This is not localizable! Note that this probably breaks the existing batch processing code. I am going to redo that in a subsequent pass. 2009-03-04 06:25:55 +00:00			`</tr>`
			`<? endif ?>`
			`</table>`
			`</body>`
As we stagger towards completing the notification module. Item changes and Item additions email notifications with this change. Still to come is item deleted, comment added and comment updated. 2009-02-02 03:09:17 +00:00			`</html>`