New tags have "undefined" in the name #430

Closed
FTWilliams opened this Issue Apr 12, 2016 · 16 comments

Comments

Projects
None yet
@FTWilliams

First time user, running a Windows machine (Lenovo laptop) using Windows 8.1.
I just installed Tagspaces and went to organize an image folder (.jpgs and .pngs). I created some tags, selected about 100 images and choose "tag selected files."

As soon as I did I started getting a series of Alert messages saying "Renaming [filename] failed."

A few minutes later I went to my folder and every image had been deleted (they were there -without question- before I ran Tagspaces). I went back to the Tagspaces viewing pane and every image that I had tagged was still listed but it wouldn't display the image, instead the displaying the default .jpeg image showing it failed to load.

In the file folder itself all the images are there, but they have new filenames: "[Original Filename]"undefined"[tag]"undefined"[tag]"undefined..." (the last bit repeats a few times). I can't rename the files or view their properties.

Thankfully, these are not one-of-a-kind, high-importance images, but I'd still like to recover them and find out why Tagspaces did this. The only thing I can really think of is that the tag included some dashes ("-"), but those weren't flagged by the program and are perfectly acceptable in a windows filename.

@FTWilliams

This comment has been minimized.

Show comment
Hide comment
@FTWilliams

FTWilliams Apr 12, 2016

Update: I tried to tag a few more files the same way to see if I could catch anything I missed and it worked fine. The tags have been applied correctly (for the first batch the tags don't look to be completely correct; I colored them red, but they're showing the default green) and the images are still viewable.

All the same, definitely not going to use this on any important files, at least until I'm certain I know what went wrong and how to avoid it.

Update: I tried to tag a few more files the same way to see if I could catch anything I missed and it worked fine. The tags have been applied correctly (for the first batch the tags don't look to be completely correct; I colored them red, but they're showing the default green) and the images are still viewable.

All the same, definitely not going to use this on any important files, at least until I'm certain I know what went wrong and how to avoid it.

@mladensap

This comment has been minimized.

Show comment
Hide comment
@mladensap

mladensap Apr 13, 2016

Member

Hello,
could you tell us exactly which version of the program you use, to try to reproduce the error?
Thanks in advance.

Member

mladensap commented Apr 13, 2016

Hello,
could you tell us exactly which version of the program you use, to try to reproduce the error?
Thanks in advance.

@FTWilliams

This comment has been minimized.

Show comment
Hide comment
@FTWilliams

FTWilliams Apr 13, 2016

It's version 2.2.1. (I just installed it yesterday).

It's version 2.2.1. (I just installed it yesterday).

@mladensap

This comment has been minimized.

Show comment
Hide comment
@mladensap

mladensap Apr 13, 2016

Member

32 bit or 64 bit?

Member

mladensap commented Apr 13, 2016

32 bit or 64 bit?

@FTWilliams

This comment has been minimized.

Show comment
Hide comment

64 bit.

@uggrock uggrock changed the title from Tagspaces broke all images I tried to tag (they cannot be viewed, opened or altered) to New tags have "undefined" in the name Apr 19, 2016

@jeanbaptisteC

This comment has been minimized.

Show comment
Hide comment
@jeanbaptisteC

jeanbaptisteC Apr 19, 2016

Dear all,

I have just downloaded and started your program which seems very promising,

I run 2.2.1 version with lubuntu 12.04 32 bits, and I got the issue that is mentioned here. Each new files tagged as an undefined added, when I try to show files with this tag, nothing shows up.

Thank you,

Dear all,

I have just downloaded and started your program which seems very promising,

I run 2.2.1 version with lubuntu 12.04 32 bits, and I got the issue that is mentioned here. Each new files tagged as an undefined added, when I try to show files with this tag, nothing shows up.

Thank you,

@abruenin

This comment has been minimized.

Show comment
Hide comment
@abruenin

abruenin Apr 29, 2016

Same problem with Windows, tried with several, now on 2.2.5. 32 bit works, 64bit messes up the tags with 'untitled'.

Same problem with Windows, tried with several, now on 2.2.5. 32 bit works, 64bit messes up the tags with 'untitled'.

@roxfanuk

This comment has been minimized.

Show comment
Hide comment
@roxfanuk

roxfanuk May 3, 2016

Linux Mint 17.3 with 64-bit TagSpaces 2.3.0 - BuildID: 2.3.0.20160429112036

Same problem, my guess is that the 64 bit version is missing the comma seperator for the tags - where it should be, the word "undefined" gets written instead.

roxfanuk commented May 3, 2016

Linux Mint 17.3 with 64-bit TagSpaces 2.3.0 - BuildID: 2.3.0.20160429112036

Same problem, my guess is that the 64 bit version is missing the comma seperator for the tags - where it should be, the word "undefined" gets written instead.

@viktor-c

This comment has been minimized.

Show comment
Hide comment
@viktor-c

viktor-c Jun 29, 2016

Hi friends!
Using Linux Mint 18 Beta and
TagSpaces 2.4.0 - BuildID: 2.4.0.20160609091902

