I was so brain satuated I forgot to include the table prefix for the modified sql statements. I'll fix that and look into the sorts.

Version 1.1.8 fixes the sql prefix and re-adds the sorting method for class type. Thanks for the early catch and thanks for the feedback folks.

So, now that we have the alternates system in, the next feature update is going to concentrate on class max limitations for events. So, I have not begun to design the feature and would like some feedback on this. If you had your chance to add 3 modifications to the calendar, what would those modifications be? List them in order from highest priority to lowest priority.

Feedback helps folks. :)

Some tweaks to the system that I plan to make:

• Adding an alternate checkbox underneath the allow signups to allow for alternates on a per event basis. (I figure this will help for those guilds that dont' want to allow alternates on events)
• An extra column noting whether or not the character is a main or an alternate.

Thankyou, you are so fast :) i will report any bugs i find here,

So, my thinking is this:

I'm going to work on creating custom calendar fields that will be stored in the calendarcustomfield table. These will be something along the lines of:

Instance Name
Type of Event
Loot Rules
Maximum Participants
Druid Max
Hunter Max
Mage Max
etc.

• When you create an event, the instance name would have a drop down that shows you all of the instances currently in Wow.
• The type of event would state whether or not it's group or raid or other.
• The loot rules would be a "fill in box" that you can put in what you want.
• Maximum Participants would be a "fill in box" that you can put in ## number.
• Druid Max, Hunter Max, etc. would be the class maximums that would be a fill in box that you could input ## number.

I have some of these fields already created on my calendar and I can actually add these fields to the addon and then program the code based on the inputs you use. It would be a bit more polished this way.

Any objections?

sounds great, espcially the Instance name, That would be good.

I'm working on polishing up the URL parsing code so that if your browser timeouts when trying to connect to the armory, you don't overwrite your existing armorydata with empty data. This has been an uncommon occurrence but it has happened. While the issue is only temporary because as soon as you reconnect to the armory, the correct data is updated correctly, it's still an annoying thing to see happen. The data is stored in a vbulletin table but the replacement data being directed into that table is the problem. I will keep you posted.

Version 1.1.9 has been updated.

This version should fix the small issues present with timed out armory URL parsing and fix any empty data values from hitting the armorydata table which would overwrite existing "good" data.

As always, if you find any issues please report them to me asap.

Thanks,

I've installed and reinstalled everything several times now but when I create an event and check the sign up box I get a blank page. If I refresh the page I get a download for the calendar.php which contains this code:

ok this fixed the problem:

uninstall, open up the xml file, and edit it like so:
Find: $xml = file_get_contents($url);
replace with:
// $xml = file_get_contents($url);
// Nah, let's cURL it instead
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_URL, $url);
$xml = curl_exec($ch);
curl_close($ch);
// cURL'd

The error you were having in your original thread is due to your hosting provider not having your php.ini settings set to allow_url_fopen.

You need to contact your hosting provider and have them set the allow_url_fopen option to on.

http://us.php.net/filesystem

I will not be changing this piece of code to support any curl functions. fopen is pretty straightforward and easy to code and not all hosts have curl installed in their libraries. Also, curl is more beneficial if you have to authenticate and we don't really need to authenticate to this data. But, in case others have an issue with being able to connect, your "workaround" is definitely a good note for others.

Thanks mate.