Closed svatek closed 10 years ago
Ondra, could you, please, give us a feedback for this issue? It's probably related to your bachelor thesis, isn't it?
Thanks
Yes, customizations are part of my thesis.
The error seems to occur while working with older customizations. Creating a new customization (ontology based or user defined) with some content (node, edge or node based on edge customization) does not seem to reproduce the error. On the other hand I recieved the error when trying to add a node (or any other content) to an older user customization (I have not changed that particular customization for over a month). That points to a possible inconsistency of database.
I'll try to reproduce the error on my local instance of Payola to see where the problem is.
To avoid a misunderstanding: I am speaking about a brand new customization. I never tried editing an old one so far.
I can't seem to reproduce the error. I guess you are working with the production version on live.payola.cz, aren't you. Could you, please, try doing the same thing on live.payola.cz:8080 (the development version)? You can login there with the same credentials accessing the same data as on live.payola.cz. (But, please, do not use that version of Payola regularly - it's not stabel.) I'll record a video later today, so you could show me, what you are doing differently.
It's not stable, but Vojtech tries to learn how customizations in Payola works. Since the latest version of customizations is on :8080 (develop), it is best for him to use that instance of Payola.
Moreover, I detected more customization errors in master, but they alll seem to be repaired in develop.
Exactly same behavior (bug) observed on the dev version, http://live.payola.cz:8080/. Aside additional usability issues (especially in FF, where the customized node selection dialog window cannot be closed - worth another bugreport, but let's say it's just optimized for Chrome...).
Ondra contacted me. Due to the deployment fault, there was a wrong version of Payola running on :8080 since yesterday's afternoon. We fixed this and starded the right version. That's also why the UI was kind of broken.
Sorry for that.
Tested, now works (for User Customization at least), thanks. The only minor issue is that a new customization makes the edge labels disappear from the diagram; this may be desirable, but perhaps not always. I can live with it.
When a customization is applied the labels are hidden intentionally. It is desired behavior. If needed, the labels can be shown again by selecting one of the edge's vertices.
Choosing a feature for a new customization (ontology or user) immediately results in fatal error: "Class cannot be found in any ontology/user customization!" The customization remains accessible but with empty dialog window only allowing sharing/deletion. Tested both in Chrome and FF.