a.daniello
-
Posts
159 -
Joined
-
Last visited
-
Days Won
2
Posts posted by a.daniello
-
-
Yes! This is, for me, a big question!
So many clients (but also staff member) ask me why "update..."!
This isn't a big problem, but maybe adding a new template for "new ticket" should be better
-
-
Tyson, please consider that this is a very important fix.
We're using proforma as default, and so for every order we need to resend manually the invoices after payment: this isn't the best for us and for our clients.
Thanks
- lukasP and Blesta Addons
-
2
-
-
Agree
-
@naja7host
What i said is only a joke, a provocation. You know my opinion about multi-language & co. in Blesta. I think also that Blesta team should take you on board, as a remote freelance!
Non only for your great contribution, but also because you can represent an foreign point of view (about translations, invoicing and pro-forma, and so on).
Good luck!
- Blesta Addons and serge
-
2
-
As i reported also in http://www.blesta.com/forums/index.php?/topic/3782-blesta-is-multi-languages/?p=29289, there is a similiar problem also in Italy: in Italy we have Province (110) and Regioni (20); Regioni ara like "States" but Blesta doesn't distinguish the two levels so in the list we see all together.
This is not fully related to ISO definitions and is more complex, also to manage:
- for "address" we use only Province
- for "tax rules" we need Province and Regioni
...so we can't simply delete/add Regioni.
Maybe can be useful (in addition to a function to edit these data, as in "Admin tools" by naja7host) add a flag to define the "area" for every entry: use "for address", "for tax rules", "for together".
I hope you understand me.
-
I imagine a real "cms":- multi-linguage (easy to do in "staff area" simply adding a select box , but hard to do in frontend because Blesta hasn't yet a language switch)- generating menu/sub menu in frontend (this is the piece that missing)- sorting and publish/unpublish with "one click" pages (easy to do too)- "page content" or "plugin/system page"I've done something like your, extending cms plugin, but i stopped because i need to change blesta core in frontend because: i dislike make invasive changes in blesta code; i like make upgrade without problems.When Blesta team will find time to compete the language switch in frontend and a way to extend frontend core via plugin, we can play with that.I hope that you understand my poor english
-
Ah! Ok, i understand... I hoped that you found a way to extend the frontend controller
-
@naja7host, very well done!
Only a question: where you call the method "get" of the cms model in frontend?
-
Great work!
I haven't time to try it, but now i go to read more in your code!
CMS is a very good news!
-
@serge this is a good news!
-
As we discussed in http://www.blesta.co...standard-label/ and in http://www.blesta.com/forums/index.php?/topic/4060-translation-of-gateway-name, there's a small improvement that can be useful:
allow for a separate, translatable, name/description to be used rather than the gateway name
So we can use a custom name for the gateway in order and/or pay form.
Thanks
-
I agree.
Opened a feature request: http://www.blesta.com/forums/index.php?/topic/4061-allow-for-a-separate-translatable-namedescription-of-the-gateway-name/
Thanks
-
However, i try to mark this as feature request because i think (thinked) that the right way to do this is as Licensecart said (simply modify the gateway language file).
-
As we discuss in http://www.blesta.com/forums/index.php?/topic/4056-changing-paypal-payments-standard-label/, there's a small issue with gateway name.
If i want translate the gateway name (eg. "PayPal Payments Standard" to "Carta di credito con Paypal") in order form and/or in client payment form, i expect that i need to edit gateway language file (eg. components/gateways/nonmerchant/paypal_payments_standard/language/en_us/paypal_payments_standard.php), but this isn't true.
I need edit pdt file with updating php code.
It's so because, for example, the code is $this->Html->_($gateway->name) where $gateway->name is selected by db, and so not traslated.
Thanks -
But only now, in his last post, i read that dvhost tell about "order form".
In this case, you'ld make changes in plugins/order and depens on template that you use.
-
@naja7host, yes this works fine because $gateway->name returns the string 'PayPal Payments Standard' so i add the language definition for this string (and for other payment type).
I preferred this solution that impacts only in view and language file and make possible "translate" every payment name (without check it with an if control).
-
If dvhost wants to modify payment form (e.g. client_pay), i think isn't so easy because Blesta get this label from DB and not in language definitions (Blesta isn't yet full multi-language).
In this case my solution is:
1. add the following in "language/it_it/client_pay.php"
$lang['PayPal Payments Standard'] = "PAYPAL as you want";
2. edit app/views/client/bootstrap/client_pay_method.pdt#81, replecing
$this->Html->_($gateway->name);
with
$this->_($gateway->name);
This works for me.
-
Many thanks, naja7host.
Now all i need is... time!
-
-
I too.
I hope thai i'll have to develop this MOD.
-
naja7host, what do you think about
1. download all invoices in an archive (eg. a zip file)
or
2. download all invoices in only one PDF file (as now is in email with multiple invoices)
?
-
How Do I Remove This?
in Support
Posted
I understand well what kpmedia says. It's the same for me.
This is a "logic" issue: e.g. if i enable only "paypal" as payment, Blesta should hide "Payment options", and so on. So, for these issues we not should need plugin!
Maybe i'm wrong, but there are some improvements about this argument in Blesta's todo list.