Geodesic Solutions Community Wiki

User Tools

Site Tools

You are here: Auction and Classified Software Support Home » Developers » Addons » Core Events
developers:addons:core_events

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
developers:addons:core_events [2011/07/08 05:19]
jonyo [Core Event Types based on Return Value] use NO_OVERLOAD 		developers:addons:core_events [2014/09/25 16:55] (current)
Line 83: Line 83:
 These core events are to deal with the user session or session data.  In all events so far, it is done in addition to, not instead of, the built in stuff.  It works kind of like a filter, except that the return values are ignored.  It is passed the session info, and that is it.  Events will be prepended with **session_**. These core events are to deal with the user session or session data.  In all events so far, it is done in addition to, not instead of, the built in stuff.  It works kind of like a filter, except that the return values are ignored.  It is passed the session info, and that is it.  Events will be prepended with **session_**.
  
-These are what the Bridge addon uses to do it's thing for syncing up login/logout with other installations.+These are what the Bridge addon uses to do its thing for syncing up login/logout with other installations.
  
 ==== user ==== ==== user ====
Line 93: Line 93:
 ==== errorhandle ==== ==== errorhandle ====
  
-This is a special case, this is the name of a core event that is it's own category.  It is triggered every time an error is triggered in the system (even notifications).+This is a special case, this is the name of a core event that is its own category.  It is triggered every time an error is triggered in the system (even notifications).
  
 In the software, we use trigger_error() as a debugging message tool, the message syntax will match: In the software, we use trigger_error() as a debugging message tool, the message syntax will match:
Line 105: Line 105:
 ==== app_bottom ==== ==== app_bottom ====
  
-This is another core event that is it's own category.  "Bottom" in this case, refers to the end of the page load, where the script is wrapping things up, not the physical location somewhere on a page.  This core event is used to allow you to do things right before the page is done, but after the page is already displayed.  In other words: It's closing time, you don't have to go home but you can't stay here.+This is another core event that is its own category.  "Bottom" in this case, refers to the end of the page load, where the script is wrapping things up, not the physical location somewhere on a page.  This core event is used to allow you to do things right before the page is done, but after the page is already displayed.  In other words: It's closing time, you don't have to go home but you can't stay here.
  
developers/addons/core_events.1310102364.txt.gz · Last modified: 2014/09/25 16:55 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki