Search results

Please open a support ticket so we can investigate this for you: https://www.clientexec.com/members/index.php?fuse=support&controller=ticket&view=submitticket

Hi there, Our API is quite limited right now. We're working on a new version, which will include full documentation. I do not have an ETA on this release though.

I see what's happening. Right now we're just validating by regex, not an actual list of TLDs. I'll see if we can do something better when not bundling with a domain product.

Can you open a support ticket so we can investigate this, and double-check your configuration? Also, which version of Clientexec are you using? Our 6.6.0 has the following changelog entry: Ensure domain name field has proper validation when not bundling with a domain product.

This will be something we look into once our 7.0 release is completed.

Looks like an issue with newer PHP versions and cWhois' implementation of the .be system. If you open a support ticket we can patch your system with a fix for this.

This is being added in our next major release.

If a1hosting.xyz is the proper domain of your control panel, then something isn't setup properly, as you can not connect to that domain + port. This would indicate a problem with your control panel setup.

Make sure the product is set to automatically activate, and then enable the order service at Settings -> Plugins -> Automation Services -> Order Processor.

If you can open a ticket we can see what's wrong. You need to make sure the routing rule is set to "Ticket Type Default Assignee" and that the ticket type gets assigned to a department. This should allow you to then get emails as long as you're in the department.

We've had no reports that it's not working. Can you please open a support ticket with us and include a CE Admin login and FTP/Control Panel access so we can troubleshoot this for you? You can also enable logging to level 4 per...

We've added a basic version in our 6.6.0 release We plan to continually improve on this system during future upgrades.

Anything in error_log? or the global apache/nginx error log? Also, hit F12, and see if there's anything in the console tab, or if there are any requests in the network tab that are in red. Your best would also be to open a support ticket so we can take a look, if you'd prefer.

Glad it's working!

Your best bet is to enable logging to level 4 (https://www.clientexec.com/members/knowledge-base/maintenance-~77/how-to-enable-logging~80) and see what is logged. You can also open a support ticket with us, and we can take a look for you.

You'll need to enable logging at level 4, per https://www.clientexec.com/members/knowledge-base/maintenance-~77/how-to-enable-logging~80, and then reattempt whatever you were doing to cause the error. Once that is done, check the log file.

This can be skipped, and just manually added. It's likely that the popen() function is disabled in php.ini, or the user PHP is running as can't access crontab.

Hi there, This appears to be a custom field. If it's attached to a product: Settings -> Products -> Custom Fields If it's on step 3, where a client enters their personal information: Settings -> Users -> Custom Fields.

We are pleased to announce Clientexec version 6.6.0 has been released as stable! As a stable release, Clientexec 6.6.0 is now recommended for all new and existing installations. Find out more on our blog!

Please allow me to sincerely apologize for the license outage today. We do take uptime very seriously and have never had such an outage like this in our history. Our team was made aware of the licensing outage this morning and quickly jumped into action to identify and resolve the issue. This...