ENOM SSL provisioning date

[rota919]

This is bugging me every time I look at an account in my system.

I see the bug has been confirmed a year ago and a statement had been made by "Nate C" that "our release team understands what is needed to fix this".

 

Well since 04-01-15 there has been several updates for WHMCS and still now fix....

maybe it was just an April fools joke posted by "Nate C".

 

How about giving us an update that includes this fix please? Surely thats not to much to ask.

 

Link to original post

http://forums.whmcs.com/showthread.php?99159-EnomSSL-module-SSL-Provisioning-Date-displays-as-00-00-0000&highlight=ssl+provisioning+date

Edited April 14, 2016 by rota919
added link to original post

[WHMCS John]

Hi,

This matter has been assigned case #MODULE-6226 by our development team and triaged with a Low/Minor priority.

The reason for this that the provisioning functionality of the module is unaffected. However you can rest assured the case is still opened in our system and will be addressed in a future release.

 

Thanks for your continued patience and my apologies for any inconvenience caused in the meantime.

[rota919]

Understand but having a 0000/00/00 displayed as the provisioning date doesn't help the client to understand that his certificate was provisioned successfully and I have to explain every time that my billing software has a bug in it.

That helps a hell of a lot for trust.

 

I would much rather have an app that doesn't look the best but is actually fully functional without such obvious issues.

 

So in my opinion it is affecting the provisioning functionality.

 

Can the dev team at least remove the relevant code in the template so that it presents better or give me a pointer where to look for it in the "six" template?

[brian!]

Can the dev team at least remove the relevant code in the template so that it presents better or give me a pointer where to look for it in the "six" template?

I don't use the module, but looking at the screnshot from the other thread, I would guess that it's in six/clientareaproductdetails.tpl

 

            {foreach $hookOutput as $output}
               <div>
                   {$output}
               </div>
           {/foreach}

if you wanted to remove the incorrect '0000/00/00' date, you could try modifying the template...

 

            {foreach $hookOutput as $output}
               <div>
                   {$output|replace:'0000/00/00':''}
               </div>
           {/foreach}

if that works, then you might be able to remove the entire line with a more expansive Smarty replace, but i'd need to know the value of $output to write that.

[rota919]

Hi Brian,

Thanks for your input.

 

I am looking at the six/clientareaproductdetails.tpl template but not 100% sure where to edit.

I will have to take some time out somewhere and check out all the possibilities and see what happens.

Don't want to break something else in the process.

[brian!]

I am looking at the six/clientareaproductdetails.tpl template but not 100% sure where to edit.

it's at line 89 in v6.3.1

 

I will have to take some time out somewhere and check out all the possibilities and see what happens. Don't want to break something else in the process.

the only thing that it will do is remove instances of '0000/00/00' - everything else should be shown as before.

 

if it takes out things that you think it shouldn't (e.g somewhere where a 0000/00/00 would make sense), then you can fine tune the replace to be more specific - but I suspect it's going to be the easiest solution until WHMCS fix the source of the issue.