Michael

That's right, but the headers can be spoofed, that's why the ticket hash.

{ticket_hash_code} is designed in such a way that Blesta can use it to identify the proper ticket, without leaving room for someone to maliciously modify the code to reply with updates to tickets that belong to other customers. It's designed with security in mind.
ticket.id and ticket.code have direct relationships with real tickets, particularly ticket.id which is auto incrementing. Someone who receives a ticket with an ID of 100 can be reasonably sure that the ticket with an ID of 99 has already been created just before this one and is probably still open, and that ticket ID 101 will follow.

Do you have a ticket open? When you updated from 4.5.0 to 4.5.1 did you apply the patch originally or the full version? There's nothing in the update that should cause the error you received, unless it was a coincidence and your license hadn't been validated in quite some time.
When you updated to 4.5.0 was everything working fine? Did you run /admin/upgrade to upgrade the database? If it was working fine, and was upgraded properly, then applying the 4.5.1 update should be fine. However, you could pretty easily roll it back by re-uploading the 4.5.0 release, or restoring from backup. Does it work if you do that?

Support > Staff, click to edit the Staff member and add a signature for them under "Settings". Whatever is added to the signature will be inserted automatically into the editor when the staff member goes to respond to a ticket. The signature can optionally be removed, but it'll appear automatically.

Not an option right now. People can download and install it.  

The problem is that you are trying to access the /cart/ URI on an AJAX order form template. The AJAX order form templates don't have a cart template because the AJAX template represents a single page that makes AJAX requests for most of the checkout process (including the cart), so there is no cart page.
I'm curious how you got to that page, though, are you linking directly to it? If so, take a look at how to link directly to a product.
If you want that link to work, you can update your order form to use one of the Wizard templates instead.

it takes courage to take this decisions
excellent move mike...
 

CMS Community Edition 1.3.0 released.

Since this has a new table and not backwards compatible I've had to release it as it's new version 1.3.0.
You can download it from the Github or from our website: https://blesta.store/client/plugin/download_manager/client_main/download/29/cms-CE1-3-0.zip
Without Recaptcha enabled (Without the icon at the bottom right):

With Recaptcha enabled:

Settings:

 
Been hoping to do this for ages and @Joseph H asking for it last night I decided to try and get it implemented. 

Please hit upgrade to upgrade your CMS CE to 1.3.0.
 
