Here is my issue....

I have started a Guild Alliance Site Untilizing your system (as I feel it is the best I have seen yet).

Now here is the first problem I have run into:

When uploading the roster from the armory (as I have to rename the site to the name of the new guild before I upload their roster from the armory (interestingly enough this work around works well but is slightly annoying should I forget to name the site back to Guilds United) but have found that although I can adjust everyones rank (which I put directly to member) but the Guild name can only be edited by them. I as the GM have no abliity to edit the guild name in any case. So my question would be is there a way to add this field as editable by me and better yet can it be imported from the armory Database?

You really probably want to use the ticketing system and open a feature request. What you really need is for Chops to start adding small tweaks for an alliance of guilds.

Something first would be the ability to define your site and a Guild Alliance. Then have it give you the ability to enter multiple guild names and define a server for each (typically they should all be the same but I have heard of alliances that are spread across servers). The character templates then needs a new field. Server name which should be directly associated with the guild for which the character was found. Then yes as you stated those 2 items would need to be retained as part of the import from the armory. Guild + Server + Numeric Rank. The Numeric Rank value comes in handy because all guilds have Custom Rank Names that map to a Numeric Rank Value. The Armory knows the Numeric Rank, DKP Profiler knows the Name Rank, and the DKPSystem site knows them both.

Indeed there are severa multi-guild (and possibly multi-game) features coming. The first of which is going to be Customizable rosters (each identified in their own way). This particular feature will work for both multiple guilds as well as single guilds with their own subgroups (Raid Groups, primarily).

However, as Saud suggests, I'd recommend making specific tickets for each particular feature, as I can then prioritize them individually. It makes it much easier for things to get done in a streamlined fashion that way, for sure.

Alrighty, this is good to know. I myself was hesitating on doing that as I didn't want to flood you with tickets as I've a few suggestions. I think they're good ones, I hope you do too. I look forward to the new features.

The last thing I want is for people to hold back on suggestions. Even if a suggestion isn't something that can be done in the immediate, it always helps to have them out there, concisely described and specced out.