just for info: HiveMail 1.2.2 has been released today, it is a bugfix version for 1.2.1

[] don Julio you will need to add {} around the database call. [/] <br />Why? Everything seems to be working fine for me now. What file would I do this in anyways?

in doapproveuser.php because otherwise you will get an error when deleting a user in the queue.<br /><br />This makes me think I forgot to put in the zip the instruction for dodeleteuser.php for deleting the email account when you delete a user.

[]Charles said:<br />in doapproveuser.php because otherwise you will get an error when deleting a user in the queue.<br /><br />This makes me think I forgot to put in the zip the instruction for dodeleteuser.php for deleting the email account when you delete a user. [/]<br /><br />I believe you're right about hte dodeleteuser.php, because when I deleted test users I set up, they still had their email accounts.

Just finished looking over the HiveMail 1.2.2 upgrade and line comparing the 3 change files in the integration hack. There does not seem to be any changes in the three 1.2.1 unhacked files and the 1.2.2 unhacked files. <br /> <br /> - conclusion - <br /> <br />Hacks to those files should not harm the upgrade and, for that matter - it appears that you can copy your hacked files and replace the 1.2.2 upgrade files. <br /> <br />When my upgrade to 1.2.2 is complete I will post any complications with the hack and 1.2.2 - if in fact there are any. <br /> <br />I do anticipate having to run the SQL command at the bottom of the hack instructions to change the prefix... <br /> "Replace all "vb_" parts with "ubbt_"" ... as the upgrade states that there are mySQL changes. <br /> <br />Tom

Post deleted by Tom_H

Charles - <br /><br />Great work on the "login name" as "email address name". It works great and is exactly what I needed to make this complete for my site.<br /><br />Kudos and Thank You for all your help.<br /><br />Tom

There is a problem in the SQL part of the hack as combined with upgrade to 1.2.2.... <br /> <br />Here is a sample of the SQL error given in HiveMail when checking new messages: <br /> <br />---ERROR--------------------------------------------------- <br /> <br />MySQL error: You have an error in your SQL syntax near 'SET hm_emails = hm_emails - 1 <br /> WHERE hm_userid = 7 <br /> ' at line 2 <br />MySQL error number: 1064 <br />Script: /hivemail/read.email.php?hivesession=6b3cbc5cf552b93379b15d3b50c41f8b&messageid=58&hivesession=6b3cbc5cf552b93379b15d3b50c41f8b <br />Date: September 15, 2003, 5:14 pm <br /> <br />Invalid query: UPDATE <br /> SET hm_emails = hm_emails - 1 <br /> WHERE hm_userid = 7 <br /> <br />---ERROR--------------------------------------------------- <br /> <br />Tom

Post deleted by Tom_H

OK - I found it... <br /> <br />MySQL error 1064 is a parse error and since there wasn't anything blatantly wrong in the "read.email.php" hack I decided to replace the integer '1' with a variable set equal to one. It worked and now no errors. Charles please update the zip with this change as it will not affect HiveMail 1.2.1. <br /> <br />Here's what you need to do... <br /> <br />---CHANGES-------------------------------------------------- <br /> <br />In read.email.php <br /> <br /> <br />---END CHANGES---------------------------------------------- <br /> <br />With this change everything seems to be working perfectly. If I come across any more errors I will post them and hopefully post the corrections. <br /> <br />Tom

[]Charles said:<br />just for info: HiveMail 1.2.2 has been released today, it is a bugfix version for 1.2.1 [/]<br /><br />Are there going to be any problems using this same hack w/ version 1.2.2 of Hivemail? I would hope not. I seem to have everything working correctly now and am almost afraid to tinker with any of it.

now since it only fixes some bugs and doesn't intervene in hacked part you should have no problems.

[]Charles said:<br />now since it only fixes some bugs and doesn't intervene in hacked part you should have no problems. [/]<br />Thanks! I wish Hivemail was a little more forthcoming about what's going into future version similar to the changelog for threads that Infopop maintains, as well as letting us know what bugs were fixed w/ the new version.

When editing and updating my profile I encountered this... <br /> <br />--ERROR---------------------------------------------------- <br />Fatal error: Cannot redeclare hivemail_check_name() (previously declared in /home/tomh68/public_html/hivemail/includes/ubbthreads_plugin.php:113) in /home/tomh68/public_html/hivemail/includes/ubbthreads_plugin.php on line 111 <br />--END ERROR------------------------------------------------ <br /> <br />I have changed "require" to "require_once" in changebasic.php and editbasic.php yet still get the error. <br />Any suggestions? <br /> <br /> <br />--EDIT----------------------------------- <br /> <br />Happens on all users when I try to <br />upgrade personal settings. <br /> <br />--END EDIT------------------------------- <br /> <br />Tom

ok tom will look into it

The only call to hivemail_check_name() in the hacked files occurs in adduser.php line 230.

try using require once in ubbt.inc.php

BINGO!<br /><br />Nice work Charles - It is nice to know that I was on the right track.<br /><br />Should I change the other files back to 'require' or leave them 'require_once'?<br /><br />Tom

I've upgraded hivemail to version 1.2.2 and it's still working like a charm <img src="/forum/images/graemlins/smile.gif" alt="" /> Just remember that you have to replace vb_ with ubbt_ in the login template because the upgrade script reverts it back to the original version.

donjulio -<br /><br />Did you need to make the variable change in read.email.php - or did yours work without the change?<br /><br />Mine needed the fix because I was getting and error when attempting to read new emails - just wondering if yours did the same?<br /><br />Tom