evolvewh

I was wondering if the Blesta Team or Nick @thesslstore has any update on this one?

We are too and now I'm thinking there's a bug. Will be curious to see what the Blesta team has to say.

I think your case is related to the task you mentioned and it says it was fixed in 4.0. I've noticed other syncing issues too but I couldn't figure out if they were related to the specific module or system wide.

Turn on error reporting in the config/blesta.php file to find out what the error is and then someone here will be able to help you troubleshoot further.

We're seeing this too and hope that it will move from the backlog to the next release or two.

I would like to see this too. I can't remember if there is a task for this or not but it should be there.

Has anyone added the tracking code for Google Analytics Ecommerce? We'd like to get the products, dollar totals, etc added through Tag Manager but haven't had a chance to do so yet. Does anyone have a template or suggestions? I'll be reviewing the Google documentation soon but thought I'd ask here first.

I was going to point you in the direction of the docs but the info looks a bit light about this module. https://docs.blesta.com/display/user/Enom

Is there an update about the release of the new version? Excited to get it!

Did you try re issuing your license?

That file is there for new installs and to help make sure that you don't overwrite your existing blesta.php file if you're upgrading.

Sounds good. The config/blesta.php contains all of your DB credentials and a key that will basically lock you out of the system if you don't have it so you don't want to overwrite it, the routes.php file, the .htaccess file if you have made any changes and any 3rd party plugins you may be using. Glad you had a backup!

It sounds like you replaced every file in every existing folder so it's more than likely you lost your config/blesta.php file when you 'uploaded to overwrite all existing files'. Were you able to make progress with this yet?

I've reported it to the SSL Store and they confirmed the bug too so they're looking into it. Hopefully there is a solution soon.

@Paul: Any luck duplicating this from your side?

Is there a way to make the EPP code required during checkout for a domain transfer?

Go to the page(s) you want to quick link and you'll see a star on the left side of your screen just below the menu. Click it and it'll turn solid yellow meaning you've created a quick link.

Yes, that's exactly what's going on.

I'm still not sure that I am following you all the way. The invoice showed the renewal date as 6/1/18 which is correct but it was listed as 5/24/18 under the services section on the admin side (I didn't check the clients area but I'm guessing that was the same).

There wasn't an extra invoice or line item but the renewal date itself didn't show up properly. I think there is a Blesta bug and it could be related to the other issue I've found with the SSL Store module as well.

We're using Blesta 4.0.1 w/ php7 along with the cPanel extended module from Cyandark. Pro rata is enabled and it has always worked the way it should until an order came through yesterday. The invoice generated properly with the pro rated charge but the renewal date did not update properly. It shows a renewal date of 5/24/18 instead of 6/1/18 so it was manually updated for the time being. The only thing that is new for us is php7 so I don't know if the issue lies there or elsewhere. Has anyone else exprerienced anything similar?

Is anyone else having an issue with the cron task to sync the renewal date? Ours is consistently showing the renewal date of 11 months instead of 12 for every Comodo we sell. We don't sell any other brands so I can't test to see if it's related to one brand or not.

Try this: plugins/support_manager/pipe.php file needs to have 700 permission and add the hash bang to the first line of the file. This is the hashbang we use: #!/usr/local/bin/php -q Don't forget to add the forwarder in cPanel as well.

Unless there are other country laws that I'm unaware of, it makes the most sense to add it to the existing invoice. Otherwise, as others have pointed out, the additional invoice won't be paid. I've seen the same behavior in other software as well.

I'll mention it to them if they follow up again. We don't use the module but I was trying to help others out.