It is possible those using the quick installer, or other aspects of ocPortal that use FTP connections may receive strange error messages relating to FTP commands that don't look like real error messages.
One example is:
ftp_put() [function.ftp-put]: Connecting to port 34031
This illustrates ocPortal failed to upload a file ('ftp_put') but the attached error message makes no sense at all.
How did this happen?
The reason for this is PHP's FTP support is rather poor on occasions, unable to generate accurate error messages. In this example 'Connecting to port 34031' is actually a status message for the FTP connection, routinely put out, and PHP misinterprets it and relays it as the error message that caused the failure.
How do I fix it?
There is no clear fix as PHP was not able to relay an appropriate error message.
Here are some potential solutions…
You should try refreshing to see if it works a second time around (it could have been a random anomaly).
Consider whether the FTP connection settings you entered were corrected. In the example above it is likely there is actually no FTP server running where it was specified, as the last status message (which PHP considered 'the error') was one prior to any connection being confirmed as established.
If you get this when installing, consider using the manual installer.
If you have a SuEXEC configuration or Windows server then you have no need at all for an FTP server to be running.
… otherwise you can avoid the need for an FTP server by setting extra permissions. Try saying you don't need FTP, noting the error message you see, setting extra 777 directory permissions (full write permissions) accordingly, and refreshing.
Contact your web host saying your server PHP cannot connect to the FTP server (and say what FTP details you used). Ask them to give you the correct FTP details, fix the FTP server, or fix PHP FTP support.
If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.