Great!!! Does this mean that the Miserable Users hack will be re-released for HTL soon?

finally got it installed great hack, makes life lots easier.

kura, please disregard my last question. i got it working and its a great mod!!!!!!! thanks

Glad you got it working :)

SloppyGoat: Yeah, I'll release the HTL version of the Miserable Users for vB3 soon :)

just installed on rc4 its pretty easy :)

Cool! Nice work!

Quick question : when running the install sequence, if the install doesn't finish for whatever reason then it's listed as unfinished. You then have 2 options, delete or continue - but how do you edit the hack if there was a mistake in it? ie. set it back to it's pre-installed status? Maybe deleting it from here would do it but I don't want to risk it right now...

Altough this hack has a great potential there are some issues with it also. I've installed the shoutbox hack and it does not remove pre-installed tables properly so the install stops and it leaves an unfinished hack. Removing the tables by hand in the database is to difficult, it installs tables all over the place. When an author does not write a text install/remove instruction your database is full of useless tables or you must have a backup with all tricky consequences eventualy when you want to dump this. I hope this incident with the shoutbox is a single event and i hope all HTL hacks will have a uninstaller/install textfile also.

@ TheMasterG:
Nominally, a hack should not be installed when there's a mistake in it. There are various ways of going around the 'safety measures'. The easiest would just be to manually update the hack's status in your database. To do so, verify what hackid it has, then run this query:
UPDATE hack SET atstep=-1 WHERE hackid=THATHACKID
Note 1) keep in mind that if you're using a table prefix, you have to add that before "hack";
Note 2) replace THATHACKID with the hackid, of course :)

Other ways are, for example, to just delete it, upload the new .htl file (the one that isn't faulty), import that to the database (NO real install!), then edit that hack and disable all steps that you've already done, and then save & do a real install for that hack, thus continuing where you left off.

@ NuclioN:
I don't really get what you mean... :(

I found a bug in the generation of phrase XML files.

When you have a set of phrases that use the hack prefix and the phrasetype prefix of your custom prefix, along with a group that only have your hack prefix (i.e. are meant to go into the custom grou), two sets of <phrasetype name="xxx"> would appear, and only the second group would be imported - thus meaning that a lot of phrases aren't installed properly.