Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create another linking property #277

Closed
tobiasschweizer opened this issue Sep 29, 2016 · 4 comments
Closed

create another linking property #277

tobiasschweizer opened this issue Sep 29, 2016 · 4 comments
Assignees
Labels
bug something isn't working
Milestone

Comments

@tobiasschweizer
Copy link
Contributor

When creating another linking property (one is already existing), the GUI does not ask the ontology responder for the correct resource class information, but for knora-base:Resource

gui

@tobiasschweizer tobiasschweizer added this to the Beta Release milestone Sep 29, 2016
@tobiasschweizer tobiasschweizer added the bug something isn't working label Sep 29, 2016
@tobiasschweizer
Copy link
Contributor Author

tobiasschweizer commented Sep 29, 2016

the problem is in jquery.resadd.js:

case 'searchbox':
                                    {
                                        attributes.type = 'text';
                                        create_entry(propname, function(ele, attr) {
                                            var tmpele = $('<input>', attr).addClass('__searchbox').insertBefore(ele.find('.entrySep'));

                                            var restype_id = -1;
                                            var numprops = 1;
                                            var attrs = rtinfo.properties[pinfo].attributes.split(';');

the first time searchbox is created, pinfo is 0, the second time it is 2 (rtinfo.properties[pinfo].attributes.split(';')). This affects the restype that is submitted to the searchbox plugin. Firs, it is Person which is correct. The second time, it is Resource which is not correct.

@tobiasschweizer
Copy link
Contributor Author

When you try to add a new value of a linking property in jquery.propedit.js by clicking on the green plus icon, the application freezes.

@SepidehAlassi
Copy link
Contributor

SepidehAlassi commented Oct 13, 2016

When you remove an optional linking property in jquery.propedit.js by clicking on red cross button and then later add it by clicking on the green plus icon, the application gives "SALSAH.ApiGet ERROR: Internal Server Error error" and freezes.

@tobiasschweizer
Copy link
Contributor Author

The "SALSAH.ApiGet ERROR: Internal Server Error error" is caused by the GUI asking the oOntology Responder for knora-base:Resource which we removed from being returned because we do not want people to create instances of knora-base:Resource, but only subclasses of it.

benjamingeer pushed a commit that referenced this issue Nov 8, 2016
- Add a button for getting the creator and creation date of a value (#309, WIP)
- Change UsersResponderV1 not to return an Option, relying on exceptions instead (#297).
benjamingeer pushed a commit that referenced this issue Nov 15, 2016
#315)

* fix (salsah): Fix the creation of multiple linking properties (#277).

- Add a button for getting the creator and creation date of a value (#309, WIP)
- Change UsersResponderV1 not to return an Option, relying on exceptions instead (#297).

* feature (salsah): Finish implementing #309.

* test (add biblio-data): add biblio-data to the test data in the browser tests

* fix (webapi): Use FILTER NOT EQUALS instead of MINUS in changeLink.scala.txt for better performance on Fuseki.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants