Jump to content

Marc

Invision Community Team
  • Posts

    14,940
  • Joined

  • Last visited

  • Days Won

    260

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Forums

Events

Store

Gallery

Posts posted by Marc

  1. 6 hours ago, Johno2518 said:

    I would think this would be of significant value considering this is one reason Invision doesn't support the product on Windows/IIS - understandable you don't want to support a myriad of different platforms and configurations which is one thing containers address. I'd also think this add's a ton of value to the cloud offering.

    As with the above assumption on how our cloud platform works, this is also incorrect. We dont actually support any environment. We support the product, and state the following

    Quote

    Our software works with all modern web servers (Apache, nginx, lighttpd, etc.) that can support secure versions of PHP (with GD, mbstring and all default extensions) and MySQL.

    The added line related to windows server is in absolutely no way at all related to how its set up. Its related to the fact we have seen on many occasions issues when people are using IIS. Usually surrounding things like permissions etc, but often related to the underlying server setup. Not necessarily just IIS. 

    Quote

    I'd also think this add's a ton of value to the cloud offering.

    I have to admit to being a little confused as to why you believe this to be the case? We don't "spin up" a new box when someone creates a new cloud instance. Its essentially just an account. While it will have it owns files (things that people have uploaded) and its own data, it doesn't necessarily mean it will have its own instance of the software. You are thinking of this in terms of an installation that is done on self hosted, and cloud just doesn't work in that manner in any way. 

    6 hours ago, Johno2518 said:

    When you say "vision of the platform" - part of that is how to modernise the deployment and upgrade/rollback experience and it would be good to know what options have been considered and why certain things have been ruled out because it gives us insight into what Invision is thinking about it's product and services.

    We are not likely to get into the decisions made on a daily basis for each items we decide on. Its simply not feesable. We have too many things we make decisions on daily. However I can put this into some context for you by asking you a simple question. If in your job, whatever that happens to be, you could do something that would add nothing at all in terms of value as a company. Would you do it? The reality is, the 'self-hosted' product is a shrinking market. We have made changes to the licensing to ensure that its viable for the immediate future for our customers. But we need to be selective over what we spend development time on, and things such as these are not really of huge value.

    Note again, it's not a decision that I would personally make. However I'm giving you the reasoning why its probably unlikely. 

  2. This is an application you already own. If you arent seeing it, go to System->Site Features->Applications and click install next to downloads. If you dont see the application there, you need to upload a fresh set of files from your client area, and you will see it once you have done this

  3. 11 minutes ago, Lemarinel Sébastien said:

    So I found a way to fix this problem. And I think Invision shoult add something in the configuration of the SMTP.

     

    I'm using the SMTP from Protonmail with SSL. For SSL and TLS Protonmail support only AUTH PLAIN (not AUTH LOGIN). But Invision use  only AUTH LOGIN and doesn't support AUTH PLAIN.

    So when I configure the SMTP I see the following message:

    535 5.7.8 Error: authentication failed: Invalid authentication mechanism

    To fix this In the file

    system/Email/Outgoing/Smtp.php

    I replaced this part:

    if ( $this->smtpUser )
    {
        $responseCode = $this->_sendCommand( 'AUTH LOGIN', 334 );
        $responseCode = $this->_sendCommand( base64_encode( $this->smtpUser ), 334 );
        $responseCode = $this->_sendCommand( base64_encode( $this->smtpPass ), 235 );
    }

    With this:

    if ( $this->smtpUser )
    {
        $responseCode = $this->_sendCommand( 'AUTH PLAIN', 334 );
        $responseCode = $this->_sendCommand( base64_encode("\0" . $this->smtpUser . "\0" . $this->smtpPass), 235);
    }

    And it's working. I think Invision need to add an option in the SMTP configuration to allow user to choose between AUTH PLAN or AUTH LOGIN or automatically detect the options available.

    Regards

    Please feel free to post his as a suggestion in our feedback area

×
×
  • Create New...