Leaderboard

This is a one-time paid plugin with unlimited support and updates. This plugin replaces the one shipped with Blesta so you can't use both. It's created to take the CMS to the next level. The plugin does have a few bugs at the moment which are going to be shipped next week so you can remove pages / blog posts, etc and also so you can add comments on the blog pages. We also have 1.2.0 and 1.3.0 all planned out and you can see the to-do list on our community forum after purchase, you can also state what you would like to see and if we like the idea we will add it to our list. Please note after payment for this plugin it's non-refundable due to the nature of the product in question. Blesta 3.6.2 with v1.1.2: Blesta 4.0.0 with v1.2.0: Pages: Blog posts: Categories: Menus: Settings: Multi-language: Blog posts: Videos: Menu Video: http://screencast.com/t/PAcVeZ8QQ Page Video: http://screencast.com/t/81paso43vd Blog Video: http://screencast.com/t/qXecVGKkox Demo url: https://licensedemo.com How can you get the CMS plugin? We provide it with our Modern Integration+ for free and we sell it on it's own here for $150 or $12 a month: Order form. The plugin is fully editable minus the 4 files used for licensing purposes. We'll only support the plugin if no major changes have been done, that way we know it is our issue and not something you've done to it. It's been tested by three people so far, Doug (Evolve Webhost - Modern Integration+), Mujahed (ModulesBakery - Developer) and myself whilst preparing for the next Licensecart design. PS: If you develop a lot for blesta (free plugins / modules, etc) and would like a copy PM me and I'll issue a free license for your hard work in the community. Free Integrations which work on BlestaCMS out of the box: - Margo

Yes that's what Blesta does now. I'm not stating that you can't have 1 minute cron jobs that work. I'm just saying, in practice, it's not really a good idea as the risk of a collision is high. Plus, why have 1 minute cron jobs when you have can SMTP polling every 15 seconds?

1 minute cron jobs are a bad idea. It's too easy for them to pile up and execute on top of each other. If the point is to pull email from SMTP/IMAP server in near real time, create a script that runs constantly and polls the SMTP/IMAP server every 30 to 60 seconds. For example: <?php while (true) { $window = 60; $start = microtime(true); // TODO: do stuff $runtime = microtime(true) - $start; // wait until we can run again... sleep(max(0, (int) $window - $runtime)); }

What do you consider to be 'full support'? Stripe, like many other gateways, supports taking payment in different ways. Typical behavior is to either allow a customer to pay from your website using their API, or to pay from the gateway's website. We categorize these behaviors into Merchant and Non-merchant gateways, respectively. Blesta implements the Merchant behavior of Stripe, that is, to allow payment to be taken from within Blesta without redirecting the client to pay off-site. When a customer makes a payment, their card data comes to your server before it is sent along to Stripe. You can choose to either store the credit card information in Blesta via a Payment Account, or to store it remotely with Stripe and use a token to process payments with it in the future. In either case, your server sees the credit card number at some point. This requires you to be PCI-compliant. Blesta also stores the last four digits of it as well as the expiration date for internal use, such as to send email reminders when the card is about to expire. The person that wrote the comment you quoted appears to consider "full support" to be a scenario where card data never touches your server (i.e. PCI avoidance). This can be accomplished using Stripe.js whereby credit card data is submitted directly from the customer's web browser directly to Stripe, skipping your server altogether. Blesta does not currently integrate with Stripe.js. I have no ETA on when that may be available, but it is on our radar and you would want to follow this task for updates.

Can you provide an example of content you've added that resulted in bold text? You could have added two underscores to make it bold, or an email client can do so as well.

Just wanted to publicly thank Michael @Licensecart. He's helped me out a LOT and I was finally able to switch to Blesta today. This guy has bent over backwards to help me get setup. DL

A credit is the sum of all unapplied transaction amounts on the account. If you want to remove a credit, I would suggest voiding/refunding the transaction(s) from whence it came. No need to create an invoice to apply the credit to, as that may indicate revenue received for tax purposes, which may not be the case.

Curious, what purpose would it fulfill to have it as an option?

As mentioned above, I use this: http://timkay.com/solo/ It's dead simple and it's not posible to have more than one cron job at same time, as cron can not be run untill last cron job ended. Because an open port is directly tied to a running process, chances of inconsistency and having to detect and cleanup orphaned PID files, are zero.

