Enthusiast 3.0.x maintenance update, and 3.1 update

Entry posted on 2006-11-15 10:28 am

I’ve released another maintenance update of Enthusiast 3.0, and we are now up to Enthusiast 3.0.2 — this release contains the following changes:

  • Fixed bug that adds an owned listing item to your list even if creation of the database table for it failed
  • Fixed SQL bug on creation of a new listing
  • Changed admin panel title to a more readable/serious format :P
  • Removed misplaced convertfanbase.php file from downloaded archive (so sorry!)
  • Automatically lowercased email in Jem’s join form fix

Enthusiast 3.1 beta is almost over — now it’s just having to write up the online documentation for Enthusiast 3.x that’s making the release a little bit longer. Work and various offline concerns still keep coming in, but I’m aiming to release by first week of December — it could be earlier, but there it is. :)

Belated Enth3 update

Entry posted on 2006-11-05 11:35 am

I decided to put together a very belated update on Enth 3.0.x — the newest stable version is now 3.0.1, which contains the login security and join form fixes. You do NOT need to download this if you have previously applied the fixes already; this is just so that new downloaders will be getting the patched files immediately.

Release candidates ++

Entry posted on 2006-11-05 9:06 am

I’ve decided that instead of stressing over beta testers, I’d adopt what I’ve seen elsewhere — release candidates for Enthusiast 2.1.8 and OhNo 2.2. I am still debating over either opening the bug tracker my Enth 3.1 beta testers and I use to general signup for reporting bugs (or open something else, I don’t know), or if it will be another can of worms I am continually opening. I have the nervous idea that opening it up will have people asking for support there, submitting bugs that are not well-worded and then leave it open without any explanation or help to actually replicate it, and so on.

I’ll confess that doing support stuff wearies me out. I’d love to help, but it also drains me quickly, and if I’d end up doing it in sheer number I tend to run away very fast. (Which is why the support forum is there, so please go there!) So I’m very hesitant about this whol bug tracker business, even though I know that logically, should be beneficial for everyone.

Who knows, maybe today I’ll decide to open it and get it up. (But I really have to work on my writing for NaNoWriMo, really.)

In any case, there it is, two new release candidates for Enthusiast 2.1.8 and OhNo 2.2, which are basically security fixes for both scripts. The optional password modification has also been updated with a syntax error bugfix, but the modification has also been incorporated into 2.1.8 as well. :)

For the moment, if you find bugs in the release candidates for Enthusiast 2.1.8 and OhNo 2.2, please contact me at scripts-AT-indisguise.org about bugs you find in both releases. I will still not answer support queries about Enth 3.x or help installing/configuring Enth 2.x — the “upgrade” needs only an overwriting of files from your previous installation, after all. If you ask, I will just direct you to the CodeGrrl boards :)

Additionally, Rachel has created a TCG Script transformation for Enthusiast 2, which allows you to use the script as a TCG script. She has sent it aaages ago but it got buried by the mail. :( Note, however, that the base install she used was 2.1.7 (the stable version, but with some security issues with login and forms) so you can either wait for an update of her modification or patch your installations. :) You can find her modification at the Enthusiast 2 modifications page, at the bottom.

Lastly– and this I can’t reiterate enough– back up your databases before trying these release candidates.

Enth 3.1 Update

Entry posted on 2006-11-01 5:19 pm

From the last post I made, I’m proud to say I’ve made a little headway with the errors. Or, it’s not somewhat more manageable, and I really am hoping to get this all wrapped up.

Additionally, I realized that for Enthusiast, I have never really made much use of the versioning system that I use! You see, the version of Enthusiast that’s out right now — 3.0.0 — is named so because of the system I’ve decided on: the numbers in the version number mean major.minor.bugfix. From there, you can deduce what level of revisions the release is. Enthusiast 3 is a lot different from Enthusiast 2, and Enth 3.1 has a number of more features than 3.0, but is not “major” enough to warrant a new top-level version number. Now, the last digit is supposed to be for bugfixing. What’s happening is that I’m releasing mods instead of updating the actual version, which was admittedly rather daft of me. :p

So now I’ve decided that I will be releasing Enth 3.1 soon. Right now, the only things that are holding back the release are the PEAR Mail issues (which we’re hopefully wrapping up somewhat) and the fact that I need to get documentation up! There are upgrade scripts ready and upgrade documentation ready for the download, but I was hoping to actually be able to release online documentation as well.
So that’s the sitch right now regarding Enth 3.1 :)

Also, watch out for a new section of sorts sometime soon.

The wait that is Enthusiast 3.1

Entry posted on 2006-10-28 1:27 pm

I would like to apologize for the insane wait for Enthusiast 3.1 (if there are people waiting!) — I would like to be able to give all sorts of reasons, and I could (so much has happened offline) but it all boils down to not having either the time or the motivation to work on continuing to fix bugs for Enth 3.1. If it’s not one, it’s the other.

It’s very frustrating even for me, as a big part of me just wants to get this over and done with! To keep everyone in the loop, the problem “happened” when I attempted to use PEAR’s Mail package to handle sending emails from Enth. It wasn’t in the “planned” changes, and it was admittedly a mistake to insert it in the middle of beta testing (bad Angela!) — I should have held on to it for Enth 3.2 or something. I apologize. At the time, it was a GREAT IDEA, hence my excitement in getting it into Enth.

Why use PEAR Mail instead of however Enth does it right now? Sending mail using PHP’s native mail() function is great if you’re sending one or two. But the problem happens when you’re sending to all members, for example — it’s highly likely that PHP will time out because it’s taking a long time to send all the emails. (I would go into a more techie explanation, but never mind.) But ever since I used PEAR Mail in one project, I’d loved it ever since because mail sending is so much faster. You won’t notice it when you’re sending an email to one person, but when you’re sending to all members, the time difference is noticeable.

The problem is that a few beta testers are having problems with it. It apparently won’t send email notifications. To me, it happens on and off — sometimes I get an email, sometimes I don’t. Or maybe I get everything, but I just don’t notice (whenever I test it, it works; I can’t check every new member against an email in my mailbox, boo).

So, that’s the problem. I admit, if I had a solution in mind already for this problem, I would be much more motivated to work on it, but because I never seem able to replicate the actual problem, it’s a BIG damper. :P I plan to keep trying, though, rest assured. :)