Jump to content

Matt

Management
 View Profile  See their activity

  • Posts

    70,143

  • Joined

  • Last visited

  • Days Won

    649

 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 Matt

  1. Matt
    twoStep_activation isn't a standard column, so I'm unsure what the default value is on that. It might be easily fixed by editing core_members in PhpMyAdmin or similar to ensure the table column has a default value (such as NULL if it's a VARCHAR, or 0 if it's an INT).
  2. Matt
    To be clear, I'm not assigning blame; we create enough of our own bugs 🙂 but it is a working reality that a portion of our support volume is caused by code that is not ours. We have added tools to speed up the debugging but it's not always clear that a third party app/hook is the problem. There's a lot we can do of course but our problem is just people-hours. We make a loss on the marketplace currently when you factor in battling fraud, chargebacks, as well as debugging support issues. We are OK with that, but it does mean that we do not have a lot of resources to put into it beyond what we already do. I'm also not entirely convinced there's a pool of younger newer coders who would be willing to learn our framework and develop modifications. The problem isn't so much that people are leaving the marketplace (life changes, etc), it's that there's fewer to replace them. Part of the barrier is the cost of course, and I do recognise that but also PHP isn't a "cool" language anymore. Most developers are learning javascript (node, react, etc). This is why our future efforts are in building APIs, events and triggers that JS languages can take advantage of.
  3. Matt
    No dates planned, no. 🙂
  4. Matt
    Bad for SEO, bad for screen readers, bad for visual clutter, not really a "thing" with modern community platforms.
  5. Matt
    I do not think that is a fair assessment. We bear the support burden when a third party item has a bug. We are the first point of contact when a customer's community throws an error. To help reduce this burden, we do review submissions before they are published. It helps, but we still get tickets daily that are caused by third party items. This is the nature of code, it breaks sometimes. Free development licences have been discussed before and we could not formulate a fair plan without effectively giving away copies of the software to anyone who was thinking about creating a plugin or theme. We could consider a new model where we take 30% of sales, but do more to help authors by giving out free licenses, etc but we really want to meddle less in what you do, not tighten the rules further and take a bigger cut to offset the losses on license sales, etc. Technology marches on. We are investing time into developing forward thinking architecture that marketplace authors can leverage, such as GraphQL, new workflows based around triggers and events. These changes mean much less code overloading and more API use which will be upgrade resistant. We have always strived to help marketplace authors both with development and marketing of their products. If you look at all of our peers, not one of them has invested as much time and money into developing systems third parties can take advantage of. Marketplace sales are still very strong. There are still gaps in what we offer that marketplace authors can take advantage of. Our feedback forum is open to read and a great place to start when looking for ideas.
  6. Matt
    Which version are you currently using? I've just checked most tables with a member ID, and they are already bigint(20).
  7. Matt
    You can ignore the support tool warning. We will revue member ID columns and increase to bigint where they are not already.
  8. Matt
    I will take a look Monday.
  9. Matt
    We have 9 different IP addresses in our database tied to your account. Banning one of them probably won't make any material difference. 🙂 We have added a ticket to investigate an API endpoint that can take an email address or IP address and tell you if it's banned or not. There is no timeline on when this will be available, but we are listening.
  10. Matt
    Thanks OpenType. We do review our processes to ensure they are compliant. We will continue to do so and appreciate this topic. 🙂
  11. Matt
    It will be cloud only because most of the functionality is in the cloud. It uses Node, React, Redis, SQS and a proprietary command runner system we built on AWS. The community code is very lightweight
  12. Matt
    Well that’s just silly.
  13. Matt
    I meant the first 42 seconds of every The Weekend songs.
  14. Matt
    I can play the first 42 seconds of most Metallica songs.
  15. Matt
    Even if it meant it was almost impossible to theme?
  16. Matt
    So CSS wasn't the speed issue?
  17. Matt
    We're not Xenforo. It'll be quicker than that.
  18. Matt
    As per Ehren, we're exploring ways to make efficiency savings in the 4.x series, but any large framework changes will need to be in 5.x given the scale, scope and destructiveness of those changes.
  19. Matt
    I think most agree that the bureaucracy surrounding GDPR is silly (cookie pop-ups, accept T&S, etc, etc) although the core message of protecting personal information is good. The embed notice is something we already have on our list but we don't have a release date for it at this time.
  20. Matt
    Why would you want to disable storing the IP address completely? We need to store it for a short time for authentication purposes and to track abuse. We do have a feature that removes IP addresses from the database after a set period of days/weeks (ACP > Members > Profiles > Profile Settings) You could set this to a low number, say 7 days. The internet is based upon recognising IP addresses, for complex applications to work and be trusted, we do need to store them for at least a short amount of time. I am not a lawyer, but we work with many GDPR/privacy focused EU brands that accept IP addresses to be stored for the purpose of the application.
  21. Matt
  22. Matt
    License key checks should now process. Apologies for the delay in getting this issue fixed.
  23. Matt
    Thanks for your patience. We're working on this right now.
  24. Matt
    Hi all, Just a note to say that the October developer's blog is out now. It has a little information about our holiday release schedule and a new developer working with us!
  25. Matt
    More information about "Development update for October 2022"
    Welcome to our October developer's update! After a frantic few months of working on the PHP8 transition, we made it across the line with our November release (4.7.4), which requires PHP8 as the minimum version. Reminder: Invision Community 4.7.4 will disable plugins and applications that are not compatible with PHP8, and the only way to re-enable them is to upload a new version. Hopefully, you've had time to get your apps updated and through our review system. Thank you again for your patience throughout this process. The next big change will be PHP8.2, which changes how DateTime is overloaded, but that's a headache for 2023. Make sure you use PHP8 with your local development environments and set your IDE to PHP8 if it has this feature. If you need a refresher on the new functionality that comes with PHP8, then I recommend this blog or this video. Impacting Code Changes We've been very careful to avoid adjusting any parameter signatures this month, and we will endeavour to get you plenty of notice if we need to change things on a central method. The main change to look out for this month is the change to IPS\<app>\extensions\core\ContentRouter /** * @brief Can be shown in similar content */ public $similarContent = TRUE; We added a public method variable to note if this content type can be used in the similar content widget. This change fixes a bug where some content types, like Commerce packages, appeared in the widget but with incompatible metadata. Holiday Release Schedule It's that time of year when we start planning releases around the Thanksgiving and Christmas holidays. We try and avoid larger releases at this point in the year to reduce the stress levels on our support and development teams. No one wants a crisis during what should be a relaxing time with family and friends. The current schedule looks like this: 2 November: November release (4.7.4) First week of December: Smaller bug-fixing release (4.7.5) Early January: Patches or a very focused bug-fixing release (4.7.5.1/4.7.6) February: Full monthly releases as usual. Deprecations This month, we removed the older guest page caching. Those looking for a better replacement are having success with a free plan from Cloudflare. We also removed the Facebook promotion tool as Facebook keeps raising the bar for approval, and we want to focus on a Zapier replacement coming soon. Finally, we also removed Vigilink, which no longer works. Other News The November release features commits from @HeadStand, who is working with us part-time to chew through the backlog and work on feature improvements. She is a coding machine and has filled my inbox with GitHub pull request notifications which I'm very happy to receive! That's all for this month, happy developing!
Invision Community © 2024 IPS, Inc.
×
×
  • Create New...