Leaderboard

We did discuss that, but it made more sense to leave it on the report page. If we were to create a client profile account action, it would probably just link to the report page and pre-fill the fields to generate for the client.

Awh thanks you! Let's hope this time for good.

Good to see you back and kicking! Welcome back!

You can certainly find value without paying a premium price, but there's always a tradeoff, and that tends to be quality and robustness. If car A works for you in the context you need it to, then that's perfect! But things are not always what they seem, especially the things you can't see and they know you can't see. From my experience, based on your example, you buy Car A but it will perform like Car C, and when you take it to a mechanic they look it over and tell you, "This is actually a motorcycle, not a car."

Return values for Module::renewService($package, $service, $parent_package = null, $parent_service = null) are either null or a set of meta fields (an array) containing the key value pairs "key", "value", and "encrypted": public function renewService($package, $service, $parent_package = null, $parent_service = null) { // Attempt to perform the renewal $renewal = ...; $service_fields = $this->serviceFieldsToObject($service->fields); if (there is an error) { // Error $this->Input->setErrors(['error' => ['type' => 'The service could not be renewed because of this error!']]); } else { // Success, the service was renewed. Update and return the meta fields return [ [ 'key' => 'mymodule_renew_email', 'value' => $service_fields->mymodule_renew_email, 'encrypted' => 0 ], [ 'key' => 'mymodule_expiry_date', 'value' => $renewal->expiry_date, 'encrypted' => 0 ] ]; } // Return null to not change any meta fields return null; }

I have had to spend countless hours fixing shotty website work done by freelancers and single-developer contractors. While you can find good freelancers from time to time, this is unlikely. Remember you get what you pay for. That said, you should probably break your website construction into two: design, and functionality. First have someone create the design you want, then have someone else integrate it and make it work.

Not currently. I recommend having a support department for GDPR requests specifically, and then staff can generate and attach it to the ticket. If there is demand, we will consider adding self-service so that clients can request and get within the client area, along with a setting so admins can enable it or not. Companies may decide to only grant requests to EU customers, or all customers, or no customers.

Unless you know the designer in person always get the files first or use a middleman. I hope you get a nice design mate sorted.

Ahh I see what you meant now absolutely. That how one of them did much work on a site and beside minor errors it was "ready" and thus he said he would be fixing it while I make the payment. Then 30 minutes after I made said payment I got the files and there was like 2 "odd balls" and he gave it the final "whack" it needed.

A package group can contain both restricted and non-restricted packages, and the group itself isn't restricted or not restricted. I would suggest mixing restricted and non-restricted packages in the same groups. There is a known bug with this right now though, where the restricted packages can mess up the order form, causing all packages in a package group to be displayed incorrectly. Should be resolved in beta 2 this week.

If you are using funnels and collecting order amounts to pass into Google Analytics, then your embed code may look a little different, and you'd want to make user of variables and possibly page conditions to set the right values. I'll have to look at an example of this using funnels and see if it's possible to provide a generic example that'll work. If you are not using funnels, and just want Google Analytics to appear on order pages, you can paste in the entire code and not use any conditionals.

That would be nice, I think the report system doesn't currently allow a search field in the report fields though. Something to consider though, thanks for the suggestion. It is a little bit more work to get the client's ID.

They would request a copy of their data by whatever means you specify. The ticket system is likely to be commonly used, but you should define this in your terms as they relate to GDPR. If there is demand for it, we would consider adding a self-service option for this in the future, but most companies will prefer to perform the export and review the JSON file to ensure it doesn't contain any information they don't want to provide before passing it along.

That's a good question. Right now the only way to sync them would be to do so manually, this option only affects new addons per the setting in 4.3. Syncing old addons to their parents could result in new prorated invoices, so I think we'd want to be careful about that. Perhaps a report to identify addons that are not in sync with their parent would be a start, if your goal is to sync them up.

Open up components/modules/logicboxes/config/logicboxes.php and add the TLD's that you want to sell (that aren't already there)

Hello, maybe it's not related to your problem but in my case setting an error in the "addService" module method raise an error on line 5742 of /app/controllers/admin_clients.php. On line 5707: $service_id = $this->Services->add($item, $package_ids, $notify); the method is returning null since an Error has been set on the Input module, however on line 5713 "$service_id" is appended to the array "$service_ids": $service_ids[] = $service_id; So on line 5716 the array $service_ids is not empty, raising then the error with the updateServicesRenewalForProration function. I solved the problem editing the admin_clients.php on line 5713, appending the $service_id to $service_ids only if not empty: if (!empty($service_id)) { $service_ids[] = $service_id; } I'm using Blesta 4.2.2, PHP 7.0.27

I think you want these options under the "Service" area instead of the "Package" area. Where you entered these, they should appear when creating/editing the Package, but the service area will be shown to customers during checkout.