Jump to content

bfarber

Clients
  • Posts

    163,911
  • Joined

  • Days Won

    346

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by bfarber

  1. No, they're not checked for avatars. The whitelist/blacklist is used when parsing url and img tags in a post - not when posting links for your avatar, in custom bbcode, etc. The word filter would have no relevance whatsoever on an avatar, since it's an image and not posted words.
  2. The url filtering should already apply to signatures. All the parsing goes through a central library, both for posts and for signatures.
  3. If you log out and back in it should reset it all.
  4. That is my understanding of their TOS at least. If you are unsure, you can always contact them. At the end of the day...it's doubtful Google is going to use all their vast resources to come after a modification author for a bulletin board software. If we provided the functionality out of the box, that chance would be higher, assuming my understanding of their terms of service is accurate.
  5. It wasn't sent when the announcement was made, it was just delayed, so you received the email now. I'm sure shortly after CCS is "announced" officially, an email will be sent as well.
  6. Because Google Analytics license agreement does not allow it. They don't allow any other software to "generate" the analytics code from pieces of data (such as the id solely). Best we could do is give you a textarea to put in the entire JS they provide, but if we did that, why not just edit your skin?
  7. Why does every setting have to have 87 other settings to control that first setting in your mind? :P
  8. Please note the forum rules at the top of this page. This "feedback" forum is designed for customers to discuss the features and capabilities of IPB, and provide suggestions on how to make it better. What you require is technical support, which must go through either the ticket system (for official support), or our peer to peer forums, which are only accessible to active license holders. You will need to get in touch with the person who owns the license and get their credentials, or have them submit a ticket directly. Note that for the future, you can have that license holder add you as an alternate contact on their account, which would allow you to submit tickets and access the peer to peer forums here yourself, without needing their credentials. We can help the license holder set that up. Once the ticket is submitted we will be happy to assist.
  9. In your first sentences you mention how there are numerous suggestions and everyone wanting it one way or the other, and then talking about an option for two separate headers. Then you go on to say it needs to hurry up and be released. Development takes time. ;)
  10. That is the default option in IPB, however it causes increased locking to the topics table, a table that is hit on almost every page load already. Updating views on a delayed basis relieves a lot of SQL "pressure".
  11. You need to use the client area for support. Most users have reported much better performance with 3.0.2 as a whole, so there is likely something isolated to your installation we'd need to investigate.
  12. Not that I know why it really matters, but... $sess_id = md5( uniqid( microtime() ) ); admin/applications/core/modules_admin/login/manualResolver.php
  13. There will only be a value under that column for files that have out of date strings - you would probably want to do this for each file that you see a number in that column.
  14. Ok, let's get rid of the fear-tactics being used in this topic ok? There is no inherent security risk in the way the ACP is managed now. As someone else already pointed out, it has been this way since 1.3, and I assure you - if there was a problem, it would be found and fixed by now. Using a cookie to validate the session proved LESS secure. If an XSS attack somehow gets through, an attacker can then just fix their cookie and reach your ACP. Presently, a secure session id is used, which of course can't be known unless you share it remotely with a user. We mitigate any links to external resources through the ACP (i.e. if you view a member who links to an offsite avatar, you actually go through a special local script on the public side that looks up the avatar, to try to prevent you referrer URL being passed), though it's not always 100% possible to stop this. For this reason, we also by default match your IP address. Unless you actually go edit a file to disable this, you're fine. On a local environment where everyone's IP address is the same, you have bigger issues (as in no one can use the site). That's what the "Match x-forwarded-for" setting is for, at which point your IP addresses are no longer the same, and the ACP then does not suffer from the issue Wolfie is suggesting. Why "would it be nice if there was something that would help to make it a little bit tighter"? Can I ask you this - how many times has your ACP been hacked through someone getting your ACP session ID? If it's 0, then why does it need to be tighter? Let's worry about real issues here, instead of non-issues. :) This, I'd say, is presently a non-issue.
  15. You can find out of date phrases on a per-file basis, but not globally presently (unless I'm missing something - does happen from time to time).
  16. Please submit a ticket to the support department for technical support.
  17. You can use the img tag to link to remote emoticons, or you could attach an image to a post. I think that's sufficient myself. This sounds like unnecessary bloat to me.
  18. The lofi skin was intended to be a NOT fully-functional skin. Basically, it was designed to give you access to the basics so you can quickly check over your site or read/post topics while on the go. If you want access to all the features, why not just use the full skin? That said, Rikki has been doing some work on the lofi skin lately to update it significantly, as I understand it. No idea when or if his work will make it into the main branch though.
  19. For those wondering, the resources article is slightly out of date now that 3.0.2 was released. In 3.0.1 we had forums_search_main and forums_search_delta, but in doing so there was no way to search just posts or just topics, so the index had to be split into 2 (4, once you factor in the deltas). I will update the resource article as soon as I get a chance. @.om - Sphinx is finding your topics and posts (the first command gives this): collected 437258 docs, 337.2 MB collected 0 attr values sorted 3.7 Mvalues, 100.0% done sorted 49.8 Mhits, 100.0% done total 437258 docs, 337175013 bytes total 81.729 sec, 4125540.74 bytes/sec, 5350.12 docs/sec ... indexing index 'forums_search_topics_main'... collected 113018 docs, 4.2 MB collected 0 attr values sorted 1.1 Mvalues, 100.0% done sorted 0.7 Mhits, 100.0% done total 113018 docs, 4242924 bytes total 9.865 sec, 430083.90 bytes/sec, 11456.07 docs/sec indexing index 'forums_search_posts_main'... When you just ran the main process, there will be nothing in the delta (since all the topics and posts are already indexed). Did you try to run a search afterwards? You should probably submit a ticket if you're getting no results at that point.
  20. If there's a bug report open for the issue reply to the bug report. Otherwise, I really would submit a ticket. If others are not experiencing the problem, it's a support issue. I haven't heard anything about the editor breaking, outside of the issue we already fixed with the emoticons panel.
  21. Post icons are not displayed in the forum listing in 3.0.x.
  22. I will see if someone can post the CSS changes
  23. Not sure I follow. If you don't want to receive email notifications, you can go to your settings and elect not to receive updates from the administrator in your email settings. http://forums.invisionpower.com/index.php?app=core&module=usercp
  24. There is certainly a chance. :)
  25. bfarber

    Spam service

    Standard licenses pay $25 every 6 months for access to technical support, updates, and additional services we offer or may offer in the future. Business licenses pay $50 every 6 months for the same. Technical support is given higher priority and has a shorter response guarantee. Perpetual licenses pay $30 per year for access to technical support only. Updates are included in their license whether they have technical support available or not. Lifetime licenses receive technical support and updates at no additional recurring cost beyond their original license purchase. As perpetual and lifetime licenses are no longer sold, it's irrelevant what the original cost was. That's not factored into future services that weren't available when the licenses were sold.
×
×
  • Create New...