n2972s Posted January 4, 2009 Author Share Posted January 4, 2009 Make sure this is the root path /clientarea/modules/admin/enom_extended/smarty/admin_homepage.php There should be something else before /clientarea I would imagine. 0 Quote Link to comment Share on other sites More sharing options...
merlinpa1969 Posted January 4, 2009 Share Posted January 4, 2009 should be /home/redrat/public_html/clientarea/modules/admin/enom_extended/smarty/admin_homepage.php according to the paths in the error 0 Quote Link to comment Share on other sites More sharing options...
sparky Posted January 4, 2009 Share Posted January 4, 2009 Sorry to but in here RedRat: use the full path as above, delete all files from the template_c directory and clear your browser cache (Mine would not work until the browser cache was cleared) n2972s: Well done... keep up the good work 0 Quote Link to comment Share on other sites More sharing options...
redrat Posted January 5, 2009 Share Posted January 5, 2009 Hi folks. I've done all of that but to no avail. Here's the full story; 1. Installed v 1.0 beta and that worked fine. 2. Upgraded to v 0.2 (most recent release) 3. The following errors then occured; Warning: Smarty error: file:/clientarea/modules/admin/enom_extended/smarty/admin_homepage.php is not readable in /home/redrat/public_html/clientarea/libs/Smarty.class.php on line 1095 Warning: Smarty::include() [function.include]: Failed opening '' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/redrat/public_html/clientarea/libs/Smarty.class.php on line 1925 4. Browser cache cleared 5. templates_c cleared 6. Path correct IE: /home/redrat/public_html/clientarea/modules/admin/enom_extended/smarty/admin_homepage.php 7. All files uploaded in binary. 8. All of the above repeated with same result. What am I missing here? The first version worked fine and it only broke when I installed the new version. I might just try reverting. Damn! 0 Quote Link to comment Share on other sites More sharing options...
redrat Posted January 5, 2009 Share Posted January 5, 2009 Resolved thanks so much to n2972s helping out directly. A very big 'up' to you, Gustave. I am very much obliged. All is well. Regards, Chris 0 Quote Link to comment Share on other sites More sharing options...
Roger Posted January 5, 2009 Share Posted January 5, 2009 Well Beta 0.2 did some weird stuff on my server. Beta 1 worked just fine. The update process produced this error: Encrypting eNom Password ... FailedYou have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '©¿V' WHERE `setting` = 'enompassword'' at line 1 Try as I may, the password will not save via the configuration link. Viewing the modee_settings table shows an encrypted user name and a blank password field. On a lark, I manually entered my enom PW in the enomusername field. Went back to the configuration link... and there's encrypted data in the user name area. Copy and paste that info manually in to the tables enompassword field, back to the configuration link and change the encrypted info in the user name area back to the unencrypted name. Back to the database. Now there is an encrypted enomusername and an encrypted enompassword present. Tested and it works. That is too weird... it would seem on my server the issue is Beta 0.2 not accepting input for the password via initial setup and subsequently the configuration link. It's just plum weird entering "in the clear" info in the table fields and it showing encrypted in the configuration link. Thats only the user name. The password entry doesn't work at all. 0 Quote Link to comment Share on other sites More sharing options...
n2972s Posted January 5, 2009 Author Share Posted January 5, 2009 Roger, Thank you for the report, what is weird on my first glance at this is that if it did not work in the password field it also should not have worked in the username field. Regardless, your lark is the way to go around that in this BETA version is correct. The encryption method will be different for future versions and get rid of the special characters since I can see that causing problems for some users. Your work around which was the way to fix encryption errors in this BETA will definately be gone down the road. Thank you for testing the script. 0 Quote Link to comment Share on other sites More sharing options...
Troy Posted January 6, 2009 Share Posted January 6, 2009 n2972s: Thanks for this amazingly useful module! I've just installed it and can see it will be very handy for us. I for one will be willing to pay for it, once it's complete. 0 Quote Link to comment Share on other sites More sharing options...
Roger Posted January 6, 2009 Share Posted January 6, 2009 Roger, Thank you for the report, what is weird on my first glance at this is that if it did not work in the password field it also should not have worked in the username field. Regardless, your lark is the way to go around that in this BETA version is correct. The encryption method will be different for future versions and get rid of the special characters since I can see that causing problems for some users. Your work around which was the way to fix encryption errors in this BETA will definately be gone down the road. Thank you for testing the script. This is a great script bud... I'd pay for it as well. Just wish I knew why my server got the weird stuff or maybe I'm the only one speaking up.... 0 Quote Link to comment Share on other sites More sharing options...
n2972s Posted January 6, 2009 Author Share Posted January 6, 2009 This is a great script bud... I'd pay for it as well. Just wish I knew why my server got the weird stuff or maybe I'm the only one speaking up.... Thanks, So far you are the only one, it may be that no one else has said anything... If you want PM me and I can investigate but I will be changing this around on the next go around and I do not believe you will get that error any longer. 0 Quote Link to comment Share on other sites More sharing options...
Roger Posted January 6, 2009 Share Posted January 6, 2009 That's what testing is all about n2972s. Sort out the probs and such. Anxious to see the next one. 0 Quote Link to comment Share on other sites More sharing options...
apollo1 Posted January 9, 2009 Share Posted January 9, 2009 Thanks for the update. I rm -rf my existing enom_extended dir and then unzipped this one to the same location. When I accessed the utility from my WHMCS, it upgraded itself and everything is working fine. Where is the enom id and pw located? I am wondering how it was able to 'upgrade' itself when I had completely wiped out my enom_extended dir tree beforehand. 0 Quote Link to comment Share on other sites More sharing options...
fetish-hosting Posted January 9, 2009 Share Posted January 9, 2009 Hi Installed this simply and easily and it worked first time - great module Thanks very much Regards Ian 0 Quote Link to comment Share on other sites More sharing options...
Roger Posted January 9, 2009 Share Posted January 9, 2009 Thanks for the update. I rm -rf my existing enom_extended dir and then unzipped this one to the same location. When I accessed the utility from my WHMCS, it upgraded itself and everything is working fine. Where is the enom id and pw located? I am wondering how it was able to 'upgrade' itself when I had completely wiped out my enom_extended dir tree beforehand. They're located in the modee_settings table from your initial install. 0 Quote Link to comment Share on other sites More sharing options...
apollo1 Posted January 9, 2009 Share Posted January 9, 2009 They're located in the modee_settings table from your initial install. Gotcha, thanks. I suspected it might be in the db, but I wasn't certain. 0 Quote Link to comment Share on other sites More sharing options...
Gx- Posted January 11, 2009 Share Posted January 11, 2009 Okay... interesting issue... I installed everything... everything looks good... except no enom data is displayed? database is populated, user/pass verified, ive used the enom api for a long time on this server... so it should check out... and the addon looks nice... like i can see where the info should be... but its just not being displayed? just blank values... any ideas? 0 Quote Link to comment Share on other sites More sharing options...
zigzam Posted January 11, 2009 Share Posted January 11, 2009 Okay... interesting issue... I installed everything... everything looks good... except no enom data is displayed? database is populated, user/pass verified, ive used the enom api for a long time on this server... so it should check out... and the addon looks nice... like i can see where the info should be... but its just not being displayed? just blank values... any ideas? Did you upload in binary mode? 0 Quote Link to comment Share on other sites More sharing options...
n2972s Posted January 11, 2009 Author Share Posted January 11, 2009 I installed everything... everything looks good... except no enom data is displayed? database is populated, user/pass verified, ive used the enom api for a long time on this server... so it should check out... and the addon looks nice... like i can see where the info should be... but its just not being displayed? just blank values... any ideas? Try this: Go to the configuration tab of eNom Extended and select "No" for Curl Verify SSL. If that does not work please PM me as a deeper look may be needed. 0 Quote Link to comment Share on other sites More sharing options...
DeSoto Posted January 11, 2009 Share Posted January 11, 2009 Great work! Donation sent as I know how it is to work so hard on something and no REAL appreciation shown. Thanks! 0 Quote Link to comment Share on other sites More sharing options...
Gx- Posted January 11, 2009 Share Posted January 11, 2009 (edited) Nope, turning off SSL was one of the first things i tried... I attached a screenshot to display what i was getting. And im pretty positive i uploaded in binary mode... as the settings section does function... I can change the config and user/pass Edited January 11, 2009 by Gx- 0 Quote Link to comment Share on other sites More sharing options...
n2972s Posted January 11, 2009 Author Share Posted January 11, 2009 Great work! Donation sent as I know how it is to work so hard on something and no REAL appreciation shown. Thanks! I appreciate it! I attached a screenshot to display what i was getting. And im pretty positive i uploaded in binary mode... as the settings section does function... I can change the config and user/pass Binary is probably okay, you are not connecting to eNom for some reason. I am sending you a PM with the link to download some files that will allow us to figure out what is going on. 0 Quote Link to comment Share on other sites More sharing options...
danami Posted January 12, 2009 Share Posted January 12, 2009 (edited) There should be no need to have to enter your enom username/password again for this module. They are already stored securely in the database. Use this function to grab them: /** * Gets our enom settings from WHMCS * * @return array */ function get_enom_settings() { $data = array(); $query = "SELECT setting,value FROM `tblregistrars` WHERE registrar='enom'"; $result = mysql_query($query); while ($row = mysql_fetch_array($result, MYSQL_ASSOC)){ $data[$row['setting']] = decrypt($row['value']); } return $data; } Edited January 12, 2009 by danami 0 Quote Link to comment Share on other sites More sharing options...
n2972s Posted January 13, 2009 Author Share Posted January 13, 2009 Thank you for the suggestion, but I am going to continue having the person enter the information on install. 0 Quote Link to comment Share on other sites More sharing options...
SilverNodashi Posted January 13, 2009 Share Posted January 13, 2009 This is a great addon, thank you 0 Quote Link to comment Share on other sites More sharing options...
Watersweb Posted January 13, 2009 Share Posted January 13, 2009 I keep getting this error when the cron runs: Any ideas? <br /><b>Warning</b>: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11) in <b>/home/watersbi/public_html/clients/modules/admin/enom_extended/cron/transfertracking.php</b> on line <b>7</b><br /> Can't connect to database server : Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11) FTR, I am not getting this error when any of my other cron jobs run for WHMCS. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.