| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
This was left in a messy state. I'm just cleaning it up a little bit
for now for the release.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Since there is currently no way to set heads for these objects, I am
replacing them with the appropriate glyphicon.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Previously, when the app was asked for non-existant paths, no content
was returned and a blank page was presented to the user. Now a canned
message stating that the requested page does not exist is shown, along
with a helpful link back to the Dashboard page.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Since this form submits a file upload, we need it to be set
enctype="multipart/form-data".
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Submissions to the iss-mesg-add form are now handled by this function.
User must be logged in and permitted to post to the issue in question.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
The SQL query here, as written, was omitting 'log' type messages from
the results.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Listing all message (and log messages) beneath the OP in chrono order.
There is a form at the bottom to submit new messages.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Some form handlers use the current logged in user (user::getCurrent()),
however do so without asserting that we are _actually_ logged in. This
is probably due to that fact that index.php (usually) catches all page
requests that are logged out and diverts control before any other handler
can be invoked. But a few handlers sneak through the cracks.
In the future, the app will be better about supportting logged out
browsing, the alpha was not written with this in the forground.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
POSTs to the dm-issue-add form are handled by this new handler. Pad
data is passed via the form, we create the new issue in the pad's first
stage, crediting the current logged in user. New issue is unassigned.
I call `location()` at the bottom, since not doing so leaves the page in
a weird state. The reason being that most of the page rendering logic
operates off of the 'pageObj', which is instanciated and assigned prior
to the invocation of this handler. This is to be fleshed-out during the
v0.2-v0.3 development iteration.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
First button added to the header of pad views is to open new issues.
This interface is still very crude and subject to change in the near
future.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
When viewing a pad, offer the 'New Issue' option under the additions
menu in the navbar. Will will display the just-added new issue modal,
for the user to open a new issue on the first stage of the pad being
viewed.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
This datamods modal is accessable from pad views to open a new issue on
the pad in question. This is a simplistic version of this interface,
subject to improvements once I start on the v0.2-v0.3 development
iteration. Suffice it to say, any frills we will want to use in the
initial draft will be accessible from the issue view modal, as options
to modify the open issue.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Adds a parameterized text area to the collection of controls.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
Updated the javascript to wire-up the issue list items shown on pad
views. When these are clicked the associated issue modal is displayed
in the foreground.
|
|
This logic instanciates an issue modal view for each issue to be
accessable from a pad view.
|
|
|
|
This reverts commit 62872702dc413b7abab94d8a5a7bd21770b5d241.
|
|
|
|
Revised implementation of redesigned data model.
|
|
This function is patched to co-operate with structural changes to the
issue class.
|
|
|
|
|
|
|
|
|
|
|
|
A dependency loop exists between class/agent.class.php and
class/group.class.php. Due to specific `require_once` ordering within
the app, this problem was not surfaced until now.
These two classes depend on eachother, but strictly speaking, the
interpreter needs to read the agent class first. This is because group
directly inherits from agent. It is only one of agent's functions which
references group. Group has a `require_once "class/agent.class.php"` at
its top, so requiring group first will read both classes, in the correct
order, and provide their definition's for the remainder of the runtime.
The main entry-point, index.php, did not have this problem since it was
explicitly requiring group itself (it actually needs group, though).
The df.php entry-point wasn't and was relying on requires in the class/
directory to resolve this issue. In a more-sane language, I could patch
this more easily directly in the affected file; rather, this patch
updates the df entry-point to explicitly require group, solving the
issue up front.
Hopefully this can be fleshed out in the future as it should not consern
the entry-points that this specific evaluation order needs to take
place.
The third and final entry-point, cron.php, is already fine at the time
of this commit. Its require tree is much simplier, and does not even
include either of the affected classes.
|
|
|
|
This is probabally more of an oops than a bug, although was causing
unexpected behavior.
When falling back to checking whether the agent has access to the
object's owner, it was wrongly accessing through $this->owner, rather
than $obj->owner (which is the function argument). This was probabally
left over from how this function _used_ to be implemented (you would
call on the object and pass in the user).
|
|
|
|
|
|
|
|
There was a problem with processing enum type fields. The way all other
field types are asserted to be 'defined' is via:
isset($field) && $field != ""
Which works perfectly fine, and is exactly what we want. However, with
enums the second part of that && can bite us if "" is in the list of
acceptable values.
This commit removed that half of the check (only for enum values) so
that the empty string may be an acceptable enum value. If "" is not in
the values array, then the check is implicitly reinstated.
|
|
|
|
Because of how this function was implemented, any failure during
database instance construction is treated the same way. IE. we cannot
tell the difference between 'no db config' (as is the initial default
state) and a 'bad db config' (either bogus data, or the server happens
to be down).
Because of this, if, after the database access is initially set up,
access to the db becomes unavailable or someone makes a bad edit to the
dbconfig.php file, Scrott behaves as if it is being configured for the
first time. This is *dangerous* behavior! (unexpected, at the least)
The implication of this is that if Scrott's database access is ever
incidentially interrupted, the very next visitor to the site is offered
the chance to (silently) reconfigure the server to point to any database
of his choosing.
This patch updates the checkConfig() function to only 'soft fail'
(return false) in the case where the configuration is _actually_
missing. IE. $_SCROTT['conf'] is not defined. This function will
otherwise passthrough any and all exceptions which result from
instanciating the database instance and will only return true if both of
these steps succeed.
|
|
This is an interface to alter the settings stored in the 'settings'
database table. Typically restricted to administrators only.
|
|
This is not meant to be a user (admin) configurable key. Rather, this
is a mechanism for success/failure results from interactions with
PHPMailer to make their way back to the UI. Down the road, email
sending functions should publish their true/false return value to this
configuration key. The initial default value of "NULL" means no mail
send attempts have taken place.
|
|
|
|
|
|
|
|
The controller now (again) prevents browsing to objects the user is not
allowed to access.
|
|
|
|
In cases where the pad had no stages beneath it, `new
stage($this->stage)` would construct an invalid object. As it turns
out, calling ->getArray() on an uninitialized stage object yeilds bad
results.
Instead of patching the stage::getArray() function, I add a check to
harden pad::getStages(). My reasoning for this is as follows: The bug
in getArray() manifests from a domain error, ie. it's only because we
are calling it on an uninitialized object. The object is already in a
bad state prior to caling getArray(). Rather, I opt to patch
getStages() so that we never create a bad object in the first place.
Now, for no-stage pads, getStages() will return early an empty array.
|
|
This particular flaw was dampening (and could popentially be hiding) the
effects of other bugs.
For instance, in this case, a GUID of "" was invalidly being used to
construct an object. This should obviously be considered an error, but
since "" evaluates to false, the construction was treated as default (no
GUID) construction and succedded. It wasn't until later when missing
properties were accessed that random PHP error messages clued me into what
was happening.
Now, when any sort of explicit value is used to construct an object (not
NULL), an object load will be attempted, giving bad input more chances
to fail outright and trigger an exception. In addition, the 'no such
guid' exception message is updated to place quotes ('') around the GUID
string to make it more obvious when "" is used in the future.
|
|
Removed placholder text and now displaying the logged-in user's display
name. This is accopanied by the user icon and (conditionally) the
'cool' sunglasses icon for admins. This is similar, but not identical,
to the markup of my old archived code I'm clearing out.
|
