Error on installing

:-(
First, this thing is under radical development, so apologies, I wouldn't actually start building anything with it yet. This sandpit version is released due to interest, not as a workable entity.

second, yeah, not-an array sounds familiar. Different versions of PHP are more strict when accessing uninitialized variables.
I recall squashing a few of them recently that showed up on a remote test site, but I need to finish my current development stream before re-issuing to CVS.

I believe it wasn't debug.inc at all, but a recent change that combines my external statement layer with intrinsic node properties (so things like 'type' are exposed as node relationship/properties - this:isTypeOf:story )
But that's a bit messy in places. I've added in extra checks for existance. In CVS by the end of the day.

Thanks for the feedback, I need it!

.dan.

i...
i... think i've died and gone to heaven...
(interesting what kinds of things make people happy these days. for me it's a new drupal module. hmm...)

just awesome! very exciting. exactly what i need. trying to tweak tagnode, creating all sorts of redundant terms and content types to effect this but it's getting really messy. i can imagine users getting very confused by it. so this is very promising. thanks very much for all that work.

just downloaded from cvs, enabled relationship, listblock, and metadata_block, went to administer > relationships, and clicked on "add term" and i got the following (turned debug on "most actions" in settings):

New DataStore initialized. Non-caching, non inferencing direct link with the database table. This engine natively supports: inverseOf
: in relationship_datastore(), line 24 rdf_datastore.inc : in _relationship_datastore(), line 304 relationship_api.inc : in relationship_query(), line 224 relationship_api.inc : in relationship_get_statement(), line 476 relationship.module 0.01s elapsed. (0 total)
invalid argument [NULL] to relationship_get_longname(). Expected a string. 1
: in relationship_get_longname(), line 673 relationship.module : in _relationship_form_term(), line 474 administer_predicates.inc : in relationship_admin(), line 176 administer_predicates.inc : in call_user_func_array(), line 354 menu.inc 0.02s elapsed. (3 total)

i realize this is under very active development. but perhaps there's just something i failed to do? or this is related to the above installation error?

i'm just hoping i can have some simple relationships to show on a meeting on monday, using our own examples that users can relate to. so, it would be great if you can give me a quick fix on the add term error or just point me in the right direction. if not, i'll just show your demo site.

crashes Apache on sandbox: WinXP Pro, wamp5 1.4.3 (Apache 1.3.33, MySQL 4.1.8, PHP 5.0.3), Drupal 4.6.3

CGI timeout on server: Slackware Linux 10.2, Apache 2.0, PHP4.3, MySQL 4.0.20, Drupal 4.6.3

(aside: at one point i thought we're using the wrong tool for our app, that is, a CMS rather than RDBMS with web GUI dev. because what we're really doing is using drupal pages to represent data and it can be restrictive in that respect. but now i think there's hope. this is what semantic web is all about anyway, yes?)

This issue was assigned to you, so I didn't get the notifications from it :-/
Not sure how that is supposed to work.

Still not quite sure exactly what could be doing this, apart from the general flakiness of things.
I've run some installs on a few 'clean' boxes to try and make the first steps as smooth as possible, and it's not doing that for me.

Timouts would be a pain tho.I've got half the caching turned off, only the the terms are cached, not the DB lookups. Still not seeing these problems at my end, although I can imagine a very special oredr of dependancies COULD cause it, shouldn't happen out of the box.

I've been doing a lot on the widgets most recently, then on Ontology grouping - you can now assign the Drupal content types with specific types of predicates and properties. Basically flexinode done with standards!

The built-in axioms are looking more and more complex, but all the behaviours - what shows up in what select lists - are configured by settings elsewhere. This is why you may see them come and go a bit - it's almost self-modifying code!

I can only suggest trying tonights CVS and see if it goes away. De-activate the relationship modules, drop the table, CVS up the new stuff, and re-activate.
(that shouldn't make a lot of difference, but it will get to a 'last known good' state.

I am thinking of writing up a little demo/tutorial for it now, So I spent half the night looking at tools for that. They all suck, so I'm, building my own!

You are right about the CMS/ data management dichotomy. I started on this for a similar reason, and realized I was bridging the gap...

.dan.

De-activated the relationship modules, dropped the table, CVS-ed up the new stuff, and re-activated. and it works! thanks much.

now, is there an active forum topic on relationship usage, not development (i haven't done lisp for a while :) or can i continue posting here in issues? although i'm pretty sure our users will have an issue with that huge drop-down. would also be easier on them if that was a multi-select.

and as mentioned earlier, we're using this for data management--the relationship metadata is actually more part of data. in which case your older demo that showed the relationships inside the node instead of a metadata block would be preferable. is it still around? can't seem to find it.

is civiCRM already using this? it includes some relationship-ing tools.

looking forward to ontology_characteristics.module.