panormitis

Contact your web hosting company or server administrator. Perhaps a custom php path is used or crond service is not running. cron accesses files directly, not via apache/webserver. .htaccess shouldn't matter

As Blesta indicates, example cron command, it's not necessarily correct, it's just an example to get you started configuring. You are running DirectAdmin, the path of the php binary is different. Change the part /usr/bin/php to /usr/local/bin/php In Minute text box set it as */5 not just 5. Assuming you want the cronjob to run every 5 minutes. You could also just put a single asterisk in the Minute text box, that would make the cronjob to run every minute, but it's not necessary to run that often.

Some coupons are always working, for example: COUPONFCNC provides a 20% discount every time a transaction is made (domain registration/renewal/transfer etc.). NEWCOM649 gives you a new .com domain registration for just $6.49 The Namecheap module settings could have a coupon text field that is applied in the API every time a transaction is made, or few text fields (let's say 3) for various coupons that can be configured in the settings to be applied on specific events. For example NEWCOM649 only when a new .com domain is registered. COUPONFCNC when any transaction is made that doesn't involve a new .com domain registration.

Yes Namecheap coupons can be passed to the API, check PromotionCode https://www.namecheap.com/support/api/methods/domains/create/ It can be passed also on domain renewals and domain transfers.

Any updates on this? A coupon / PromotionCode field in settings, would be nice.

This happened to me too today. The client paid manually (bank transfer) two weeks ago. I recorded the payment, the domain was included in the invoice. Date Expires was updated. Date Renews wasn't updated. And Blesta went ahead and sent an e-mail to the client "This is a notice that the domain <domain.com> has expired on 2025-02-08 and is no longer under your ownership. To re-purchase this domain, please log in at ...". This needs to be fixed, worried clients are bad for business...

I found out the solution thanks to Discord, I'm just posting it here, in case it helps others. 1. Go to the domain you want to cancel or delete & click Manage. 2. The actions you have there are: Change Auto Renewal, Renew Domain, Update Nameservers, Push to Client, Unparent and Reset Price. You don't need these for now, just click the Edit Service button in the lower right corner. 3. Now you have the actions Suspend, Cancel, Schedule Cancellation, Change Renew Date, Update Coupon. 4. You can choose to use the module or not. You could cancel the domain right away by selecting Cancel & clicking Save. 5. Afterwards the domain is placed in canceled domains, where you can delete it.

Hello, I'm using Blesta 5.9.3, I recently activated the domain manager plugin and now domain names have their own section and not appearing as services anymore. However in the past if I wanted to remove a domain name from a client, I could cancel (and delete if needed) the corresponding service. I don't see how I can do this with domain manager. How can I cancel and potentially delete a domain name of a client? I'm not asking how to delete it from the registrar, just how to cancel it and potentially remove it from the client account. The only potential solution I found is to manually edit the database, which seems like a bad idea.

On PHP 8.0/8.1 disabled functions are treated as nonexistent so a fatal error occurs. On earlier PHP versions, disabled functions raise just a warning and the script continues to work. I believe this should be addressed in Blesta, some functions could be disabled so they should be checked with function_exists() first.

Technically I guess it's not really a bug, but since a disabled function in PHP 8.1 becomes pretty much non existent, it raises a fatal error and prevents Blesta from working. So I commented out line 78 of the file ...vendors/minphp/session/src/Session.php and added another bellow it. // ini_set('session.' . $key, $value); if (function_exists('ini_set')) { ini_set('session.' . $key, $value); }

I found a temporary workaround, initially I was trying a try-catch like this: // $output = call_user_func_array('sprintf', $args); try { $output = call_user_func_array('sprintf', $args); } catch(ArgumentCountError $e) { } However it didn't work. But this did: // $output = call_user_func_array('sprintf', $args); try { $output = sprintf($args[0], $args[1], $args[2]); } catch(ArgumentCountError $e) { } EDIT: Ok the following works too, just needed a backslash ? // $output = call_user_func_array('sprintf', $args); try { $output = call_user_func_array('sprintf', $args); } catch(\ArgumentCountError $e) { }

On older php versions this would have generated just a warning, but now throws a fatal error. Uncaught Exception ArgumentCountError: "3 arguments are required, 2 given" at ...vendors/minphp/language/src/Language.php line 125 {"exception":"[object] (ArgumentCountError(code: 0): 3 arguments are required, 2 given at ...vendors/minphp/language/src/Language.php:125)"} I tried a try-catch to suppress it but didn't help. Any ideas?

Hi Joseph, Mine too. 4.3.0-b1

Thanks for the advice Tiny. I don't think it's the database anymore. Logged in users have no issues.

Reply button works just fine, only the Close button raises a jquery 401 error.

Hi Tiny, I performed some tests. On some departments of support manager, I have unchecked the "Allow only clients to open or reply to tickets", because I want also non-clients (without an account in Blesta) to create tickets via sending an e-mail. The issue only occurs on non-clients, not for everybody. If someone without an account in Blesta, visits a ticket via {update_ticket_url} he/she can't close it. A 401 jquery error is generated when clicking the Close button and the ticket remains open. However, clients with an account (they are required to log in to access the tickets) are not affected. Looks like a session issue. I have edited my first post for clarification. I didn't know it only affects users without an account.

In my case the files were overwritten correctly and the database seems ok. Perhaps there is some bug/incompatibility with PHP 7.2.8. Or perhaps the issue is occurring because I'm using reverse-proxy NGINX + Apache (I'm starting to suspect that's it).

Can I perform a clean install and import the clients/packages/services etc. Is that possible? Is there an export - import function?

Yeah, I reverted back to the original file. I only used jquery 3.3.1 for a little while

I replaced app/views/client/bootstrap/javascript/jquery.min.js with the uncompressed jquery 3.3.1. I get an error on line 9600: xhr.send( options.hasContent && options.data || null ); Any ideas?

Hi Tiny & Paul, I upgraded from Blesta 4.2 and I'm positive I overwritten all files. Actually I restored a backup and tried the upgrade twice (in case something went wrong the first time) and this issue is reproducible. I don't know if it matters, I'm using PHP 7.2.8 and on Blesta 4.2 I was using support manager pro. Now on Blesta 4.3 I have uninstalled support manager pro and using the regular support manager.

Hi lolgc1, In my case, the columns are there. Please check the attached picture.

I have upgraded to Blesta 4.3.0 I'm using support manager. On some departments I have unchecked the "Allow only clients to open or reply to tickets", because I want also non-clients (without an account in Blesta) to create tickets via sending an e-mail. If someone without an account in Blesta, visits a ticket via {update_ticket_url} he/she can't close it. A 401 jquery error is generated when clicking the Close button and the ticket remains open. If it's a client with an account, everything works normally. Looks like a session issue Please see the attached pictures

I would like to see WorldPay on blesta too.