Leaderboard

If the public and private key pair no longer match then it would be possible to be able to encrypt a card number with the public key, but not decrypt it using the (wrong) private key. Since the key in the config file is used to generate an HMAC and encrypt the private RSA key, it's also possible (and more likely) that the key in /config/blesta.php was changed. This could have happened if Blesta was installed fresh, and the config file was overwritten with a previous one. That is likely what happened here. If you don't have the original config file that was created when that RSA key pair was generated, then you're better off doing a fresh install. That key is used for encryption in other places as well, so I would highly suggest a fresh installation, especially since it is not production.

You might receive a 500 internal server error if you have a fatal error or syntax error in the code that is unparseable. If it only affects modules, then my guess is one of the modules is causing it. You can remove all of the module directories from /components/models/ and see if the problem goes away. Then add them one-by-one until you discover the module that is causing the problem.

Thanks. This issue is resolved in CORE-1592 for the next version of Blesta. It won't fix the fact you have a 'hidden ticket', but it will make it so you cannot split ticket notes by themselves, as that is not the intended behavior. e.g. since a client doesn't see ticket notes, they have nothing to see in regards to that ticket. If you'd like to remove the 'hidden ticket', you will need to either add a reply (not a note) to that ticket--via the database--or convert a note to a reply, then it will be visible from the UI.

Thanks! Didn't think of the sub nav bar. I'll have to look at that. It's going to be my weekend project.