Jump to content

D9Hosting

Member
  • Posts

    249
  • Joined

  • Last visited

  • Days Won

    1

D9Hosting last won the day on August 18 2017

D9Hosting had the most liked content!

About D9Hosting

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

D9Hosting's Achievements

Senior Member

Senior Member (3/3)

9

Reputation

  1. We moved over to the LCWSoft module a few months ago and the migration was amazingly seamless. As part of the setup you can choose to import billing agreements from other modules and it worked without any hiccups at all for us.
  2. I have never tested Stripe using 2 different WHMCS installations but I would imagine the problem, if it exists, could easily be solved by creating a 2nd Stripe profile/brand under your existing Stripe account. You'd then have 2 different sets of API keys for each installation whilst still being able to manage everything under your existing Stripe account: https://stripe.com/docs/account/multiple-accounts
  3. It's an issue that's as old as the hills, see here: WHMCS claimed they fixed it in v8.1.1 but we still come across it every now and again. I think they have given up trying to figure out what's causing it.
  4. Just to update the thread for anyone else who comes across the same error - I've fixed the issue by disabling Cloudflare on the domain running our WHMCS installation. Neither Gocardless, nor Cloudflare have any idea why Cloudflare would be interfering with the API callbacks but at least things are working again!
  5. Just wondering if anyone else has noticed problems with this module receiving callbacks from Gocardless since August 11th? I noticed a few days ago a strange lack of direct debit payments being received and on checking in our GC account any callback sent to the module is generating the following error: 498 Token expired/invalid I've generated new live tokens and webhook endpoints, re-uploaded all the module files but the issue remains. There is nothing showing up in the WHMCS module log, and in the gateway log all I am seeing are lots of entries saying: Callback verification failed (Invalid Token) : Payment requests and setting up new mandates still work fine, it's just the payment callbacks that aren't working. I've got a ticket open with the creator of the module but so far haven't had a response. I did also open a ticket with GC who said: Anyone got any idea what the issue could be? From our end nothing has changed since it stopped working so it's a bit of a head scratcher and for now we are having to go through and manually cross reference all paid invoices in GC with those in WHMCS and mark them as paid.
  6. We've got one client who is managing to trigger this error every time he orders something yet it looks to be fine for everyone else. The error he is getting is related to the capatcha on the checkout page (using invisible recapatcha) so for now I've just disabled the capatcha for that page.
  7. Add us to the list of users seeing this issue in 8.13. Just had a PO'd client get in touch with us because he "paid" us for an order that we had no record of.
  8. We've seen the same problem sporadically with both Six and a custom template. The "please complete capatcha" message shows for a few seconds and then it disappears and the domain search results show up. I figured it could be due to us using Cloudflare on the domain but gave up trying to fix as it's not a total system breaker and just another WHMCS quirk.
  9. I liked this section from the blog post that mentioned the exciting features they were working on for a future release: More marketplace bloatware to look forward to, but who knows, maybe we are in the vocal minority and most users are requesting this?
  10. Common <> Good For major changes like this you need to ask the users of your software for feedback BEFORE you go ahead and implement yet another "feature" that makes our lives harder.
  11. You're too good for this community, problem solved! Thanks so much for the help, I'll buy you a beer.
  12. I do actually get the "Email Sending Failed - Email message rendered empty - please check the email message Smarty markup syntax" error message, but the line of code it mentions in the logs is any line that has this in it: I like the sounds of the hook idea rather than wasting more time on this, I'll send you a PM.
  13. Hi @brian!, Thanks for the quick reply. Still no luck I'm afraid: $smarty_security_policy = array( 'system' => array( 'enabled_special_smarty_vars' => array( 'session','foreach','section','block','capture','now','get','post','server','request','template','const','cookies', ), ), 'mail' => array( 'php_modifiers' => array( 'strstr', ), ), ); Generates the following error when sending an email : PHP function 'strstr' not allowed by security setting Just going back to what you mentioned last week: This was triggered when I first noticed a security policy error that was being triggered by a custom template using "$smarty.session". To fix this I set a security policy as per the WHMCS docs to allow the session variable. I then noticed a ton more errors when accessing various pages in the admin area relating to WHMCS system variables - server, capture, etc. It was at this point I got in touch with WHMCS and they advised I now needed to add all the variables used by WHMCS to the security policy and not just the variable I wanted to allow. So it looks like as soon as you create a security policy to enable a certain variable using "enabled_special_smarty_vars" anything that was previously being used when there was no security policy in place needs to be specifically added. WHMCS did say they were working on a more "graceful" way to handle this in the future but I wont hold my breath.
  14. Hi Guys, Thanks for the responses. Unfortunately the newly formatted code doesn't work either: $smarty_security_policy = array( 'system' => array( 'enabled_special_smarty_vars' => array( 'session','foreach','section','block','capture','now','get','post','server','request','template','const','strstr','cookies', ), ), 'mail' => array( 'php_modifiers' => array( 'strstr', ), ), ); With the above code the template which uses $smarty.session works fine but the email template containing "strstr" throws up the security policy error as before. If I remove the system security policy leaving just the email policy the emails work fine. I have a ticket open with WHMCS but don't hold out much hope. As a workaround and before I spend a morning editing custom email templates, is there perhaps an alternative I can use to "$smarty.session.cart.promo" in /orderforms/configureproduct.tpl to pull the promo code used (if any) by the client? Figure it will be easier to edit that one file rather than a ton of email templates!
  15. Apologies for bringing an old thread back from the dead but this issue has reared its ugly head again in version 8.13. We had an issue with a smarty variable in a custom template file triggering a security policy error so WHMCS Support suggested adding this security policy to our config file: // Smarty enable special variables policy: $smarty_security_policy = array( 'system' => array( 'enabled_special_smarty_vars' => array( 'session', 'foreach', 'section', 'block', 'capture', 'now', 'get', 'post', 'server', 'request', 'template', 'const', 'strstr', ), ), ); This fixed the issue with the template not working but now we are getting a "'strstr' not allowed by security setting" error when trying to send any email that contains this: {if strstr($client_credit, "GBP")}Blah blah blah{/if} The original security policy we had in place to allow "strstr" is still there but doesn't work if we also have the new "'system'" security policy in place, it works fine if we remove this leaving just the original security policy but ideally we need both the custom template and the code in the email to work! FYI our full security policy is listed here: // Smarty custom email based template policy: $smarty_security_policy = array( 'mail' => array( 'php_functions' => array( 'strstr', ), ), ); // Smarty enable special variables policy: $smarty_security_policy = array( 'system' => array( 'enabled_special_smarty_vars' => array( 'session', 'foreach', 'section', 'block', 'capture', 'now', 'get', 'post', 'server', 'request', 'template', 'const', 'strstr', ), ), ); Any ideas how to fix or if not, is there another workaround we could use to display conditional data depending on the currency used by the client?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated