Flitterkill

+Clients
  • Content count

    795
  • Joined

  • Last visited

1 Follower

About Flitterkill

  • Rank
    Spam Happy

IPS Marketplace

  • Resources Contributor Total file submissions: 6

Profile Information

  • Gender

Recent Profile Visitors

17,853 profile views
  1. PHP7 Compatibility

    @TheSonic That does seem to be the problem. The libraries they use to thoroughly test the hell out of the thing are reliant on PHP 5 something so until those things get pushed to PHP 7 compatibility they are unwilling to risk PHP 7 patches. However, if someone can patch stuff for HTMLPurifier that fixes PHP 7 problems *AND* are backwards compatible with the current PHP 5 stuff they use to test then they are all for it.  
  2. PHP7 Compatibility

    HTMLPurifier will get updated - many of you are misreading the situation. It may not be soon but it isn't as if the dev (and others contributing code) have stopped developing it. The last commit was two days ago. The problem is apparently with libraries they use to *TEST* HTMLPurifier. That is a big difference from libraries needed for HTMLPurifier to work. And if any patches someone makes are back compatible with PHP 5.x he'll gladly merge them in.
  3. This was just brought up in contributor chat again and I jumped on through to a linked topic which linked back to a long dead bug report/feature request: This never went anywhere, or at least we never heard back on why you have locked down the locations to header, footer, sidebar. Of course we can move those around somewhat but adding in new locations altogether seems to be out of the picture without some hard coding around it. More work but doable for plugins/apps; probably not so much for theme authors who I would argue would get the most use out of adding in new/unique locations for widgets. @Matt stated in that report that "We currently don't allow custom widget areas because we feel it would lead to inconsistency between themes?" The bug report died about a year ago with a mention that it would be brought up internally. So, a few questions: 1) What is the problem with inconsistency between themes? I mean, if you expect all the themes to be mostly CSS changes and are trying to keep the IPS suite looking like "the IPS suite"  I guess I get it... but with the whole idea of the core separate from the apps and the underlying system changes why lock us down like that? So some themes have more/different widget areas - isn't that the point of themes? 2) Are there any technical reasons why that if statement (if widget not flagged header, footer, sidebar then err) exists? Could it just be removed to let us run wild with locations? I see zero drawbacks if that is the case and I guarantee all theme authors would agree. Here's Tom's final response in that report: Comments? Answers?
  4. We cant search 3 letters/less. REALLY?

    Just a heads up that a recent bug fix has caused some problems in that if you are using InnoDB for your posts table and are setting the InnoDB character search variable to determine the minimum number of characters to search that variable is ignored, as shown above, IPS now reads the MyIsam ft_min_word_len variable *exclusively*  to determine the minimum search length. So if you are running with Inno you have to set both the Inno and MyIsam vars - one to make IPS work, the other so your DB works. No, I have no idea why after telling everyone that InnoDB is the way to go for full text searching and so on why they are now pulling the MyIsam variable directly instead of accounting for both or letting us choose. Also, it's possible on upgrading that the posts table gets reverted to MyIsam even if you had it set to InnoDB. Bug report submitted a few weeks back. That, of course, will cause problems as well...
  5. A few questions from a user

      I'll just leave this here...
  6. Let's vote for Post Preview feature

    I agree with @Lindy that overall this is mainly a confidence issue. Once people get a few weeks of posting under their belt the need/want will probably drop away. However - marketplace to the rescue: The nice part of this is that it is just a pop-up modal so no new page reload. This should solve most people's needs. Be sure to rep the mod author if it helps!
  7. It actually seems there are no permissions to be set in Member Groups for Commerce at all. It is as you say; if you are registered (Member or higher) then you can access Support but guests cannot. I can see where IPS is coming from in doing this but your use-case makes a lot of sense as well. Especially if someone just got the Core and Commerce they would have no way of working with guest (pre-sale) inquiries outside of a generic email account (or creating multiple email accounts) - which bypasses the nice Support system already in place. I think @Mark is the primary for Commerce stuff so I'll tag him to have him maybe pop his head in here. Allowing guests to access Support shouldn't be too hard of a change to make but it is a feature request at this point. Sorry.  
  8. Upgrade Now Front End Message

    Tracy Perry brings up a good idea. A flagged, permanent-until-upgraded notification would do the trick as well. I would combine both the front end message (but dismiss-able) with the perma-notification. You could even css the critical notification and wrap it in a red background, etc. @someone.... When you say the message is for administrators only is that for the single distinct user group "Administrators" or for any/all that have ACP access?
  9. We cant search 3 letters/less. REALLY?

    I'd be glad to look if you want. PM me.
  10. We cant search 3 letters/less. REALLY?

    Agree not working on this IPS site. It's quite possible they haven't updated this site. @Lindy All I can say is I *know* the bug cited above has been patched (looked at the source file myself) and on a stock 4.1.3.1 install I can search three char words just fine. For your own site hit the support tool button in the ACP to drop and rebuild all the caches and if it persists afterwards (taking into account all the MySql stop words and so on) submit a support request.    
  11. We cant search 3 letters/less. REALLY?

    Probably should submit a support request then; something else might be going on. I can confirm three char works on a stock 4.1.3.1 install. Just tested again to be sure.
  12. We cant search 3 letters/less. REALLY?

    See the above. It was a bug. Fixed in 4.1.3.1. If you are still on 4.1.2 or less it will stick to 4 characters or more.
  13. We cant search 3 letters/less. REALLY?

    I don't think you'll ever get two character searching available on IPS cloud-hosted sites. But, if your IPS hosted site is on 4.0 and the db tables are innodb three character searches should be default. You'll need to get a response from staff to confirm though. As to why you would not be able to get two character searches that's because it requires changing a default db configuration and adds addition file size and server load to the server and in a shared hosting environment that impacts everyone. It's possible down the line that IPS might start spinning out each IPS-hosted site as individual Amazon/whatever hosted process in which case they could probably add an option for stuff like two char searching for an additional fee, etc. but again, that's stuff for IPS to decide/do/etc...
  14. We cant search 3 letters/less. REALLY?

    It's a minor bug that will get patched when they update this site and everyone will have it when they do the next release. If you have to have it now for your site see my fix here: And yes, three character *and* two character searches (if your DB is configured properly) work just fine.