• last updated 8 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Improved the queries for global/instance params ...

1. First shot at sitewide admin ui for global parameters. You can edit them

from the sitewide admin page list that was previously built for packages

that have a sitewide-admin subdirectory. Package is now displayed for

either the existence of sitewide-admin or global parameters.

2. Did something I'd wanted to do for some time. When Nima added the

parameter_changed callback in acs subsite, he actually *moved* the

set_value call there. I've changed it so it more rationally sets the

value in the parameters page, then calls the parameter_changed callback.

3. Invented a global_parameter_changed callback that works as the regular

parameter_changed callback. This was necessary to avoid breaking existing

uses of parameter_changed.

More testing is required before release (which will hopefully happen

tomorrow, Sunday Apr 4).

The instantiate callback would fail if search was mounted during initial

install (as in a custom install.xml file). It only indexes now if the

init file has been sourced, which will be after server restart if one is

doing an initial install.

Ugh ... finally got inherited parameters right.

Needed to build the subsites package keys cache ...

Added a new "rename-instance" node, useful in particular for renaming

"Main Site" to something more useful.

    • -3
    • +28
    /openacs-4/packages/acs-tcl/tcl/install-procs.tcl
Allow for the specification of "scope" when registering a parameter from

an install xml file.

part 2 of (temp) fix - added bit to sweeper that clears out invalid (unauthorized) notif requests

Finished up PG semantics for global/instance parameters on package upgrade.

The Tcl API stuff to do this should technically be moved down into the

oracle/PG API but 1) it's a fair amount of db-specific work and 2) people

should be using the high level constructs in the first place (and why do

people explicitly register new parameters when they're registered from the

package info file on upgrade in the first place?)

Making global/instance changes work with Oracle

More code dealing with instance and global parameter semantics. I finally

have a reasonable model of inheritance and semantics implemented, not

perfect from a language-theoretic point of view, but works well without

having to rewrite every bit of parameter-handling code in acs-core.

Add UI to create global parameters from within the APM package builder.

Display "scope" of parameters on the version parameters page.

Add missing query

Fix dave's fix :)

"object_type" was not defined at the point where a DELETE error was being

logged.

    • -2
    • +2
    /openacs-4/packages/search/tcl/search-procs.tcl
Add missing query for question choices stored in CR filesystem

More global parameters stuff: XML file parsing and package installation

Added a test for global parameter set/get value.

added security check to notifications sweep query - without this check and with no mechanism to remove requests for users who are no longer authorized, notifications still go out. not good.

The check for a blank tab was incorrect, because it didn't check to make

sure elements on the page were visible rather than hidden.

adding vendorwebuid to list to expand web resource opportunities

Oracle now passes the first set of global parameter tests. More to follow

for both PG and Oracle.

Fixed up the apm parameter stuff to the point where I can at least

register and unregister, and cache values of, global parameters. There's

some really funky code here, I also took the time to have the unregister

code use the unregister API in PL/[pg]SQL rather than roll its own.

    • -26
    • +11
    /openacs-4/packages/acs-tcl/tcl/apm-procs.tcl
    • -20
    • +17
    /openacs-4/packages/acs-tcl/tcl/defs-procs.tcl
Victor had made an upgrade script for version d4, and committed it before

I got around to adding and committing mine. So now my tcl upgrade commits

and my datamodel ones aren't synchronized :( But they're dev versions so

no harm should result.

If I'd known global parameters would be such a PITA, would I have TIP'd to

do them?

Turns out we must make a parameter value when a parameter is registered, else

all sorts of stuff dies. This is for PG. Oracle will come soon.

A bunch of stuff related to global/instance parameters.

Added 'embeds' to allowable dependencies.

Restored the data links upgrade script I'd accidently overwritten earlier.

1. added "bio" attribute to user rather than person (initial install was fine)

2. only make package instance parameter values for instance scope params