The 3.1.3 bugfix/delayed feature release of Enthusiast is out! You can either pick up a complete installation zip or get an upgrade zip if you’re already running Enthusiast 3.1.2. Please run the upgrade file (upgrade_312_313.php) after overwriting the contents of your Enthusiast installation folder/admin panel with the updated files from the zip.
Changes for this version include:
Please let me know if you run into any bugs, but support and troubleshooting should continue to be at the CodeGrrl forums.
The 3.1.3 bugfix/delayed feature release of Enthusiast is out! You can either pick up a complete installation zip or get an upgrade zip if you’re already running Enthusiast 3.1.2. Please run the upgrade file (upgrade_312_313.php) after overwriting the contents of your Enthusiast installation folder/admin panel with the updated files from the zip.
Changes for this version include:
Please let me know if you run into any bugs, but support and troubleshooting should continue to be at the CodeGrrl forums.
The upcoming bugfix release of Enthusiast is really more like a delayed feature release. As such, the changes are somewhat significant (compared to previous bugfix releases) and so I’m doing an alpha test on my own websites at Aking Mahal. If while visiting the websites, you see any problems (especially with sending/receiving mail), please let me know! ♥
This test will continue for about a week before I release this bugfix. Just a heads up!
The upcoming bugfix release of Enthusiast is really more like a delayed feature release. As such, the changes are somewhat significant (compared to previous bugfix releases) and so I’m doing an alpha test on my own websites at Aking Mahal. If while visiting the websites, you see any problems (especially with sending/receiving mail), please let me know! ♥
This test will continue for about a week before I release this bugfix. Just a heads up!
A new bugfix release has been done for Enthusiast, raising its version level to 3.1.2. This bugfix release fixes a few dashboard presentational problems as well as some SQL injection vulnerabilities. An upgrade zip is also available at the download section, which contains files you will need to upload/overwrite your installations with–so please upgrade your Enthusiast installations now. :)
A new bugfix release has been done for Enthusiast, raising its version level to 3.1.2. This bugfix release fixes a few dashboard presentational problems as well as some SQL injection vulnerabilities. An upgrade zip is also available at the download section, which contains files you will need to upload/overwrite your installations with–so please upgrade your Enthusiast installations now. :)
It’s probably a minority, but WordPress users who are using third-party scripts (like Enthusiast) directly coded/included into their WP templates (read: not included as a plugin) who have upgraded to 2.1.2 and higher may experience problems getting their blogs to work. This is due to a conflict between the database link that WordPress uses and the database link that your other script is using. Users get a variation of the following line:
Warning: mysql_error(): X is not a valid MySQL-Link resource in (path) on line Y
Basically, PHP 4.x’s mysql_connect function—which lets the script talk to your database server—gets confused as to which connection is active. This has happened to me since the script I’m using for my downloads (here in this archive, in my wallpapers archive, and the various downloadable things in my other sites) is not set up as a WP plugin; I just do a series of includes in my WP templates. So when I updated to 2.1.2, I ran into problems.
I meant to address this earlier, when I came across the problem here in my tech blog/scripts archive, but got sidetracked. I was only reminded of it when I came across some open support posts at CodeGrrl.
The fix? It’s rather simple. After every chunk of code (or PHP include) you put in your WP template that accesses the database server (read: it generates the above error), add this line of code:
// reconnect to WordPress database
$wpdb->select( DB_NAME );(Actually, the first line isn’t that important. But comments are good for you.) This might not work for every instance; basically it just changes the database that the link connection is using. However, it’s possible that the new database user the connection is, ah, using, can’t access your WordPress database. So if the above doesn’t work for you, you’ll have to use something else:
// reconnect to WordPress database
$wpdb = new wpdb( DB_USER, DB_PASSWORD, DB_NAME, DB_HOST );That should basically restart the WordPress database. I haven’t tested the second option, so if you end up needing to use the second option and get problems, let me know. :)
If you’re using Enthusiast with WordPress 2.1.2+ and need a better example, here’s something that may be clearer:
// show joined listings
require( 'config.php' );
$show_list = true;
include $path . 'show_joined.php';
// reconnect to WordPress database
$wpdb->select( DB_NAME );Do the same for all the other snippets and you should be fine.
It’s probably a minority, but WordPress users who are using third-party scripts (like Enthusiast) directly coded/included into their WP templates (read: not included as a plugin) who have upgraded to 2.1.2 and higher may experience problems getting their blogs to work. This is due to a conflict between the database link that WordPress uses and the database link that your other script is using. Users get a variation of the following line:
Warning: mysql_error(): X is not a valid MySQL-Link resource in (path) on line Y
Basically, PHP 4.x’s mysql_connect function—which lets the script talk to your database server—gets confused as to which connection is active. This has happened to me since the script I’m using for my downloads (here in this archive, in my wallpapers archive, and the various downloadable things in my other sites) is not set up as a WP plugin; I just do a series of includes in my WP templates. So when I updated to 2.1.2, I ran into problems.
I meant to address this earlier, when I came across the problem here in my tech blog/scripts archive, but got sidetracked. I was only reminded of it when I came across some open support posts at CodeGrrl.
The fix? It’s rather simple. After every chunk of code (or PHP include) you put in your WP template that accesses the database server (read: it generates the above error), add this line of code:
// reconnect to WordPress database
$wpdb->select( DB_NAME );(Actually, the first line isn’t that important. But comments are good for you.) This might not work for every instance; basically it just changes the database that the link connection is using. However, it’s possible that the new database user the connection is, ah, using, can’t access your WordPress database. So if the above doesn’t work for you, you’ll have to use something else:
// reconnect to WordPress database
$wpdb = new wpdb( DB_USER, DB_PASSWORD, DB_NAME, DB_HOST );That should basically restart the WordPress database. I haven’t tested the second option, so if you end up needing to use the second option and get problems, let me know. :)
If you’re using Enthusiast with WordPress 2.1.2+ and need a better example, here’s something that may be clearer:
// show joined listings
require( 'config.php' );
$show_list = true;
include $path . 'show_joined.php';
// reconnect to WordPress database
$wpdb->select( DB_NAME );Do the same for all the other snippets and you should be fine.
I was waiting to get a few more bugfixes rolled into this release, but I decided I should just get this up first and then worry about the other bugs as they come in. I’m afraid the PEAR Mail issues still aren’t resolved, but I mean to get it sorted out a little better soon. I’m also looking into a better way to work on Enthusiast; if anyone has any suggestions, feel free to pipe up. ;) I’ve already started using Bazaar to track changes, so hopefully that helps.
The full Enth download has been updated to 3.1.1, and there is also a 3.1.1 upgrade zip file which will contain only the updated files.
The list of changes are below:
(more…)
I was waiting to get a few more bugfixes rolled into this release, but I decided I should just get this up first and then worry about the other bugs as they come in. I’m afraid the PEAR Mail issues still aren’t resolved, but I mean to get it sorted out a little better soon. I’m also looking into a better way to work on Enthusiast; if anyone has any suggestions, feel free to pipe up. ;) I’ve already started using Bazaar to track changes, so hopefully that helps.
The full Enth download has been updated to 3.1.1, and there is also a 3.1.1 upgrade zip file which will contain only the updated files.
The list of changes are below:
(more…)
I’m finally releasing Enth 3.1 after quite some time. :) I meant to release earlier, but because of some weather-related problems, I had to postpone it for a bit. I’m inclined to postpone it a little more but I figure I should just get this over and done with!
Enthusiast 3.1.0 has the following new features (for the full list, please view the changelog):
An online demo is, again, available at the Enthusiast features page. Feel free to check it out.
Online documentation of Enthusiast is also now fully available, and most the the new documentation has been delegated to it — if you see anything amiss there, please feel free to correct me. ;) Being around the scripts so much, I might sometimes skip over some documentation errors.
A fresh installation can be downloaded here as well as an upgrade script if you’re already using Enthusiast 3.0 — it contains all the new files (well, virtually EVERYTHING) plus a script you will have to run to update your database. Please go here to download the script; if you have having problems, try the quick download page.
Please note that some addons may not be needed anymore with 3.1, or might not work as expected, such as the conversion script from Fanbase. I’ll be working to update those in the next few days. :)
Much thanks to my beta testers — their help weeding out the bugs is greatly appreciated plus they got a lot of the kinks out. :) :x A few may remain, though, as with any script — if you find any, please feel free to head on over at CodeGrrl and we’ll see about that. :)
Please remember to back up your databases before upgrading your installations. ;)
Hope you guys like the new version. :)
I’m finally releasing Enth 3.1 after quite some time. :) I meant to release earlier, but because of some weather-related problems, I had to postpone it for a bit. I’m inclined to postpone it a little more but I figure I should just get this over and done with!
Enthusiast 3.1.0 has the following new features (for the full list, please view the changelog):
An online demo is, again, available at the Enthusiast features page. Feel free to check it out.
Online documentation of Enthusiast is also now fully available, and most the the new documentation has been delegated to it — if you see anything amiss there, please feel free to correct me. ;) Being around the scripts so much, I might sometimes skip over some documentation errors.
A fresh installation can be downloaded here as well as an upgrade script if you’re already using Enthusiast 3.0 — it contains all the new files (well, virtually EVERYTHING) plus a script you will have to run to update your database. Please go here to download the script; if you have having problems, try the quick download page.
Please note that some addons may not be needed anymore with 3.1, or might not work as expected, such as the conversion script from Fanbase. I’ll be working to update those in the next few days. :)
Much thanks to my beta testers — their help weeding out the bugs is greatly appreciated plus they got a lot of the kinks out. :) :x A few may remain, though, as with any script — if you find any, please feel free to head on over at CodeGrrl and we’ll see about that. :)
Please remember to back up your databases before upgrading your installations. ;)
Hope you guys like the new version. :)
Yesterday was quite a busy day for me! I added various pages to Indiscripts, notably in the new Documentation section of Enthusiast: Documentation for Enthusiast 2.x, Changelog (for 3.1, though, even though it’s not yet released!), and I’ve redone the Road Map a little bit. :) The latter is now clearer in terms of what plans I have for Enthusiast.
Notably, I have also uploaded online demos — this isn’t a new thing for Enth 2.x, but you may be interested in the online demo for Enth 3.x — after all, what’s loaded is 3.1, and not 3.0 :) It’s not yet released but I’m putting it up as a sneak preview of sorts. December is just a few days away, after all. These demos will “reset” everyday at 3am (server time) — all data will be deleted from the demos and reloaded with a “clean” install. Additionally, you won’t be able to send/receive email from either of these demos; for 3.x, certain sections are disabled.
If you’re interested in taking a peek of what’s up with 3.1, head on over to the Enthusiast features page to find out. :)
Yesterday was quite a busy day for me! I added various pages to Indiscripts, notably in the new Documentation section of Enthusiast: Documentation for Enthusiast 2.x, Changelog (for 3.1, though, even though it’s not yet released!), and I’ve redone the Road Map a little bit. :) The latter is now clearer in terms of what plans I have for Enthusiast.
Notably, I have also uploaded online demos — this isn’t a new thing for Enth 2.x, but you may be interested in the online demo for Enth 3.x — after all, what’s loaded is 3.1, and not 3.0 :) It’s not yet released but I’m putting it up as a sneak preview of sorts. December is just a few days away, after all. These demos will “reset” everyday at 3am (server time) — all data will be deleted from the demos and reloaded with a “clean” install. Additionally, you won’t be able to send/receive email from either of these demos; for 3.x, certain sections are disabled.
If you’re interested in taking a peek of what’s up with 3.1, head on over to the Enthusiast features page to find out. :)
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:
convertfanbase.php file from downloaded archive (so sorry!)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. :)
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:
convertfanbase.php file from downloaded archive (so sorry!)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. :)
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.
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.
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.
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.