We have two sites, each with a copy of aMember Pro, being hosted with Network Solutions on a shared server. Two days ago both aMember portions of the site began to fail with an error: "Warning: base64_decode() has been disabled for security reasons in /(directory path...)/amember/rconfig.inc.php(19) : eval()'d code on line 1" aMember could not function at all. amember Tech Support told me to have Network Solutions enable base64_decode() function. I opened a trouble ticket with Network Solutions. They responded with the information at the end of this post. I followed their instructions by creating a php.ini file using their content and placed it in our cgi-bin directory. aMember again works correctly on both sites. Network Solutions gave no warning they were going to block base64 functions so I am posting this in the hope of helping other aMember users who discover a similar problem. The info from Network Solutions follows... Your PHP is erroring because your code uses a base64 decode that we have blocked for security purposes. You can bypass the block, however, your request can only be accomplished via customizing PHP on your hosting package. Default values for PHP can be modified by use of the php.ini file that can be created in the cgi-bin. Modifications to the php.ini file are not supported by Network Solutions technical support. You may make changes to the php.ini file and upload it to your /cgi-bin folder, but any changes to the php.ini file that are detrimental to the server's performance may result in a suspension of your hosting account. When creating your php.ini file we recommend using the following values, and adding or changing any of the values from there. session.save_path = /data/tmp upload_tmp_dir = /data/tmp asp_tags = On register_globals = On safe_mode = Off upload_max_filesize = 25M post_max_size = 25M output_buffering = 1024 mime_magic.magicfile = /usr/share/misc/file/magic.mime memory_limit = 16M include_path = .:/usr/services/vux/lib/php disable_functions = shell_exec,passthru,exec,system,pcntl_exec allow_url_include = 0 allow_url_fopen = 0 extension_dir = /usr/services/vux/php5/lib/php/extensions extension = suhosin.so zend_extension = /usr/services/vux/php5/lib/php/extensions/ioncube_loader_lin_5.2_real.so zend_extension = /usr/services/vux/php5/lib/php/extensions/ZendOptimizer_real.so suhosin.simulation = On suhosin.executor.eval.blacklist = base64_decode, popen suhosin.log.syslog.facility = 511 If you have any other questions about this issue, please contact our Support Center and refer to Service Request 1-480038738 and a specialist will be happy to further assist you and ensure that we completely resolve your issue as quickly as possible. Thank You, Tom Technical Services Network Solutions US/Can: 1.866.391.4357 International: 1.570.708.8788
Evidently NOT Solved? A follow-up on the situation... After further examination I discover that aMember is having problems on the Administration (Control Panel) side as well as the Member side. I have a trouble ticket in with aMember but I have a feeling I am going to have to move my domains to a host that does not block base64 functions.
SOLVED by aMember Tech Support aMember Tech Support has risen to the challenge again! They went in and made adjustments to aMember Pro and the sites are now functioning properly! I am pleased and impressed with this organization.