Add oroperty hangs

[Roland Cornelissen]

HI
I use OntoWIki 1.0 and try to add a property to an ontology. It hangs on the progress indicator and no popup screen is shown....
I feel I am missing something here :)

Thanks,
Roland

[Roland Cornelissen]

ok, that should have been Property

I jjust noticed that adding a property to a resource of a certain type works well!
It's only adding a property to an ontology (KnowledgeBase) that hangs.
 

[Natanael Arndt]

Hey Roland,
how exactly did you try to add the property to the ontology? Maybe you could give us a step by step explanation, so we can reproduce and hopefully fix the issue.

All the best,
Natanael

--

---
You received this message because you are subscribed to the Google Groups "OntoWiki User Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ontowiki-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Roland Cornelissen]

Hi Nate!

how exactly did you try to add the property to the ontology? Maybe you could give us a step by step explanation, so we can reproduce and hopefully fix the

 

issue.

I select in the box Knowledge Bases for a certain KB the option 'View as Resource'. In the main screen I click the button 'Add Property', then the progress indicator appears and never dissapears again... no pop-up to select a property.

As mentioned before, whe I click the button Add Resources for an individual of a certain type the popu-up box appears fast and beautifull.

BTW, Very nice job you guys have done on the 1.0 version!

Thanks,
Roland

[Shinobu]

Heyho Roland,

I followed your steps and had no problems adding a property to the KB

could you tell us a few things about your setup?

I tried your steps with:
OntoWiki on 35feb9 (1.0 release)

Virtuoso on 07.20.3217-pthreads

PHP on 5.9.9-1ubuntu4.19

Firefox 48.0 without Javascript deactivation addons

running on Ubuntu 14.04

if the progress indicator it the greyed out screen, it might be a problem with js, so do you have any errors in the console of your browser?

Greetings,

Shinobu

[Roland Cornelissen]

Hi Shinobu,

Thanks for your reply! It has been a while but I just bumped into this issue again. I didn't find any JS errors but I discovered that the issue only happens with a certain KB. Another KB works fine, i.e. popup with input form. I don' t know what's 'wrong' with the KB ... The only difference I find in he SPARQL endpoint is that the ontology having the issue is lacking the rdf:type predicate with object owl:Ontology.

I will try later if this fixes the issue.

Thanks,

Roland

[Roland Cornelissen]

Hi Shinobu,
I ran into another situation having the same behaviour; adding a property to an existing resource hangs on a greyed out screen ... I don't understand why, but it happens both in Firefox and in Chrome. When I open the javascriot console in Chrome there are 6 deprecation warnings [1].
Could this be related? Could an update of jquery provide a solution?

Thanks,
Roland

[1]
jquery-migrate-1.3.0.js:23 JQMIGRATE: Logging is active
jquery-migrate-1.3.0.js:43 JQMIGRATE: jQuery.attrFn is deprecated
migrateWarn @ jquery-migrate-1.3.0.js:43
jquery-migrate-1.3.0.js:45 console.trace
migrateWarn @ jquery-migrate-1.3.0.js:45
jquery-migrate-1.3.0.js:43 JQMIGRATE: jQuery.browser is deprecated
migrateWarn @ jquery-migrate-1.3.0.js:43
jquery-migrate-1.3.0.js:45 console.trace
migrateWarn @ jquery-migrate-1.3.0.js:45
jquery-migrate-1.3.0.js:43 JQMIGRATE: jQuery.fn.andSelf() replaced by jQuery.fn.addBack()
migrateWarn @ jquery-migrate-1.3.0.js:43
jquery-migrate-1.3.0.js:45 console.trace
migrateWarn @ jquery-migrate-1.3.0.js:45
jquery-migrate-1.3.0.js:43 JQMIGRATE: jQuery.fn.live() is deprecated
migrateWarn @ jquery-migrate-1.3.0.js:43
jquery-migrate-1.3.0.js:45 console.trace
migrateWarn @ jquery-migrate-1.3.0.js:45
jquery-1.9.1.js:8492 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery-1.9.1.js:8492
jquery-migrate-1.3.0.js:43 JQMIGRATE: jQuery.fn.die() is deprecated
migrateWarn @ jquery-migrate-1.3.0.js:43
jquery-migrate-1.3.0.js:45 console.trace
migrateWarn @ jquery-migrate-1.3.0.js:45





Op zaterdag 17 december 2016 17:20:18 UTC+1 schreef Shinobu:

[Roland Cornelissen]

 just tried to run OntoWiki (SIlverblue theme ) with jquery3.1.1 and jquery-ui-1.12.1, the most recent versions. Alsa a the newer version jquery-migrate-1.4.1 was used. Now I get different error messages in the javascript console in Chrome, as in [1], But the problem still remains; grey screen when adding a property to a resource.
The message that appears when this situation happens is this:

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

send @ jquery-3.1.1.js:9425
ajax @ jquery-3.1.1.js:9143
queryGraph @ rdfauthor.js:1959
_fetchPredicateInfo @ rdfauthor.js:550
_populateView @ rdfauthor.js:865
(anonymous) @ rdfauthor.js:2135
_callIfIsFunction @ rdfauthor.js:271
RDFA.CALLBACK_DONE_PARSING @ rdfauthor.js:803
(anonymous) @ rdfa.js:1836
RDFA.GRDDL.runProfiles @ rdfa.js:1419
(anonymous) @ rdfa.js:1432
RDFA.GRDDL.DONE_LOADING @ rdfa.js:1389
(anonymous) @ xhtml1-hgrddl.js:93

