Leaderboard

Under the client details further down, you will see Record Payment. Complete all the details and click Continue.

It's just a difference in opinion and that's fine. We opted not to go with a heavy template engine for the reasons Tyson mentioned, because they are known to have vulnerabilities, and because they produce more overhead. That's not to say that the purpose these template engines fulfill isn't valid, I can understand certainly how the restrictions they place can be beneficial. Using smarty/twig/other wouldn't make me feel any better about giving someone I don't trust access to the templates though. If I don't trust them, I'm not even going to hire them, and if I do trust them, I'm still going to audit the code myself. They can have access to the dev environment, but never live. Fortunately with templates, it's fairly easy to spot any logic that shouldn't be in there, so not difficult to audit.

If you want to delete a post, it probably shouldn't have been posted to begin with. A good rule for the future.

OK, let's bring this thread back on topic, It's not fair to the OP.

thank you paul for rewriting mine @Paul I told you I wasn't a PR person and I appreciate you rewriting the grammar,etc

So minphp v1.0 will likely be the same as it is for Blesta, where it will require the bridge. Maybe a 2.0 would not require the bridge. Constants are not subject to change (they are "constants" after all). If you really needed to change them without modifying core files, then you *might* be able to define them at run time through the AppController::preAction event, which may or may not suffice for what you use them for.

Yes , you can . maybe something like $reply_data = array( 'ticket_id'=>9, 'vars' => array( 'ticket_id'=>9, 'staff_id' => null, // the reply is from this staff user 'client_id' => 2, // the reply is from this client user 'contact_id' => null, // the reply is from this client contact user 'type' => "reply", // this is a ticket reply 'details' => "API reply", // the ticket reply description 'status' => "open", // status of the ticket 'staff_id' => null, // the staff user the ticket is assigned to ), 'files' => null, 'new_ticket' => false // this reply is for a newly created ticket ); $response = $api->post("support_manager.support_manager_tickets", "addReply", $reply_data);

Thank You @jobplease. It worked!!!

Great plugin, but I have one problem. There is no way to open new ticket for unregistered client, I get " The client selected for this ticket does not exist." error.

OK guys, this page has been updated. Please review. I made some grammar changes, etc. especially on yours @timnboyshttps://www.blesta.com/development/

Just remember there are a bunch of open source modules/plugins/templates/gateways/etc from naja7host. That doesn't include his helpful code posts in this forum. Plus he has been around the forum since the end of 2012. That gives me a lot to go on to base his coding skill off of as well as his reputation around this community. You are fairly active on the forums but from what I can see you don't have any open source projects for blesta that I can look at. You haven't yet contributed enough to the community to be considered at naja7host's level. Maybe in the future as contribute more and have more people using your modules/plugins and reviewing them, but not yet.

I'm not a coder... but I asked my dev to really customize my blesta install, and he did a great job doing it without ever touching the core files. We hit some limitations (like you would on competitors), which could be overcome, but that meant overwriting core files and like you, I didn't think it was a good idea It's very secure though. I had an outside party try all the common attack vectors + whatever they had in their toolbox and no exploits to be found. So while I didn't do it myself, it does seem like Blesta's way to theme things is still secure. Btw : one thing I'd suggest is get a dev or staging license from Blesta. Have your third party theme it on that license. Run tests on it, get the code reviewed by someone else if you don't trust your dev, and when you feel good about it, move it to production.

Not sure which plugins you are talking about . from my part all my plugins/ modules will be upgraded to be fully v4 compatible . we have begin the most used free plugin "cookies cutter" , we have added so many option now to that plugin, the next is clean orders and resend welcome email . i think they need just a small Html code change . We have Logicboxes Reloaded already upgraded , but we will not release it now, as we respect other developer that has a paid version, so we don't want to disturb his business .

I will write another text, I will send a PM with the text.