Empathy List Archives

CP

Christopher Pott

Mon, May 14, 2012 1:03 PM

Hi,

I've recently upgraded to v2.3 of Collectionspace, and merged my configuration (domain and local extensions) from v2.0. Everything compiles, and I can see that tables are generated for my extensions in the database. I can create a collectionobject with no errors reported, both using the UI and testing with directly to services using curl. However, any extension data I provide is just ignored, and I can see it's not being stored in the db. I'm attempting some debugging, but can't find the cause yet - Has anyone got any advice on where I should concentrate my efforts? Any configuration differences since 2.0 that I may have missed?

Regards,
Chris

Hi, I've recently upgraded to v2.3 of Collectionspace, and merged my configuration (domain and local extensions) from v2.0. Everything compiles, and I can see that tables are generated for my extensions in the database. I can create a collectionobject with no errors reported, both using the UI and testing with directly to services using curl. However, any extension data I provide is just ignored, and I can see it's not being stored in the db. I'm attempting some debugging, but can't find the cause yet - Has anyone got any advice on where I should concentrate my efforts? Any configuration differences since 2.0 that I may have missed? Regards, Chris

RL

Ray Lee

Mon, May 14, 2012 3:21 PM

Hi Chris,
I had the same problem. It turns out there's been a change to the tenant-bindings file. All of the xmlns uris have changed from http://collectionspace.org/services/common/ to http://collectionspace.org/services/config/. I did a search and replace of those strings in tenant-bindings.delta.xml, and it fixed the problem.

Ray

On May 14, 2012, at 6:03 AM, Christopher Pott wrote:

Hi,

I’ve recently upgraded to v2.3 of Collectionspace, and merged my configuration (domain and local extensions) from v2.0. Everything compiles, and I can see that tables are generated for my extensions in the database. I can create a collectionobject with no errors reported, both using the UI and testing with directly to services using curl. However, any extension data I provide is just ignored, and I can see it’s not being stored in the db. I’m attempting some debugging, but can’t find the cause yet – Has anyone got any advice on where I should concentrate my efforts? Any configuration differences since 2.0 that I may have missed?

Regards,
Chris

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Chris, I had the same problem. It turns out there's been a change to the tenant-bindings file. All of the xmlns uris have changed from http://collectionspace.org/services/common/ to http://collectionspace.org/services/config/. I did a search and replace of those strings in tenant-bindings.delta.xml, and it fixed the problem. Ray On May 14, 2012, at 6:03 AM, Christopher Pott wrote: > Hi, > > I’ve recently upgraded to v2.3 of Collectionspace, and merged my configuration (domain and local extensions) from v2.0. Everything compiles, and I can see that tables are generated for my extensions in the database. I can create a collectionobject with no errors reported, both using the UI and testing with directly to services using curl. However, any extension data I provide is just ignored, and I can see it’s not being stored in the db. I’m attempting some debugging, but can’t find the cause yet – Has anyone got any advice on where I should concentrate my efforts? Any configuration differences since 2.0 that I may have missed? > > Regards, > Chris > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

PS

Patrick Schmitz

Mon, May 14, 2012 4:40 PM

Ouch - that was a nasty documentation gap. We'll make a note to address
that.

Thanks - Patrick

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Ray Lee
Sent: Monday, May 14, 2012 8:22 AM
To: Christopher Pott
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] configuring extensions on v2.3

Hi Chris,
I had the same problem. It turns out there's been a change to the
tenant-bindings file. All of the xmlns uris have changed from
http://collectionspace.org/services/common/ to
http://collectionspace.org/services/config/. I did a search and replace of
those strings in tenant-bindings.delta.xml, and it fixed the problem.

Ray

On May 14, 2012, at 6:03 AM, Christopher Pott wrote:

Hi,

I've recently upgraded to v2.3 of Collectionspace, and merged my
configuration (domain and local extensions) from v2.0. Everything compiles,
and I can see that tables are generated for my extensions in the database. I
can create a collectionobject with no errors reported, both using the UI and
testing with directly to services using curl. However, any extension data I
provide is just ignored, and I can see it's not being stored in the db. I'm
attempting some debugging, but can't find the cause yet - Has anyone got any
advice on where I should concentrate my efforts? Any configuration
differences since 2.0 that I may have missed?

Regards,
Chris

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace
.org

Ouch - that was a nasty documentation gap. We'll make a note to address that. Thanks - Patrick _____ From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Ray Lee Sent: Monday, May 14, 2012 8:22 AM To: Christopher Pott Cc: talk@lists.collectionspace.org Subject: Re: [Talk] configuring extensions on v2.3 Hi Chris, I had the same problem. It turns out there's been a change to the tenant-bindings file. All of the xmlns uris have changed from http://collectionspace.org/services/common/ to http://collectionspace.org/services/config/. I did a search and replace of those strings in tenant-bindings.delta.xml, and it fixed the problem. Ray On May 14, 2012, at 6:03 AM, Christopher Pott wrote: Hi, I've recently upgraded to v2.3 of Collectionspace, and merged my configuration (domain and local extensions) from v2.0. Everything compiles, and I can see that tables are generated for my extensions in the database. I can create a collectionobject with no errors reported, both using the UI and testing with directly to services using curl. However, any extension data I provide is just ignored, and I can see it's not being stored in the db. I'm attempting some debugging, but can't find the cause yet - Has anyone got any advice on where I should concentrate my efforts? Any configuration differences since 2.0 that I may have missed? Regards, Chris _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace .org