I seperate keywords both with commas and semicolons in my Gallery2-Installation. After import to Gallery3 only separations with semicolons seem to work. The result are broken keywords.
Example:
Gallery2: tag1, tag2; tag3 = "tag1" "tag2" "tag3" = three keywords with correct separation
Gallery3: tag1, tag2; tag3 = "tag1, tag2" "tag3" = two keywords with false separation after import of g2-data
*I'm using the keywords-album-module, not the 3rd party tags-module.
Posts: 16503
First make sure you're using the latest experimental code:
http://codex.gallery2.org/Gallery3:Upgrading
If it still does this, file a ticket please:
https://sourceforge.net/apps/trac/gallery/newticket
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 16
Ok, i'm using a two-days-old git-version. So i did file a ticket.
Posts: 16503
There have been changes since then.
I don't think to this specifically, but in the future if reporting bugs, feature requests, etc, please always make sure you're running the latest experimental code while before we have our first final release.
Thank you filing the ticket:
https://sourceforge.net/apps/trac/gallery/ticket/822
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 16
Thanks, nivekiam! i promise to use the very latest code next time
Posts: 22892
I would not get my hopes up in this being fixed. It was a big task to get multi word tags/phases imported properly.
Tags was a 3rd party module, most users perhaps greater than the 80/20, used one method to add tags in G2 and not a combination.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 16
Floridave, sorry for not being specific enough: I'm using the official keyword album module in G2, not the 3rd party tags-module. I will correct this in the ticket.
Posts: 358
I closed the ticket with a reason of wontfix.
Semicolon is the only supported separator in g3.
Because of the variability of keywords (i.e. free form), we have no idea what was used for a separator. So the we look for a semicolon first and if its there, then that becomes the separator. If there are no semicolons it checks for a comma as the separator. If it can't find either of those it uses a space.
http://www.timalmdal.com
Posts: 16503
Are you sure, or am I not following you correctly? I can separate tags with commas (which I believe is what most people prefer), but not with semicolons. Separating tags with commas, creates multiple tags, but separating tags with spaces or semicolons creates long, single tags.
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 358
Oops, I stand corrected, got it backwards... we only support comma's as a tag separator. Thanks for the correction nivekiam.
http://www.timalmdal.com
Posts: 16503
Then, in that case, isn't the G2 Import module kind of handling it backwards? Shouldn't the poster's example end up a bit different?
Shouldn't that end up being "tag1", "tag2; tag3" in G3?
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 358
There are two separate issues here which are mutually exclusive:
1) How to convert from g2 keywords
2) How tags are separated from each other when entered in g3.
In the first, determination of the keyword seperator is handled as I described. The second uses a comma as a separator.
I can't remember how keywords are stored in g2, but I believe that it is one field. So in his example of tag1, tag2; tag3 and based on the algorthim described above, the import checks for a semicolon first and finds one. It then proceeds to separate the keywords into two tags <tag1, tag2> and <tag3>. So its working as designed which leads to the won't fix resolution on the ticket.
http://www.timalmdal.com
Posts: 16503
Thanks. Just wasn't sure of the logic behind the scenes.
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here
Posts: 16
@all: I can live with this issue and will clean up my G2-data before the final import. By the way: G3 works out great so far!!