1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
<?php
/**
* @mainpage OJS API Reference
*
* Welcome to the OJS API Reference. This resource contains documentation
* generated automatically from the OJS source code.
*
* The design of Open %Journal Systems 2.x is heavily structured for maintainability,
* flexibility and robustness. For this reason it may seem complex when first
* approached. Those familiar with Sun's Enterprise Java Beans technology or the
* Model-View-Controller (MVC) pattern will note many similarities.
*
* As in a MVC structure, data storage and representation, user interface
* presentation, and control are separated into different layers. The major
* categories, roughly ordered from "front-end" to "back-end," follow:
* - Smarty templates, which are responsible for assembling HTML pages to
* display to users;
* - Page classes, which receive requests from users' web browsers, delegate any
* required processing to various other classes, and call up the appropriate
* Smarty template to generate a response;
* - Action classes, which are used by the Page classes to perform non-trivial
* processing of user requests;
* - Model classes, which implement PHP objects representing the system's
* various entities, such as Users, Articles, and Journals;
* - Data Access Objects (DAOs), which generally provide (amongst others)
* update, create, and delete functions for their associated Model classes, are
* responsible for all database interaction;
* - Support classes, which provide core functionalities, miscellaneous common
*
* As the system makes use of inheritance and has consistent class naming
* conventionsl it is generally easy to tell what category a particular class falls into.
* For example, a Data Access Object class always inherits from the DAO class, has a
* Class name of the form [Something]%DAO, and has a filename of the form
* [Something]%DAO.inc.php.
*
* To learn more about developing OJS, there are several additional resources that may be useful:
* - The docs/README document
* - The PKP support forum at http://pkp.sfu.ca/support/forum
* - The technical reference (and other documents), available at http://pkp.sfu.ca/ojs_documentation
*
* @file index.php
*
* Copyright (c) 2003-2009 John Willinsky
* Distributed under the GNU GPL v2. For full terms see the file docs/COPYING.
*
* @ingroup index
*
* Front controller for OJS site. Loads required files and dispatches requests to the appropriate handler.
*/
// $Id$
/**
* Handle a new request.
*/
function handleRequest() {
if (!Config::getVar('general', 'installed') && pageRequiresInstall()) {
// Redirect to installer if application has not been installed
Request::redirect(null, 'install');
}
// Determine the handler for this request
$page = Request::getRequestedPage();
$op = Request::getRequestedOp();
$sourceFile = sprintf('pages/%s/index.php', $page);
// If a hook has been registered to handle this page, give it the
// opportunity to load required resources and set HANDLER_CLASS.
if (!HookRegistry::call('LoadHandler', array(&$page, &$op, &$sourceFile))) {
if (file_exists($sourceFile)) require($sourceFile);
else require('pages/index/index.php');
}
if (!defined('SESSION_DISABLE_INIT')) {
// Initialize session
$sessionManager = &SessionManager::getManager();
$session = &$sessionManager->getUserSession();
}
$methods = array_map('strtolower', get_class_methods(HANDLER_CLASS));
if (in_array(strtolower($op), $methods)) {
// Call a specific operation
call_user_func(array(HANDLER_CLASS, $op), Request::getRequestedArgs());
} else {
// Call the selected handler's index operation
call_user_func(array(HANDLER_CLASS, 'index'), Request::getRequestedArgs());
}
}
// Initialize system and handle the current request
require('includes/driver.inc.php');
initSystem();
handleRequest();
?>
|