If you get an error or the blestacms_settings hasn't been created or populated please open: blesta_cms_plugin.php
Find:
if(version_compare($current_version, '1.2.6', '<')){ or if(version_compare($current_version, '1.2.8', '<')){ change it to:
if(version_compare($current_version, '1.2.6', '>')){ or if(version_compare($current_version, '1.2.8', '>')){  

I left a detailed response to exactly this question yesterday
 

We're almost ready for the Beta 1 of the BlestaForums. Myself and Timothy (our collaboration together) are testing everything to try and keep bugs to a minimum. We're testing everything and when it's ready for Beta 1, we will update everyone here. We will be having a trial for 14 days to try it and then you can purchase a license from either Blesta.Store or CubeData. Each has their own licensing system. We've agreed on doing what I did with the BlestaCMS in the beginning and that will be that it will be open-code minus the bits for licensing.
We will be adding features as we go along and I'm looking into a way to integrate this forum plugin into the CMS so it can be a paid addon or free if you have the forums and the cms.
You can view my forums alpha version if you're a customer of ours: https://blesta.store/client/plugin/blesta_forums/
Please note if you find a bug please let us know here and I'll get us onto it to fix it.

What Mike said. There is likely a pending service that is failing to be provisioned. Could be resulting in an error. Check your logs at ../logs_blesta/ (Defined under Settings > System > General) Pending services listed under Billing > Services: Pending

More adoption!

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

Great Work .

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

Thanks mate wouldn't be possible without your help making the tickets  and I'll fix that haha how is now in the future haha. Fixed.

Nice!
Looks like you may have another typo in the success message.  It says 'you can how submit a support ticket'.

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

Never do 2 things at once. Since 4.4.2 supports PHP 5.6, I suggest doing the upgrade of Blesta first, then upgrading PHP.
Backup database + files 3.6->4.4 is a long way, I suggest upgrading to 4.0, then 4.4.2. See the upgrade docs at https://docs.blesta.com/display/user/Upgrading+Blesta for an important list of files that must be deleted when upgrading from 3.x. After you are up and running on 4.4.2 on PHP 5.6, and upgrade PHP, then you will need to apply the right hotfix in the blesta-4.4.2.zip file, hotfix-php7 for PHP 7.0, and hotfix-php71 for PHP 7.1 or 7.2.

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

It sounds like you want to POST each form to a separate location.
<?php // POST to the valid method $this->Form->create('/validate/valid/', [...]); ... $this->Form->end(); // POST to the index method $this->Form->create(null, [...]); ... $this->Form->end(); Your Validate::valid() method really shouldn't require an argument if you want to POST to it

Thanks,
i get now Blesta running:
ISPConfig3:
Web Domain -> Options -> PHP open_basedir: "None" -> Save
I'm not sure if that opens any security problems ?

Disabling open_basedir is the simplest solution, but you could alternatively include all paths that Blesta must access. Off the top of my head, the install directory, the uploads directory, the temp directory (/tmp/) to start. phpseclib also tries to access /dev/random, /dev/urandom for encryption purposes. It's easier to leave open_basedir disabled, but that's up to you. We also recommend running Blesta on its own server (A VPS will do) without any other applications, but many run in it a shared environment.

Your example mixes procedural and class syntax, so I'm not sure if you're running individual functions or if those are methods in a class.
If you are writing procedural functions, simply:
return success(); otherwise for one class method to call another non-statically:
return $this->success();  

Depending on the configuration, you will likely need to reissue your Blesta license to the new domain/location.
If the credentials are all the same.
 
There is a README file included with Blesta that describes how to upgrade. The upgrade documentation is also useful.
Here's what I would recommend in your case:
BACKUP YOUR BLESTA INSTALLATION AND DATABASE (especially /config/blesta.php) Put Blesta in maintenance mode Disable your Blesta cron job Download and upgrade to v4.0.0 as an intermediate step. This is mainly due to there being a lot of changes between v3.6.2 and v4.4.2 to make in one big leap. I would recommend upgrading via CLI mode (instead of /admin/upgrade in your browser) so that the upgrade process cannot time out in the web browser. Upload the contents of the "blesta" directory The upgrade documentation will be helpful to review. There are files you should delete as well, mentioned in the note at the top of that page. Some people have problems if those files remain after upgrade while most others do not. Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.0.0 Backup your Blesta installation and database again, now for v4.0.0 (You can perform the server/cPanel migration here, or later at step #12-13) Upgrade your server to use php 7.2 (php 7.2+ is only supported on v4.4.0+ of Blesta) Ensure php 7.2 is installed for both CLI and web Download and upgrade to the latest version (currently v4.4.2) - via CLI mode is recommended over /admin/upgrade in your browser Since you are on php 7.2, you will need to overwrite a few files from the "blesta" directory with all the files in the "hotfix-php71" directory. You will receive ionCube errors if you do not do this Upload the contents of the "blesta" directory, which now contains the overwritten files from the "hotfix-php71" directory Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.4.2+ Update configuration settings, like cron jobs and email templates, if necessary, since many changes were made since v3.6.2 Backup your Blesta installation and database again, now, v4.4.2+ Perform your server/cPanel migration as necessary Be aware that changes to your Blesta location (e.g. by domain or subdomain) may necessitate that you update any third-party configuration to point to the new location. e.g. PayPal IPN URL Log in to your account with us, or your reseller, and reissue the license Click to "Manage" the service representing your Blesta license, check the "Reissue License" checkbox, and submit Visit your Blesta installation at your domain and log in. This will complete the license reissue at your new domain Re-enable the Blesta cron job and observe that it runs tasks as shown on the Settings > Automation page You may need to reconfigure the cron job to run at the new location if it has changed Disable maintenance mode