xvid

http://forum.whmcs.com/showthread.php?50258-WHMCS-5-1-2-New-method-Domain-Sync-quot-not-supported-quot Temporary solution: apply all 5.1 patches provided: http://forum.whmcs.com/showthread.php?51266-V5-1-Patches and use old crons.

I can confirm that the old separated sync script are now working properly on my end. This is very strange though as few days back they didn't. Maybe some of the patches are involved I don't know.. but yes - I am confirming they are working and it is a good alternative for now...

Works fine on my end

I understand your point, just want it to clear out mine.

It might be a part of a bigger issue indeed .. ok BUT you are not right about "Matt already give his answer" and I will tell you why - it is simple as that: In 5.0.3 I had normal domain syncing script and now I simply have NOT. I don't care if the registrars are not prepared with their APIs because it worked just fine in 5.0.3 and now it doesn't work so the problem is in WHMCS and not in the registrars or me making some custom registrar syncing (and yes the old separated syncing scripts are not working). By the way I am talking about already included and old supported registrars in WHMCS not for custom ones.

I am talking about the "Sync Not Supported by Registrar Module" problem when the domainsync.php is run and that problem is clearly not fixed yet ---> http://forum.whmcs.com/showthread.php?50258-WHMCS-5-1-2-New-method-Domain-Sync-quot-not-supported-quot

I might add a very important one - the new cron domainsync script does not work with many registrars and shows "not supported" but that's a little offtopic.

This is not only Nominet, InternetBS syncing gives me "Not supported.." constantly since the upgrade to 5.1.2

It is also affecting Internetbs registrations. That's for sure.

Absolutely agree with you. I have btw tried to fix it myself but it includes some core changes etc.. and I think it would be better if the WHMCS team make an official FIX as this is not simply a bug but a core and very important feature that does not work ... I have sent a message to Matt so I really hope he is aware of this problem.

Any word for a fix?

It is a known issue: http://forum.whmcs.com/showthread.php?50258-WHMCS-5-1-2-New-method-Domain-Sync-quot-not-supported-quot No official position yet.

I have tested the old sync scripts and they don't work either so we need a fix for this ASAP as practically we don't have auto sync now...

Did someone make it to work properly. The Error persists, at least on my end.

Same here - Testing with InternetBS registrar.

Just to let you know guys - I had my website approved again by the new Payza verification process and now it is working properly.

Just to let you know guys - I had my website approved again by the new Payza verification process and now it is working properly.

Hi guys, I have just installed the new Payza module after reading this: http://blog.whmcs.com/ The module is successfully activated and installed However, I am still receiving: This merchant is not able to accept payments through Payza at this time. Anyone else tried the new module?

Same here. It gives: This merchant is not able to accept payments through Payza at this time.

Hello Everyone, The new Product Group creation is possible, but what about new product type? As far as I see, there are only 4 predefined product types and a new one cannot be created? This functionality is required for me because I am offering other product types along with the hosting and domains and I need different email templates per product types. I will be thankful is someone share his opinion.

Hello guys, I have noticed the following behavior regarding invoices: When I go to Admin Area ---> Click on Client --> Click on Invoices and then I try to view/download an invoice - it is generated only in English regardless the Language chosen in Admin Area --> The Client --> Profile This is also the case when the system automatically sends the invoices to the clients. When a client browses his invoices in his Client Area they (the invoices) are generated in the language that the client has chosen in the client area drop down. So that is the correct behavior but why it is not the same as the Admin Area? Any help will be appreciated.

Thank you for answer othellotech. I am aware of the "exclude process" feature of the Firewall. I still can't explain why such request is necessary though: tcp: my_server_ip_address:41095 -> yy.yyy.yy.yyy:110 because pop.php is supposed to be a simple piping script?

Hi Everyone, I have whmcs installed on cpanel along with the CSF firewall running on this server. Evertyhing works just fine on the system with the following exception: Once a week I receive the following email from the CSF: lfd on myserver.com: Suspicious process running under user mywhmcsuser Command Line (often faked in exploits): php -q /home/mywhmcsuser/public_html/pipe/pop.php Network connections by the process (if any): tcp: my_server_ip_address:41095 -> yy.yyy.yy.yyy:110 Files open by the process (if any): /dev/null /dev/null /tmp/sess_e1b78de5b6t0933m7261f87c48da5c2fc Is this a normal behavior or I am missing something here?