6 replies to this topic

[apeisa]

It would be great if there would be an easy way to add flash-type of session variables. Here is citation from codeigniter docs:

Quote

CodeIgniter supports "flashdata", or session data that will only be available for the next server request, and are then automatically cleared. These can be very useful, and are typically used for informational or status messages (for example: "record 2 deleted").

[apeisa]

Ahh... now I get it. There is $notices variable. Very nice.

If others are thinking how to use it, just take a look at notices.inc from templates-admin folder. You can access the very same $notices from your template code. And setting these notices is super simple:

$session->error("Houston, we have a problem");
$session->message("Hello world!");

[adamkiss]

So it's solved?

[apeisa]

Yep. Although mention about these on session docs and on cheatsheet would be nice.

[Soma]

I don't really get it. Notice class has something to do with flash session data?

[apeisa]

You do this on template:
$session->error("error error");

or this on class:
$this->session->error("error error");

End then on next page load you can have this:

foreach($notices as $notice) {
if($notice instanceof NoticeError) {
  echo "<p>$notice->text</p>";
}
}

And that error notice is gone, no need to clear it yourself.

[ryan]

I never knew the name for it. It's good to hear that, "flashdata". This was mainly setup so that modules could queue messages that would only be seen on a follow-up page. Since many modules do a session->redirect() after a save, there needed to be a way to queue those messages to be seen on the following page load rather than the current (where they would never be seen). I don't think that you actually have to call $session->message(), as I think any notice sent through message() or error() gets queued. Though calling $session->message() is a good way to make that intention clear from the code side.