WordPress I deployed on SAE is Version 3.9, but wordpress4sae is 3.4 In the SAE app store, although there are indeed many improvements in Version 3.9, many modifications need to be made when deployed on SAE, and some plug-ins also need to be modified. Today, a netizen asked me a previous mailbox plug-in question, I just want to write down the solution. If I remember the other improvements in the future, I will only talk about the modification of the WP mail stmp plug-in today.
I believe that many wper want their websites to interact with netizens in real time and send comments to emails in a timely manner. The WP mail stmp plug-in is powerful enough to satisfy most users. This plug-in is easy to configure and can be used immediately after the plug-in is configured. However, some users still cannot use the configuration correctly. I was one of them at the beginning, which is indeed a headache. The problem I encountered at that time could not connect to the mailbox server problem, then on the class-smtp.php
/* $ This-> smtp_conn = @ stream_socket_client ($ host. ":". $ port, $ errno, $ errstr, $ timeout, stream_client_connect, $ socket_context); * // pory modifies the email service, $ this-> smtp_conn = @ fsockopen ($ host, $ port, $ errno, $ errstr, $ timeout); // pory modifies the email service. The default version is shown in the preceding figure.
In the above modification, only
The stream_socket_client function is changed to the fsockopen function. Both functions are the same, and the network socket connection is enabled. In essence, only some spaces have disabled one function, and most spaces have disabled the fsockopen function. However, Sae is strange that stream_socket_client is disabled. If there is a mailbox problem in the future, you can check whether the replacement attempts are valid for these two functions. Different spaces are different.
SAE + WordPress mailbox problems, WP mail stmp plug-in configuration but invalid Solution