Jump to content

Ryan H.

Members
  • Posts

    4,489
  • Joined

  • Last visited

  • Days Won

    9

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Ryan H.

  1. I'm not aware of any circumstances that could cause that, nor what measures you could do to restore whatever was there before (short of database work). If the data's gone, it's gone.
  2. I'll have to update that text. I revamped that whole section in the last release for 4.2 compatibility, and sorting by usage is no longer realistic (too resource-intensive).
  3. Sure, that's possible. All CSS. The default prefix formatting has style="...", you just need to fill in the dots. color: gold; makes colored text. background: black; makes black background. http://www.corelangs.com/css/text/csscolor.html
  4. Okay, I'll investigate. Won't have any short-term solution.
  5. Is that on the latest version? Correct. Feel free to PM me.
  6. I'm not aware of any such issue, I can't really help with installer errors like that though. Contact IPS support?
  7. Hm, I'll look into that. Yeah, do it, shouldn't hurt.
  8. Nothing's broken though. It just looks a little off. It's nothing to do with the bold text, just styling. It shouldn't be hard to work around, I'm just not going to publish a release just for that. I missed it on the last update.
  9. No change. Not considering it a breaking issue.
  10. Can you give more context? Before/after screenshots?
  11. That's going to be 'not a bug' on both parts, I'm afraid. Prefixes are tags internally, just special ones. That means a given member must be able to use tags in order to use prefixes.
  12. No progress. I can't provide any timeline at this point.
  13. Sounds like a plausible issue. I'll look into it.
  14. Unlucky just said the same thing. I'll look into it.
  15. Can you take a screenshot or two to show what you mean?
  16. I think it's all or nothing with predefined tags--so no. It sounds like the tag cache didn't actually rebuild properly. What version of IPB and AT&P? Coloring, tags? You mean prefixes? Screenshot?
  17. No. Won't be coming. I'll look into that, thanks. You can't delete them from the tag manager?
  18. Ah, I see. That makes sense. Might be able to do something about that.
  19. Oh, I missed that during prep. One of these updates.
  20. Update is out. @jair101: It turns out my copy had some fixes for special chars on tag management from some months back. They're included. Notes of caution on this update: Clubs: Club forums are just like regular ones, except for the part where they aren't like them in any way. You can edit them in the admin by going to Clubs > {edit club} > Forums > {edit forum}. The normal tag/prefix settings will now appear there. These settings cannot be changed from the frontend by the club owner. I have no intention of changing that. Tag quick-edit: This should respect context settings now (forum-specific tag restrictions, etc.). BUT IPS bakes prefix handling into that same input, and gave me no way to change that. That means the prefix can be changed from the tag list with no regard for permissions or prefix restrictions. The only alternative is having tag quick-edit unset any prefix entirely, which seemed worse. There's nothing I can do about it. Mage Tags: I revamped the manage tags section out of necessity. The old DB table it was using before gets worse with every release. The new one should work more reliably (no more page count bug!), but I have no idea how well it will scale for sites with thousands or millions of tags. If the answer is 'not well', my ability to improve that is probably limited. What's New in Version 3.1.9 This release targets IPS 4.2. Backwards compatibility to 4.0 is likely, but not guaranteed. Added tentative support for Clubs forums (settings can be edited via Club forums in admin). Added tentative support for tag quick-editing on frontend. Note: Prefixes fall back to default functionality in that context; this is unavoidable. Refactored Manage Tags section to fix SQL grouping errors and paging quirks. Improved caching performance. Fixed some instances of tag case insensitivity. Fixed lingering tag edit/delete encoding issues.
  21. I don't know much about the automation plugin, so I really can't answer what it's capable of. I believe it does have some ability to touch tags/prefixes, but you'll have to ask its author about that.
×
×
  • Create New...