I'd need to know what you mean - do you mean the drop down menu on the top of WHMCS containing the settings or do you mean the J!WHMCS Integrator settings in the product? Also, are you using a custom WHMCS admin template?
You will need to reissue the license, but if you have done this and it isn't saving then it sounds like you need to disable JWHMCS from the backend of WHMCS (WHMCS > Setup > Addon Modules) then enable the Dunamis framework FIRST... then enable JWHMCS. The order matters.
If you enable debug in the settings of JWHMCS in WHMCS > Addons > JWHMCS > Settings > Debug you can visit the front end of the web site and add the following to the URL:
This will gain you access to the debug screen for JWHMCS on the front end, which will help troubleshoot connectivity issues.
1. I am not using a custom admin template. The settings that go to a 500 page are the ones in the whmcs jwhmcs addon package, otherwise joomla is fine. This remains the only issue.
2. License issue fixed (wooooot)
3. It is now starting to wrap properly although needs work to make it look right.
"If you enable debug in the settings of JWHMCS in WHMCS > Addons > JWHMCS > Settings > Debug"
this is the part where I don't have access to, even after following the instructions in part 2.
ERROR 500 - INTERNAL SERVER ERROR
The administrator has disabled public write access.
No Wrap and No Settings in whmcs addon
3 years 6 months ago #6788
Hmm... so when you access the settings in WHMCS > JWHMCS > Settings it returns a 500? What version of J!WHMCS Integrator do you have installed? If the front end is wrapping that would indicate to me that at least the URLs are correct to retrieve the Joomla site. If you upgraded from a prior version, be sure to remove form the WHMCS side the following:
WHMCS > JWHMCS > Settings it returns a 500 correct
I deleted the [WHMCS]/includes/api/jwhmcs*.php with no improvement
My clients have no access to header.tpl and footer.tpl which make the integration complete. Please help as I am getting lots of emails about this.
Submitting ticket on this as recommended.
For those customers that have encountered this issue, increasing the available PHP memory in your php.ini file resolved it for them. I've had a couple that were on a smaller VPS package with more limited resources and for those customers I had to hard code a correction (which I need to implement product wide yet).
If increasing the memory doesn't resolve it, please open a ticket and I'll be happy to take a look and try to get this solved for you.