ModulesBakery
-
Posts
141 -
Joined
-
Last visited
-
Days Won
5
Posts posted by ModulesBakery
-
-
I don't think your solution is something we'd be able to use. It's generally bad design to override existing fields (i.e. non-merchant gateways) to inject special-case alternate functionality (i.e. credits). I'd also be curious to know how your solution affects the Wizard and Standard templates considering they already handle credits.
I think that Naja7host posted that solution (regardless of how good it is) as a temporary solution for other Blesta users to use till you decide to solve this and re-design the order forms to support paying using the credit.
-
You can follow the steps provided here to integrate it with your website design:
http://www.blesta.com/forums/index.php?/topic/3642-blesta-integration-33x-advanced/
OR you can get in touch with LicenseCart ... he can help you with that:
http://www.blesta.com/forums/index.php?/user/38-licensecart/
-
-
It sounds like the Order plugin would have to support and listen to its own custom events in the case you described. Plugins supporting their own events would be interesting, but I think the OP's feature could be resolved simply by updating the Order plugin to support the 'one service per client' feature.
As Licensecart mentioned, this does bring up some potential issues, such as when the service is cancelled, can they order the service again? What if an admin manually adds multiple services to the client? Would this negatively affect you, the client, or the services in some way? And how would this affect addons? Could addons be ordered multiple times if they are added onto separate services? Some things to think about..
- Service is canceled: as Naja7host said, when setting up a package an option for this would solve the problem.
-
Hi,
I would like to request a feature where it would be possible to limit a package to one service/order per client, so each client can place one order only for that package, if it is already in the client's account, that client cannot place any more orders of the package.
-
-
Other solution if you don't want to touch the code:
Admin Area >> Settings >> Look And Feel >> Themes >> Client Tab >> Edit the selected theme >> in the header logo field just add your logo url.
EDIT: just saw your post above mentioning that you've already managed to change it from the system.
-
public function getClientTabs($package) { return array( "tabClientSome"=> array( "name" => Language::_("yourmodule.tab_client_yourmodule", true), "icon" => "glyphicon glyphicon-someicon", )); }As licensecart said, however, from your module .php file:
blesta/components/modules/yourmodule/yourmodule.php
search for the getClientTabs method and modify each tab as shown above.
-
$fields = new ModuleFields(); $my_label = $fields->label("My Field Label", "my_field_id"); // Create a field label displayed next to the checkbox $field_label = $fields->label("My Value", "my_field_my_value_id"); // Create and attach the field to the label, set as checked (3rd param) if necessary $my_label->attach($fields->fieldCheckbox("my_field_name", "my_value", (isset($vars->my_field_name) && $vars->my_field_name == "my_value"), array('id' => "my_field_my_value_id"), $field_label)); // Attach a tooltip to the label $my_label->attach($fields->tooltip("This is my tooltip")); $fields->setField($my_label); -
I've decided to set up Blesta to sell domains, SSL, hosting. The package I installed should be version 3.3.3 (the last paid extension available). The documentation, as it is found in here http://docs.blesta.com/display/user/Overview, is particularly crappy (outdated and incomplete at the same time).
I think I've managed to install it, and to install enom together with PayPal. By the way, the PayPal module asks me for my password, which is extremely dangerous. Anyhow, dangers and concerns aside, now the question is what to do with these modules I've installed.
Any link to some updated documentation that makes sense? Thank you.
Besides what Licensecart said, the PayPal payment gateway plugin asks you for an API authentication user and pass not your PayPal password.
-
Not sure why would Blesta provide or help moving to a competing product ?!!!! does not make any sense !!
-
Module Features:
- Account Management (Create, Un/Suspend, Termination)
- Account Statistics
- FTP Accounts Management
- Email Accounts Management
- Email Forwarders Management
- Addon Domains Management
- Sub Domains Management
- SiteWorx & Webmail Login Buttons
- Backups Management
- Cron Jobs Management
- Databases Management
- Domain Redirects Management
- One-Click Web Apps Installer
Preview:
Visit our website, click here.Only $69.99 / One Time
[Order Now] | [FREE Trial] | [More Info]
What's Included:
- 1 Year of updates.
- 1 Year of support.
- Instant download.
- Have a question or need more information:
Send a ticket to our sales department. -
I am looking into taking 2checkout in addition to PayPal but they are having me fill out this whole PCI compliance. Looking at it most of the questions are geared towards a huge company. My question: The 2checkout module using the API does it store the card information locally on my server or at 2checkout? Is there an alternate I could use like BluePay, etc. that would not require me to store credit card data on my server?
2CheckOut is a non-merchant payment gateway, so no card info will be stored in your server, in fact the whole payment processing operation won't be on your own server, your customers (after submitting their orders) will be redirected to 2checkout's website to submit payments.
-
Stay away mate, as Paul said obviously it can and probably will harm your business.
-
Nice! When you tweet out updates, if you mention Blesta we'll usually retweet. If it doesn't mention us, we don't usually see it. Nice work!
Thanks! , i was in a rush when tweeted the news.
-
You can do this as follows:
$fields = new ModuleFields(); $fields->setHtml("<script type='text/javascript' src='js/yourjsfile.js'></script>");More info can be found here:
-
New Update For The Tasty cPanel Module has been released, click here.
-
i agreed with you , i think is not the adequate time to release a official module for DO as already one in the market , is true that is paid and mybe the price + annual support is hight . but i assume blesta should keep developpers making modules for blesta , if they release the same modules , the developpers will not be interested in developping for blesta , because they feel one day the module will not be sellable in the market .
I agree with that Blesta would not bother releasing an Official module when there is one already done, specially, when they have more prioritized/important features/plugins to think of.
As for the pricing of our module, not sure if it is allowed in this forum to talk about our own pricing, but anyways, i would agree that the owned price might not fit with everyone, thats why we have a monthly license, not sure how a $6.99 per month can be considered a high price.
"...never stated it was necessarily a public module..."
As licensecart said, in addition to, not stating leaves the door open for others to assume which module you're talking about, since searching the Blesta forums and google would only gets you to the DO module that is done by us "ModulesBakery" i had to come here and clarify things up.
-
1) I didn't specify whose module I was speaking out.
2) Never once did I say that the V1 API should be used, quite the opposite actually.
3) This is a request for an official module.
Hi Danny,
1) As far as i know there is only one DO module for Blesta.... Which is ours.... so obviously....
2) Am i misunderstanding what you said below?
The V2 API is in Beta so obviously they devs may wish to hold off, the the V1 API is stable and established.
3) I replied to this thread only because you've pointed to the 3rd party's DO module anyways.
-
If anyone else is interested in this please +1. There is a 3rd party (paid) module but it seems sketchy to say the least. The V2 API is in Beta so obviously they devs may wish to hold off, the the V1 API is stable and established.
- I am sure you're talking about our module, but Huh? sketchy? all of the available methods through DigitalOcean APIv2 have been included in that module, let me know what made you think it is sketchy??
- I know APIv2 is still in Beta however, developing a module based on an API v1 which will be deprecated soon, is not a good option too, another thing that made me feel comfortable about developing the module with API v2 that before starting on that module i have sent a message to DigitalOcean's support and they recommended me to use the API V2 (attached a screen shot of their reply), so with such reply, not sure why i would use the API v1 instead.
-
The AJAX order templates are not designed to support applying credits. If you want clients to be able to pay via credits on their account, you should use the Standard or Wizard templates instead.
That does not make any sense, a feature included in a template shall be included with all others specially something like that ?
-
Hello,
I believe there is a bug in the Ajax Boxes Order Form Template, when you're on the order form and you're logged in as a client there is no option to pay using the credit while on the other order form templates it does show the option to use the client's credit.
-
-
Yeah we have been in business for less than a month and thats probably not enough for some of you to trust us, but in fact ModulesBakery is growing. More and more products are being built, And although i wanted to announce this later on when the new products are almost done, but anyway, new members have joined our team this week @ ModulesBakery (a developer and a web designer).
Blesta Developer Wanted
in The Marketplace
Posted
Thank you for the kind words, it was a pleasure doing business with you