Upgrade/merge/modify whmcs templates

bobbravo2 commented 9 years ago

You'll be creating two new folders, mirroring the new WHMCS V6 structure:

ZIP of the two sets of new templates here: http://cl.circletr.ee/3s2V0H1O1I0g

Final structure

+new directory+ /src/templates/five +new directory+ /src/templates/six

domainchecker.tpl
- Add a {$namespinner} tag inside of the relevant
  element.
clientareadomains.tpl
- Add everything inside of the {if $enom_transfers} ...... {/if} tag, modifying the class names, and structure to mirror the new templates from WHMCS.
clientareadomaindetails.tpl
- Add code from inside {if $enom_srv }....{/if} into the new sub-menu structure, as above. (old template had this submenu item added inside of
enom_srv.tpl -> Should be OK with a normal copy
How to test
1. Domain checker page should show namespinner results after running $_POST.
  - Also, verify that clicking a name response checkbox successfully gets added to cart.
  - If not, WHMCS may have modified the html input names.
2. Transfers
  - Manually submit a new domain transfer order under a whmcs user account
  - Going to the domaindetails page for that domain should show our pending transfers view (even if it has an error in it... as this is a test mode transfer)
3. SRV Records
  - Add a new enom domain order, and activate the domain order, submit it to eNom
  - Verify that this domain now shows our "SRV Records" menu item for the domain index page (NOT domain detail page...)

anatoliyrazin commented 9 years ago

Notes and questions:

I assume the folders are not to create, but to replace existing "five" and "six" directories and then update with four files from repo "default" directory
The guidelines for files are great for "five", but not perfect for "six" since the code there is totally different.
What is the actual deadline for milestone? Asking because GitHub reports past due. Anyway unless something does not work, the testing should be quick after the proper clarification for 1 and 2.

bobbravo2 commented 9 years ago

Correct, at least I think so... You will in fact create new directories inside of the repo, the ZIP provided is the reference of the distributed WHMCS templates. The final repo format should only contain the files we've modified, not adding the entire WHMCS templates. Just wanted to be clear ;-)
Yep. That's why you're doing the merge :-) If you have questions about how to run the merge, please let me know.
As soon as you're able.