Tiki Wiki CMS Groupware

I left the “Max size of tracker item title in the search engine friendly URL” to the default 200 characters. So we have nice URLs, which will be a lot better for SEO. Ex.: ... [More] https://dev.tiki.org/item2196-Tighter-integration-with-Apache-s-htaccess-error-messages I noticed last word is chopped off. I will inquire to see if this is a feature or a bug If text of tracker is changes, URL will still work, as with of SEFURLs (blog posts, etc.) So this works: https://dev.tiki.org/item2196-Tighter https://dev.tiki.org/item2196-ABC https://dev.tiki.org/item2196 And Canonical URL is what it should be [Less]

I left the "Max size of tracker item title in the search engine friendly URL" to the default 200 characters. So we now have nice URLs for wishes, which will be a lot better for SEO. Ex.: ... [More] https://dev.tiki.org/item2196-Tighter-integration-with-Apache-s-htaccess-error-messages I noticed last word is chopped off. I have inquired to see if this is a feature or a bug If text of tracker item is changed (which is to be expected), URL will still work, as with other SEFURLs (blog posts, etc.) So this all works: https://dev.tiki.org/item2196-Tighter https://dev.tiki.org/item2196-ABC https://dev.tiki.org/item2196 And Canonical URL is what it should be. Thank you Ricardo Melo for having coded this recently. And thank you to Sylvie Greverend and Sébastien Lord-Jetté for the smart original SEFURL design on blog posts and articles. [Less]

Preference name: tracker_show_comments_below This seems better to me. We can revert if there are objections.

Preference name: tracker_show_comments_below This seems better to me. We can revert if there are objections.

Preference name: tracker_show_comments_below This seems better to me. We can revert if there are objections.

I have renamed the "Blocker" ticket category to "Release Blocker" to make it more clear and prevent false assignments of reported issues to this category. Also added the following description to it: The bug or issue would prevent ... [More] releasing new Tiki version because it would break installation/usability of the site or existing sites when upgraded to it. [Less]

I have renamed the "Blocker" ticket category to "Release Blocker" to make it more clear and prevent false assignments of reported issues to this category. Also added the following description to it: The bug or issue would prevent ... [More] releasing new Tiki version because it would break installation/usability of the site or existing sites when upgraded to it. [Less]

I have renamed the "Blocker" ticket category to "Release Blocker" to make it more clear and prevent false assignments of reported issues to this category. Also added the following description to it: The bug or issue would prevent ... [More] releasing new Tiki version because it would break installation/usability of the site or existing sites when upgraded to it. [Less]

I have renamed the "Blocker" ticket category to "Release Blocker" to make it more clear and prevent false assignments of reported issues to this category. Also added the following description to it: The bug or issue would prevent ... [More] releasing new Tiki version because it would break installation/usability of the site or existing sites when upgraded to it. [Less]

I have renamed the "Blocker" ticket category to "Release Blocker" to make it more clear and prevent false assignments of reported issues to this category. Also added the following description to it: ... [More] The bug or issue would prevent releasing new Tiki version because it would break installation/usability of the site or existing sites when upgraded to it. [Less]