- Threadmark types, allows categorizing distinct from the main threadmark list.
- Permissions on threadmark categories define who can create a threadmark on a given category.
- Categories are admin defined.
- A post can only have 1 threadmark.
- Fix issue where moving a nested threadmark to a new category results in that thread's threadmark ordering for that category being uneditable.
The trouble with the positioning is once you have multiple categories it gets kinda nuts and makes responsive design very difficult.@Sidane, thanks, nice add-on.
One of the things I liked about this add-on was the neat positioning of the menu beside the pagination links, but having just installed it, it's showing below the pagination links. Any quick way to restore it to the side? Thanks,
View attachment 154525
Part of the problem is where the heck do you stick the UI option to hide those bits.@Sidane,
It would also be nice to have an option to have the 'add threadmark' show (or not) above the quick reply box.
Right now it looks a bit crammed there for something that will be used occasionally. MHO.
The various add-ons I maintain communicate they need you need to rebuild search indexes dynamically, they dump it into the error log for a lack of a better place to put it.One other thing, it would be nice to warn people in the first post that they will need to rebuild the search index. It's a bit worrying when you install an add-on and get a db error.
While I understand that, I'm really fond of the the original, simpler design, without categories, where you'd just have one drop-down labeled 'threadmarks'. I find it hard to see the need for this complexity on a thread level but again it's just MHO.The trouble with the positioning is once you have multiple categories it gets kinda nuts and makes responsive design very difficult.
It's great to know that it would restricted to the thread creator but to me this is a bit over the top, as it's really easy to just add the threadmark to a post once it's published. For now I just commented out that whole template.The 'add threadmark' above the quick reply only shows if you have permission to add a threadmark, so making another admincp option for it would be doable.
As I said before, I'm a fan, so there's no need to justify anything, besides the idea of throwing it in the error log is great.The various add-ons I maintain communicate they need you need to rebuild search indexes dynamically, they dump it into the error log for a lack of a better place to put it.
Upgrading any complex add-on tends to cause issues during the upgrade, I try my best but it is often hard to know what will break under-load while php files are being updated or XML file being applied.
- Do not special case touch for on-hover events in js
- Rework threadmarks menu to play nicer with touch
- Allow per-thread threadmark category cache to be injected with additional information
- Add statistics block to threadmarks index with option to disable it.
You need to grant the admin "Manage threadmarks" permission on the administrator page for the user. Super-administrators get all new permissions by default, normal administrators do not get new permissionsIt looks as if the page to define threadmark categories is limited to superadmins, not just admins. Is there a particular reason for that?
- Include Like count when fetching threadmarks, useful for theming on a thread's index page
- Elasticsearch v6 single-type support is complex so move it into https://xenforo.com/community/resources/enhanced-search-improvements.4762/
.XenBase li.threadmarkListItem .newIndicator {
color: #FFF;
background-color: #2e9bda;
border-color: #16628e;
}
.XenBase li.threadmarkListItem .newIndicator span {
display: none;
}
Look for the template modifications with the description "Add threadmarks on reply" and "Add threadmarks on quick reply", and disable them. Or edit the template quick_reply_threadmark and remove the contents
- Respect thread locked state when adding/editing/deleting threadmarks
- Surface some threadmark info as data attributes on threadmark index
We use essential cookies to make this site work, and optional cookies to enhance your experience.