Hello Chad, I just buyed ProBlog and I'm disappointed how tags widget works.

1. No spaces allowed in tags. Space should not automatically ending tag, but only enter or comma as it is.
2. No proper slug conversion for utf-8 tags. Slug transliteration is broken. When type some utf-8 character in widget slug is automatically ended (rest of characters from word are not included in slug). When adding tag in Tags backend section, there is no such problem, because October itself handle it well.
3. No autocomplete when typing.

Overall this is just totally unusable for me.

Better part are categories in links, I didn't test it but I guess it works well. I was just surprised it support only one category for post and one level (without categories nesting). Do you plan to improve this area?

Overall I'm happy just because I can support you as October developer, and October devs by this payment. But if this widget tags will stay like this, I cannot use ProBlog to anything.

Last updated 10 years ago

Thank you amdad for your candor. I agree with you - I think Tags in general could use some attention. I will make my best effort to improve that feature. Specifically auto complete, and will investigate utf-8 with spaces. This may take me some time as I do have a full time job. But I certainly do appreciate your support and feedback.

Thanks for reply Chad. Of course, no hurry. I'm happy you accept my proposal at all.

Also you it would be nice to update such a small things (should very easy to do) as new format for time and dates on backend lists.

05/26/16 01:20 pm when you and I are from europe, and use 24h format. In latest builds October improved a lot date and time formats for each language. Automatically display right way. So it will be 26 may 2016 13:20 or just 26.5.2016 13:20.

And list title columns should have this small icon on right, to configure which columns show/hide and how many posts should be displayed at once.

Both functions are easily available, new localised dates/time in latest October builds.

Ok - so I have autocomplete working, as well as allowing spaces. I am testing UTF-8 for example (Τὴ γλῶσσα μοῦ ἔδωσαν ἑλληνικὴ) and the slug that I see in the db is in fact "Τὴ-γλῶσσα-μοῦ-ἔδωσαν-ἑλληνικὴ". Could you post here an example of what utf-8 term you see as being truncated in the slug? I am not seeing that, and I am wondering if this is just how your db is set up?

yes, i will look into implementing system date/time that did not exist on initial dev. Good suggestion.

Try this words: słuchaj, więcej, nieźle

Last updated 10 years ago

I cannot find also option to remove tags from database.

when adding that tag via a post I now get "słuchaj,-więcej,-nieźle" as the slug. is this what you want? You want comma's in your slugs???

No, comma I use just for separation of examples. Slugs should be:

słuchaj = sluchaj, więcej = wiecej, nieźle = niezle

Already are broken like:

słuchaj = s, więcej = wi, nieźle = nie

So when widget meet unknown character it stop taking more letters. It should transliterate it like October do it when you type it in Titles. You can see how it works just by typing this words on Tags backend. There October transliterate it as it should be. Problem is in Widget, cannot do what October do very well in whole system.

Last updated 10 years ago

Already October normally disallow to use utf-8 in slugs at all. That's why it have transliteration. In other topic on ProBlog Forum we asked for support utf-8 in urls, but this should be optional and consistent. So now tags also should be transliterated instead of using original characters.

Please don't forget about buttons to remove tags from database. Now we can only add new.

After update, I see new localized dates working well. Also, autocomplete and spaces in tags works.

Transliteration of slugs is still broken.

mmm, I don't think so. I think this is something specific to your DB setup. I am not able to reproduce. The UTF8 in slugs works fine. Unless you are suggesting that the slugs translate to non-utf-8? in which case I would say that's not going to happen.

When I enter the same Tags through radiantweb/problog/tags/create (or /update) to Title field, slugs transliteration works perfect (like in the rest slugs in October). If I enter the same tag through widget on post page I have broken slugs. Try with words "słuchaj", "więcej", "nieźle", "zło" as I write before.

lol, I did. Again, your database is not setup to be utf-8 compliant. My testing of those terms work perfectly.

You laughing at me? :)

You're right, because in many cases I use SQLite database. This one which October created itself.

And when I drop it to mysql, then YES, in my case it not stripping down slugs. It just saving them directly without transliteration. Spaces are replaced by - OK. Though,

It's not bug it's a feature!

I tested, and also slugs of posts accept utf-8, so it seems like we have full localized links now. That's right! That's cool!

So the only last thing is... is my SQLite is broken? It is work for you on SQLite or you just not test it?