Problem is when adding one or multiple built-in tags, imported or newly create tags to a file, undefined appears.
Hope this gets a fix soon :)

UPDATE
After restarting computer and app everything is working just fine. Weird...

viktor-c commented Jun 29, 2016

Hi friends!
Using Linux Mint 18 Beta and
TagSpaces 2.4.0 - BuildID: 2.4.0.20160609091902

Problem is when adding one or multiple built-in tags, imported or newly create tags to a file, undefined appears.
Hope this gets a fix soon :)

UPDATE
After restarting computer and app everything is working just fine. Weird...

@Buena-Vista

This comment has been minimized.

Show comment
Hide comment
@Buena-Vista

Buena-Vista Aug 23, 2016

newly installed v2.4.0 got the same "undefined" error when tagging with or without a pre-existing tag. restarted the program (running in portable mode), now it works. quite bizarre. maybe it was because I changed options during that first execution and didn't restart?

but now.....
no space between the title and [tags] even on fairly short names. the docs say a space should exist and I'd prefer that.

I'm actually teaching myself nw.js right now. I look forward to maybe helping out some day, altho I'm a slow learner. This looks like a great tool. Best wishes for continued success.

newly installed v2.4.0 got the same "undefined" error when tagging with or without a pre-existing tag. restarted the program (running in portable mode), now it works. quite bizarre. maybe it was because I changed options during that first execution and didn't restart?

but now.....
no space between the title and [tags] even on fairly short names. the docs say a space should exist and I'd prefer that.

I'm actually teaching myself nw.js right now. I look forward to maybe helping out some day, altho I'm a slow learner. This looks like a great tool. Best wishes for continued success.

@uggrock

This comment has been minimized.

Show comment
Hide comment
@uggrock

uggrock Oct 12, 2016

Member

I will close this issue since, there are no reports for reproducing it with 2.5.0

Member

uggrock commented Oct 12, 2016

I will close this issue since, there are no reports for reproducing it with 2.5.0

@uggrock uggrock closed this Oct 12, 2016

@lanzafame

This comment has been minimized.

Show comment
Hide comment
@lanzafame

lanzafame Oct 31, 2016

Running version 2.5.0 - BuildID: 2.5.0.20160905130746a on Fedora 25 64bit. Attempted to add two tags to a batch of pdf's and they were renamed with undefined at the end of the filename and then undefined after each tag I had applied.

Running version 2.5.0 - BuildID: 2.5.0.20160905130746a on Fedora 25 64bit. Attempted to add two tags to a batch of pdf's and they were renamed with undefined at the end of the filename and then undefined after each tag I had applied.

@nmarshall23

This comment has been minimized.

Show comment
Hide comment
@nmarshall23

nmarshall23 Nov 9, 2016

Running version 2.5.0 - BuildID: 2.5.0.20160905130746 on Ubuntu 14.04.5.

Trying to add a tag, say named TagName add TagNameundefined is added as a tag. When I try to remove the tag, it now has a undefinedundefined tag. Trying to remove that tag I get undefinedundefinedundefined.

nmarshall23 commented Nov 9, 2016

Running version 2.5.0 - BuildID: 2.5.0.20160905130746 on Ubuntu 14.04.5.

Trying to add a tag, say named TagName add TagNameundefined is added as a tag. When I try to remove the tag, it now has a undefinedundefined tag. Trying to remove that tag I get undefinedundefinedundefined.

@roxfanuk

This comment has been minimized.

Show comment
Hide comment
@roxfanuk

roxfanuk Dec 12, 2016

I should add that my issue resolved itself after uninstalling, then (attempting) installing 32bit version, then reinstalling 64bit.
After that it was fine. No idea how, but maybe worth some experimentation if anyone has the energy.
After that no more undefined tags. Wondering if a restart after install helps...

roxfanuk commented Dec 12, 2016

I should add that my issue resolved itself after uninstalling, then (attempting) installing 32bit version, then reinstalling 64bit.
After that it was fine. No idea how, but maybe worth some experimentation if anyone has the energy.
After that no more undefined tags. Wondering if a restart after install helps...

@BotChen

This comment has been minimized.

Show comment
Hide comment
@BotChen

BotChen Jan 21, 2017

Same issue for me running version 2.6.0 on 32bit Windows 10.
undefined
Should the "undefined" be something like "," ?

BotChen commented Jan 21, 2017

Same issue for me running version 2.6.0 on 32bit Windows 10.
undefined
Should the "undefined" be something like "," ?

@uggrock uggrock reopened this Jan 21, 2017

@uggrock

This comment has been minimized.

Show comment
Hide comment
@uggrock

uggrock Jan 21, 2017

Member

Issue is preliminary fixed in version 2.6.4. An improved fix will follow in version 2.7

Member

uggrock commented Jan 21, 2017

Issue is preliminary fixed in version 2.6.4. An improved fix will follow in version 2.7

@uggrock uggrock closed this Jan 21, 2017

uggrock added a commit that referenced this issue Jan 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment