Infralliance

It would be nice, but when we go in the "login as client" section the client's language should be selected at first, with the option of switching to whichever language the admin prefer. That would be my favourite scenario. Another would be to go in the "login as client" section in the admin language, and have a warning or small banner mentionning "The account is configured using Other_language, would you like to switch?"

It would be nice, but when we go in the "login as client" section the client's language should be selected at first, with the option of switching to whichever language the admin prefer. That would be my favourite scenario. Another would be to go in the "login as client" section in the admin language, and have a warning or small banner mentionning "The account is configured using Other_language, would you like to switch?"

it might help in some sense  . but we should know first the language set by client .
 
the core CORE-1320 will resolve other important issue .
 
my opinion should by default use the client language . i have check the code , and i don't see that is a diffuct task to add/change  .

if i don't know Arabic or Spanish or either one of my staff don't know it , i  will not offer this languages as options for my clients .
 
normally LOGIN AS CLIENT should be the same as it meaning , login as client , so simple .  admin has it own interface to edit and show client profile , in it they use preferred language . 
 
So to avoid this opinions, a option in admin setting to allow staf use the client language when they login as client , is preferred .

+1. Custom CSS and HTML in the header.

i have adressed this in a previos thread .
 
normally login as client , it should use the client language instead of staff languages .

this one

CORE-818 and CORE-819 address the domain management plugin (These Epics are currently private). We are working out the details internally, and considering everything everyone has had to say regarding domains. It's likely that we will open these tasks up and start a discussion in the near future.
 
These features will be dependent on 4.0 however, which we want to get out relatively quickly. There are a lot of major benefits to developers in 4.0, in part because of the PHP dependency change to PHP 5.4, namespaces, and more. Domain management won't be in 4.0, but we are continuing to make progress in designing the feature, and implementing some other core changes so that it will be easier to implement. (For example, plugins will be able to control package pricing. This allows for the domain plugin to set pricing for domains (Think pricing grid for new/renew/transfer, 1-10 years). It's a powerful feature that could be used by other plugins for a variety of purposes.)

Yeah, domain management appears to have a few things missing. My big wish is for a DNS manager for cPanel DNSonly so that clients can use our nameservers and manage their domains how they wish.

A draft feature like the invoices however would be a nice idea.

The Blesta Translator has also been updated to include language terms for v3.5.0. It also resolves a couple bugs mentioned here and here.

The error you encounter with some language terms should be resolved once the translator is updated to include  the next version (v3.5.0) after its public release.

At the moment it looks like Paul has it on the list to do but the TastycPanel module does it already if you need it instantly.

You probably want to use configurable options for all of this. Packages > Options. Create an Option Group, then Create all of these options and assign them to the group.
 
Then, when you create a package and define your "base pricing", you can select the configurable option group.
 
Now, assuming your Package is assigned to an order form, during check out all of the options will be available.
 
EDIT: Mike's right. You can sell the options, but they will not be automatically provisioned via cPanel and would have to be added manually to the service. It's likely we will be updating the cPanel module to support automatic provisioning of these kinds of options in the future.

Seems this went off topic. Everyone take a break and watch some BillingBRAWL.
 
@ModulesBakery, feel free to open a new thread whenever you want to do a new poll. This one is 5 months old, and off track so I'm closing it.

Just use robots.txt and block from google and other bots.you can use this links and generate your robots.txt
http://tools.seobook.com/robots-txt/generator/

Also for this one:
 
Translate the following:
? {var1} - {var2}
 
Term: Invoices.!line_item.service_option_renew_description
File: language/en_us/invoices.php
Type: Neutral string
 
Same error message.

For français, FR: Translate the following:?
 
Term: AdminBilling.invoices.duration_infinite
File: language/en_us/admin_billing.php
Type: Neutral string
 
When I translate "?" into "?" (exactly the same in French), I get the following error message: Invalid term ID for version "3.4.0".
Also: Well done! You have completed the translation of français, FR. New language definitions are added periodically, please come back later to contribute more to this language. If you'd like, you may translate another language now.
 
The translation of the French language is far from being done, and if I switch from "In order" to "random" I can continue (there is no skip button in "in order" mode).
 
 

Merci @PointPubMedia

I would loooooove an OVH module Any chances?

Thanks for bringing this up, and for including the term that led to the error. We'll look into the problem shortly.

New language file exports have been generated, available from the download links on the translator.

Re-re-did the upload... 6251 successfully uploaded files, 7 failed transfers (directory already created), 0 Queued files.
 
Went back for the upgrade process, and I have the same result :\
 
Oops... I redownloaded, and it shows 7188 items... Something possibly went wrong when extracting... stay tuned...

Hi Guys
 
I was after a plugin that exported customer data, invoices and payment information to use on the desktop version of quickbooks.

This has been fixed in CORE-774 for v3.0.4.
 
To patch yourself, update /app/models/invoices.php (line 885):
 
Replace:
// Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); return $invoice_id; With:
// Increment the used quantity for all coupons used foreach ($coupons as $coupon_id => $coupon) $this->Coupons->incrementUsage($coupon_id); // Update invoice totals $this->updateTotals($invoice_id); return $invoice_id;