If your site seems to not be working properly, you should first check your server's configuration settings to be sure that it meets SocialEngine's minimum requirements and is optimally configured. If you notice a server misconfiguration and would like to change the configuration settings, your hosting provider should be able to assist you.
To access the Server Information page, in your Admin Panel navigate to Stats > Server Information.
Note that depending on the version of SocialEngine you are using, it might be located in a different place than shown in the screenshot.
Sometimes you might receive an error stating that PHP has exhausted its memory. This error usually occurs when PHP tries use more memory that your server’s php.ini config file permits. This problem can be corrected by increasing the “memory_limit” directive to 64M or 128M if additional memory is required.
If you receive an error such as "'The given destination is no directory or does not exist" when uploading files even though you do have a public and a temporary directory with 777 permissions recursively on your server in the SocialEngine root directory, it could be that the PHP directive “open_basedir” is currently enabled on your website and may be interfering with SocialEngine's ability to access the /tmp directory. Please contact your hosting provider and ask them to disable this directive and see if that resolves the problem.
File uploads in version 4 are bound by the values of the PHP directives “post_max_size” and “upload_max_filesize”. By default the value these directives are set to 8MB and 2MB respectively.
If these values need to be increased, you can try adding the following to the .htaccess file in your SocialEngine root directory:
php_value post_max_size 100M
php_value upload_max_filesize 100M
The above may not work on all servers. If adding the above rules to your .htaccess file does not affect the value of your website's post_max_size and upload_max_filesize directives, please contact your hosting provider and have them increase the value of these directives for you.
If your site seems to sometimes get a blank page or content while trying to view a page, or fails when performing an action, your site might be losing connection with its database. This usually occurs if the “mysqli.reconnect” directive is disabled (OFF) on your server which can significantly increase the number of connections made to the MySQL server. If PHP loses connection to the MySQL server and this directive is disabled, PHP will throw a Fatal error, halting the scripts execution. However, because of the “interactive_timeout” and “wait_timeout” values, the database connections may continue to persist for 8 hours, as that is the default value. In the very least, this directive should be enabled in your server to prevent this problem from happening.
Great work! Please feel free to contact us if you have any questions or need further tutorials. Visit our community to have more interactions with us and other clients or third party developers. We’d love to see you there!