I have now posted the solution above

Nice find never would have thought of that, - normally do a HR.

I wouldn't say it'd be in the next release. An addition to the success page has not been a consideration for us yet as we have more pressing additions to get through to get to version 4.

I'm not aware of any issues with Plesk 12 and the Plesk module with Blesta. Plesk maintains backward compatibility with its older versions, so even though the Plesk module in Blesta only currently allows you to select a version up to 11.5, this will work for any newer version of Plesk (e.g. 12) as well. If you are looking for the module to support features added in Plesk 12, then these are not available through the module in Blesta. Some people have experienced issues with configuring Blesta/Plesk to work correctly, however, which may be what you were referring to regarding other forum posts. You should make sure Blesta is installed on a server with libxml enabled in php and that your Plesk credentials are set appropriately in Blesta to ensure the API is working correctly. It is also recommended to have Plesk and Blesta on separate servers. If you have them on the same server, you can experience an issue where Plesk will restart itself before it is able to notify Blesta that an account was created. This will result in the account being added in Plesk, but not being synced up with the service in Blesta. See this thread.

Something like that could be shown to the client on the success page. I believe the data is available to the success page template, so it could be included.

There are always bugs somewhere, but none that I'm aware of that are caused by something in v3.5.2. Here's a list of recent bugs.

i have used as najahost say . and it work . but the return_url and the callback_url was confusing for me . i have thinked the callback_url is was used just for notification's gateways . also the success() method is not storing any data as naja7host mentioned by the processReceived() , and i ask why it return all the transaction data if not stoed or showed to the client . so i think it should be at least in the thank_you message display a something like Thank you for your orders ..... Transaction ID ; XXXXXX Amount Paid ; 0000USD Invoice PAID N ; 1451 , 1452 ; 1453 ; What do you think Tyson ?

You're more than welcome mate, been a pleasure to help, and glad you are now live without whmcrapsecurity

Blesta also needs to execute the mysqldump binary on your server, so you should make sure that it's available and your user has execute permissions.

If you use the Portal plugin (installed by default), an "Order" link will appear on the index page that you have Blesta installed under. You can set that link up to default to the client registration form by setting it as the default order form under [Packages] -> [Order Forms] -> (Settings tab). If you want the client login page itself to have a link to register, then this would require you to update that template file. You can find it in /app/views/client/bootstrap/client_login.pdt. You can then add HTML to set a link to the client registration order form. Note that you have to maintain this core file change after each upgrade of Blesta, or it may be overwritten.

One of these reasons caused the redirect: The ticket is assigned to a client. -- The client must be logged in to reply. The ticket's support department only allows clients to reply. The SID was not given or is invalid.

The error "Register is in an invalid format" is not a message that Blesta displays AFAIK. Is that the exact error? I see you are using custom client fields. You have one disabled. That might be the issue.

Thanks for contributing to the translation! There are over 30 other contributors that have helped to translate Portuguese for Brazil, so I'm sure more will help.

Many thanks for sharing I will also tomorow doing a litle donation (im on my smartphone in bed lol its 23:20/at night eheh)

new release 2.4.0 + removed option to correct invoice date , is fixed in CORE-1605 . + aded option to read/write language selector in sessions .

There are two URLs a gateway typically needs to use. First, the payment callback should be sent to: Configure::get("Blesta.gw_callback_url") . Configure::get("Blesta.company_id") . "/yourgateway/". $client_id Second, the client should be redirected to: domain.com/blesta/client/pay/received/yourgateway/client-id/ ...which should be provided to the YourGateway::bulidProcess() method in $options['return_url']. If the gateway only supports one of these, use the callback URL.

You would set the email tags in the package welcome email. Let's say you have a universal module product that you're creating. Under the "Package Options" section of your product, you can set a label, name, type, values, whether the field is required, and whether to encrypt the values. e.g. Label: My Package Option Name: my_package_option Type: Text Required: No Encrypted: No Values: Similarly, under the "Service Options" section of the product, you have the same fields available. e.g. Label: My Service Option Name: my_service_option Type: Text Required: Yes Encrypted: No Values: Now when you add/edit a package where you have selected this universal module product, the Welcome Email has tag support for your fields based on their "Name" value as set in the universal module. Based on my example Package and Service options above, you would have these tags available to the package welcome email: {package.my_package_option} {service.my_service_option}