Leaderboard

Blesta has required this since 3.0. When we decided to require it, as with all requirements, we gave it considerable thought. I don't see this changing anytime soon. Mailparse is a good library and any reputable hosting provider shouldn't have any issue enabling it. It works well, and it's efficient.

Never mind, I enable this by modifying solusvm_api.php and now password protection is working. Thanks to Open-source

Hi folks, Couldn't find this reported, however it seems there's a bit of an issue when attempting to install 4.0.0 using PHP 7. It appears there's a syntax error when taking into account MySQL Ports I've configured my development environment to use MySQL on port 13306 and entered the host as 127.0.0.1:13306 Installation works perfectly on PHP 5.6.23 (via FPM & CLI), however via PHP 7.0.18 it throws the following error: SQLSTATE[HY000] [2002] Failed to parse address "127.0.0.1:13306:3306" Changing config.php to the host as 127.0.0.1 and port 13306 does not remedy this issue, as such it appears that I'm unable to use PHP 7.0 with MySQL from a fresh install. Oddly enough an upgrade, admittedly on a slightly older php7 version, worked without issue. Note: it was installed using 127.0.0.1:13306 in the host string, as there was no separate port, despite the configuration having a port option. The exception is occurring on line 74 of core/ServiceProviders/MinphpBridge.php (the new PDO connection setup). var_dump($dbInfo); shows the following data: array(10) { ["driver"]=> string(5) "mysql" ["host"]=> string(9) "127.0.0.1" ["port"]=> string(5) "13306" ["database"]=> string(6) "blesta" ["user"]=> string(6) "blesta" ["pass"]=> string(6) "blesta" ["persistent"]=> bool(false) ["charset_query"]=> string(16) "SET NAMES 'utf8'" ["sqlmode_query"]=> string(26) "SET sql_mode='TRADITIONAL'" ["options"]=> array(0) { } } I've confirmed via debug that the data being input to new PDO is: string(40) "mysql:dbname=blesta;host=127.0.0.1:13306" Changing lines 64 to 74 from: $connection = new PDO( $dbInfo['driver'] . ':dbname=' . $dbInfo['database'] . ';host=' . $dbInfo['host'] . ( isset($dbInfo['port']) ? ':' . $dbInfo['port'] : '' ), $dbInfo['user'], $dbInfo['pass'], $options ); to $connection = new PDO( $dbInfo['driver'] . ':dbname=' . $dbInfo['database'] . ';host=' . $dbInfo['host'] . ( isset($dbInfo['port']) ? ';port=' . $dbInfo['port'] : '' ), $dbInfo['user'], $dbInfo['pass'], $options ); Resolves the issue, and the site is now operational. This fix obviously relies on the port being explicitly set, so having a field to fill in that port is still required. Edit: looks like it worked doing the upgrade because my other upgrade was on my other laptop, that runs mysql on 3306...

this is not downgrade or upgrade, is term change , client can change term via service tabs

Is there a reason that the providers give as to why it isn't enabled or why they can't enable it? I know in the past I ran into providers who didn't offer this extension. My guess was due to higher resource usage that that module could cause. Regardless, at this point I don't think there is a good reason for a reputable shared hosting provider to not have this. With cloud linux they can even more strictly control your resource usage if resource usage was the issue. Do you know of anything that can replace mailparse. I had looked many times and never found anything that worked as well as mailparse did.

Correct when the next monthly invoice is due he will be billed the yearly plan for the year.

SHare your solution for others ...

If your hosting provider does not offer Mailparse, then find a different one. It is standard among good hosting providers. -Adam

Any providers whose does not do this properly are garbage or simply "winging" their shared setups. Instead of blaming Blesta blame the incompetence providers whose don't enable it for you.

Ethics should always get "first" even when your risk is at stake. For example if your having an absurd amount of "bad" orders it not because it ALWAYS from country xyz. But rather your poor anti fraud filtering means. Not because that country is responsible for it but rather it YOURS responsibly. As other says a country filter is just a "speed bump" if someone want to ruin your business/rep they WILL. However losing legitimate orders is WAY easier than adding so many "speed bumps". At the end of the day it your business responsibly to use NON discriminating means to filter out fraudulent orders not countries.

regarding your question, you can block the ips fro the whole countries with htaccess if you want, but just to note also, frauders use almost of times proxies, you can reach what you want by this online tool https://www.countryipblocks.net/country_selection.php and you can block some sort of proxies by this .htaccess code RewriteEngine on RewriteCond %{HTTP:VIA} !^$ [OR] RewriteCond %{HTTP:FORWARDED} !^$ [OR] RewriteCond %{HTTP:USERAGENT_VIA} !^$ [OR] RewriteCond %{HTTP:X_FORWARDED_FOR} !^$ [OR] RewriteCond %{HTTP:PROXY_CONNECTION} !^$ [OR] RewriteCond %{HTTP:XPROXY_CONNECTION} !^$ [OR] RewriteCond %{HTTP:HTTP_PC_REMOTE_ADDR} !^$ [OR] RewriteCond %{HTTP:HTTP_CLIENT_IP} !^$ RewriteRule ^(.*)$ - [F]

I believe they said it was in was in the making and would be out with the new release or something of that effect.

is better to add fraud detect system rather than block countries ...

Looks like the functionality changed for ignoring the module. I sent you an email with details. I did find a workaround for now.

I think because we started using namespaces in 4.0, ApiGen organizes everything differently. Most classes are under "None", see http://source-docs.blesta.com/class-Upload.html It's possible some things are still missing, but it's also possible they are just in a different location relative to 3.6 http://source-docs.blesta.com/3.6/class-Upload.html

Blesta aka Phillips Data is the maker for Blesta and minPHP. Please provide documentation to minPHP. If source-docs.blesta.com is not the right place for minPHP then let everyone one where the new place should be.

Your not using cPanel/WHM correctly. Login to WHM Select Module Install Select PHP pecl Then search for mailparse Install I highly recommend you use CloudLinux with cPanel/WHM or even cPanel's MulitPHP Manager. https://documentation.cpanel.net/display/ALD/MultiPHP+Manager+for+WHM Either solution allows you have cPanel accounts use different version of PHP. This is great for legacy applications that require specific versions of PHP or specialized setups. -Adam