Panormitis

I can ask another support agent again. In the meantime, I do prefer the module to retrieve the retail prices for everything (even if that seems odd). I suppose the API call names aren’t going anywhere anytime soon, so even if the module gets updated, I’ll just change PE_GetProductPrice to PE_GetRetailPrice. I would be very surprised if I’m the only one who prefers this. An option in the module settings, to choose between PE_GetProductPrice and PE_GetRetailPrice could be a nice idea though.

I know Blesta can do it. What I'm saying is that Enom support said they will send notices too, no matter what. I can't disable Enom notices, they are obligatory. The only thing I can do is at least make the prices match, for transparency. Otherwise my customers will receive renewal notices with different prices. EDIT: I can tell them "Don't send notices yourself, I have a billing software that does", but they didn't give me that option. The way they said it, implies I don't have that option.

I have asked Enom support about this and their support agent explicitly said they are obliged to send renewal domain notices, no mater what, but at least they will show to the customers the retail prices I have set. This is why I want to sync the correct prices, for transparency.

I understand that, but I don't think it's practical. When the time comes for Enom's domain renewal notices (Enom is obliged by ICANN to send them on my customers) won't the domain notices list the renewal/retail price I have set on my Enom reseller account? This is what the customer will pay, not "my cost" price. It looks a lot cleaner to me to fetch the retail prices to sync everything perfectly, than fetching "my cost" prices and rely on markup to make profit.

Hello, I have an Enom reseller account. I started using Enom domain module and I noticed when I try to sync the TLD prices, the prices retrieved are the base "my cost" prices, not the retail domain prices I have set for the customers, which I find odd. I managed to fix it so I just wanted to share my solution in case anybody finds it useful. Open file <blesta_dir>/components/modules/enom/enom.php for editing. Find: PE_GetProductPrice Replace with: PE_GetRetailPrice There should be 3 instances, on lines 185, 193 amd 198. Save the file, clear Blesta's cache directory and enjoy! I really think this should have been fixed by Blesta developers. Domain prices should be synced to the retail prices, not the base ones.

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); }