Posted by hendler on March 19, 2008 at 4:20am
Jump to:
| Project: | Semantic Search - Faceted Search and Semantic Web |
| Version: | 5.x-1.x-dev |
| Component: | Store :: Sesame |
| Category: | bug report |
| Priority: | critical |
| Assigned: | hendler |
| Status: | closed (fixed) |
Issue Summary
"I changed the name of the subcategory 'Treatment Programs' to 'Substance Abuse Treatment Programs', and now, neither subcategory appears on the home page. I also move 'Pregnant Women and Children' from Finding Health Care to a subcategory of Income-Based-Programs, and it also does not appear as a subcategory or a sub-subcategory."
Likely cause:
I use two different Sesame interfaces, one custom, and one using the standard store. Because I use a Sesame Memory store for each, they are not synchronized. The update is sent to the custom API, and the read for the literal of the category names comes from the standard Sesame REST api.
Comments
#1
Notes:
* does not use sesame HTTP transaction URL, as it once did.
* updates not showing in workbench
* either the transaction is cancelled
* or the repos are different.
* the altered one does not include the superclass of the CCK type
* on hook_nodeapi this works correctly
* the poblem begins with on node_taxonomy on updates
* request is properly recieved
#2
Further notes:
1. The logfile location is not working, either because of permissions, or or the config is not being passed. Either way, now the log messages are printed to console as a temporary fix. This should be fixed later.
2. "java.lang.IllegalArgumentException: Not a valid (absolute) URI: " - this error is new to sesame 2.0, and appears to happen when there is an uri. This fixes the issue with adding new statements.
3. the other likely cause is still , as above, "the altered one does not include the superclass of the CCK type"
#3
issue identified and generally fixed.
Appears that several issues were the cause
* transaction failed
* the identification of a taxonomy term as actually a class failed because the update did not complete
Remaining cleanups:
* verify that the normal editing can occur and no associations are lost, and that hierarchical relationships can be altered without issue
* test on windows server
#4
remaining issues:
* crashes on 0 results - see http://drupal.org/node/174853
* may still be sync issues but looking better
#5
marking fixed
will test on server shortly
#6
appears to work as expected.
testing not extensive - may be reopened, or opened as another bug if issues come up