This message was the same with the other jquery version.

Still don't know how to resolve this issue....
Cheers,
Roland


[1]
JQMIGRATE: Migrate is installed with logging active, version 1.4.1
jquery-migrate-1.4.1.js:45 JQMIGRATE: jQuery.browser is deprecated
migrateWarn @ jquery-migrate-1.4.1.js:45
jquery-migrate-1.4.1.js:47 console.trace
migrateWarn @ jquery-migrate-1.4.1.js:47
jquery-migrate-1.4.1.js:45 JQMIGRATE: jQuery.fn.andSelf() replaced by jQuery.fn.addBack()
migrateWarn @ jquery-migrate-1.4.1.js:45
jquery-migrate-1.4.1.js:47 console.trace
migrateWarn @ jquery-migrate-1.4.1.js:47
jquery-migrate-1.4.1.js:45 JQMIGRATE: jQuery.fn.live() is deprecated
migrateWarn @ jquery-migrate-1.4.1.js:45
jquery-migrate-1.4.1.js:47 console.trace
migrateWarn @ jquery-migrate-1.4.1.js:47
jquery-3.1.1.js:3855 Uncaught Error: Syntax error, unrecognized expression: a[href='javascript:navigationEvent('toggleHidden')']
    at Function.Sizzle.error (jquery-3.1.1.js:1586)
    at Sizzle.tokenize (jquery-3.1.1.js:2238)
    at Sizzle.select (jquery-3.1.1.js:2665)
    at Function.Sizzle (jquery-3.1.1.js:890)
    at Function.jQuery.find (jquery-migrate-1.4.1.js:290)
    at jQuery.fn.init.find (jquery-3.1.1.js:2921)
    at jQuery.fn.init.jQuery.fn.find (jquery-migrate-1.4.1.js:677)
    at jQuery.fn.init (jquery-3.1.1.js:3031)
    at jQuery.fn.init (jquery-migrate-1.4.1.js:241)
    at jQuery (jquery-3.1.1.js:98)
jquery-3.1.1.js:1586 Uncaught Error: Syntax error, unrecognized expression: a[href='javascript:navigationEvent('toggleHidden')']
    at Function.Sizzle.error (jquery-3.1.1.js:1586)
    at Sizzle.tokenize (jquery-3.1.1.js:2238)
    at Sizzle.select (jquery-3.1.1.js:2665)
    at Function.Sizzle (jquery-3.1.1.js:890)
    at Function.jQuery.find (jquery-migrate-1.4.1.js:290)
    at jQuery.fn.init.find (jquery-3.1.1.js:2921)
    at jQuery.fn.init.jQuery.fn.find (jquery-migrate-1.4.1.js:677)
    at jQuery.fn.init (jquery-3.1.1.js:3031)
    at jQuery.fn.init (jquery-migrate-1.4.1.js:241)
    at jQuery (jquery-3.1.1.js:98)
jquery-3.1.1.js:9425 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery-3.1.1.js:9425
widget.property.js:549 Uncaught TypeError: Cannot set property '_renderItem' of undefined
    at W._init (widget.property.js:549)
    at W.ready (widget.property.js:71)
    at Selector.presentInContainer (rdfauthor.selector.js:48)
    at addProperty (support.js:736)
    at <anonymous>:1:1





Op woensdag 25 januari 2017 16:37:51 UTC+1 schreef Roland Cornelissen:

[Pantelis Natsiavas]

Hi. 

I have also the same problem.

I deployed the Windows binaries on a cloud VM on Windows Server 2012 using Virtuoso 7.2 as a back-end to explore OntoWiki. My VM has 8GB and despite that, OntoWiki is a little bit slow. However, when adding a property, OntoWiki hangs.

On Mozilla Firefox, I get a grayed screen when I click "Add property" on a specific resource. 

On Chrome, I get an infinitely working javascript "Loader" animation.

I had the same behavior when trying to add "Admin" password in the fist steps of my installation.

I can see no errors on the server side log (I have already enabled the "debug" option on the configuration" and I can only see "deprecated" messages in the javascript console.

Is there a known solution on this issue? Since I am currently exploring the OntoWiki tool, I could provide access to the VM in order to debug the issue.

Thank you in advance,

Pantelis Natsiavas

[Pantelis Natsiavas]

Hello.

I kindly ask if there is anybody following this email list? 

Does anybody know if this project is dead?

Best regards,

Pantelis Natsiavas

[Natanael Arndt]

Hi,

yes I'm following the list. We just have no instant support team to follow up the mails since this a community project.

Regarding your problem, which version of OntoWiki are you using, from which source did you install it?

The OntoWiki project is not dead but big changes have to follow and will follow. The problem is, that the current OntoWiki implementation is running on PHP 5 where the support ended in December 2018 (https://secure.php.net/supported-versions.php) and it was not yet possible to update it to run in PHP 7. Currently we are working on a new technology stack to implement OntoWiki which will be published hopefully soon.

Kind regards,
Natanael

--

[Pantelis Natsiavas]

Hi Natanael,

Thank you very much for your response. I used the windows binaries available on github.

Info presented on the ontowiki installation "About" page.

Release 1.0.0

PHP Version 5.6.40

Please note, that I could also provide you direct access on the VM if that is convenient.

Best regards,

Pantelis Natsiavas