BUG: Crash on renaming a custom workflow

I have been having a problem with Verbum adding a (2) to custom workflows when they are initially created i.e. there is no other workflow sharing the name. When I tried to rename the workflow without the unneeded suffix, the system crashed.

VerbumCrash.zip

Find more posts tagged with

Comments

John Connell

I have found that if I try to create a clippings file with the same name as a passage list I get the (2) on the second document.

JBR

https://community.logos.com/discussion/comment/1205087#Comment_1205087

I have found that if I try to create a clippings file with the same name as a passage list I get the (2) on the second document.

I have recently noticed the same. I was using my tablet at the time so I wasn't sure whether it was due to the mobile app or whether that is just the characteristic of Logos.

To be clear my experience was on Logos and not Verbum and it was on the latest stable version (9.13) and not a beta. I think that suggests that it is an existing characteristic of Logos/Verbum in general.

Philana R. Crouch

I have been having a problem with Verbum adding a (2) to custom workflows when they are initially created i.e. there is no other workflow sharing the name. When I tried to rename the workflow without the unneeded suffix, the system crashed.

VerbumCrash.zip

MJ,

Your logs are out of date. Could you reproduce this and upload your logs. Does this happen consistently? Was the original name Untitled and then you are changing that? I'm having trouble reproducing your crash, but I think it's possible I'm not following the same steps and might be trying to rename it out of order. It would be helpful to know what you are doing step by step.

MJ. Smith

https://community.logos.com/discussion/comment/1205516#Comment_1205516

I'm not getting the crash today ... it was previously reproducible, but I have the new beta ...

Philana R. Crouch

https://community.logos.com/discussion/comment/1205579#Comment_1205579

I'm not getting the crash today ... it was previously reproducible, but I have the new eta ...

Ok, please let me know if you encounter this again.