rilex

There should be more to that error -- can you provide it?

Yes, all of the updates in en_US and Global_Updates are needed.

No, sorry... Also not sure what you're talking about

Guilds.aspx has been made into a ListView, with the changeset, 33571.

If anyone has a realm with a large number of Guilds (>500), let me know how this new ListView performs (ideally, it should load in <2 sec).

ies it is :-S

Hmm... Do you have Setup under Tools? That also requires gmlevel 5 to access.

I fount ver3.1.3 characters.data field offset have big diffrence from ver 3.0.x,

I want to know both 3.1.3 and 3.0.x characters.data offset detail,

but i cannot find it in forum,could you tell me where can i find it?

You should create your own thread for this, but look in the MaNGOS source file, UpdateFields.h. That will tell you the value for the version you have downloaded.

Is your account gmlevel 5? You can make that modification directly via the account table in the realmd database.

When looking at their character? Can you copy the entire error (it should be in Tools -> Error Log)?

You probably need to turn on the ASP.NET Session State services (in services.msc). I believe this release covers it:

http://micromanager.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=24818

Good catch.

Changeset 33240 should resolve that issue for two mail functions as well as an auctionhouse function.

I did a visual check of the SQL statements and off hand only found the 3. There may be more, but hopefully not.

Rev 33093 now includes some Statistics on Statistics.aspx! Thanks to bthallid for all of the code!

I guess I still don't understand. What do you mean by 'side'? You can enforce security via the menu layout (check menu.xml).

Yep, an fr-FR translation would be awesome!

There is no problems to make client pages using your code inside and separate it from admin commands ?

Not quite sure I understand what you're asking...

In this thread? No, it doesn't. But you can click the > arrow under the Last Post column when you're looking at the forum.

Given the non-existant version of PG2 (natch, "MoBlock") requires access to /etc, and on a shared system, you don't allow users to have write-access to /etc, that might be difficult to use.

That doesn't make any sense. Even if you don't import the MM db, you should be able to login given your connection strings in the web.config are correct (and MySQL is running, of course).

What trouble are you having with Setup.aspx? That is going to be key to resolving the issue with Characters, since you need to select which version of MaNGOS you're running (0.12, .13, or .14) which in turn defines what offsets are used to view character traits.

That is a newer table which is in the Updates folder. After you import the base MicroManager db, you have to import all of the updates in the updates folder.

Question, did you go through the Tools -> Setup page? Did you import the MicroManager database (and any applicable updates)?

A) You should create your own post for this, but

B) You shouldn't post about this. MaNGOS only supports up to GM Level 4 (which is the console itself).

Thank you!

FWIW, if you do:

SELECT `account`.*, `realmcharacters`.* FROM `account`

LEFT OUTER JOIN `realmcharacters` ON `account`.ID = `realmcharacters`.acctid

WHERE `realmcharacters`.acctid IS NOT NULL

That will force MySQL to use the secondary PK on realmcharacters (IOW, the acctid PK instead of realmid PK). Apparently MySQL will use PKs in the order specified, so acctid will never be used if realmid ISN'T used in your query. This is probably why I discovered that specifically creating an account on acctid resolved my perf issue (but the above query works around that).

I have the key, in Sqylog as:

Indexes: PRIMARY

Columns: realmid,accid

Unique: Checked

Also, here is the create script from the current realmd.sql:

--

-- Table structure for table `realmcharacters`

--

DROP TABLE IF EXISTS `realmcharacters`;

CREATE TABLE `realmcharacters` (

`realmid` int(11) unsigned NOT NULL default '0',

`acctid` bigint(20) unsigned NOT NULL,

`numchars` tinyint(3) unsigned NOT NULL default '0',

PRIMARY KEY (`realmid`,`acctid`)

) ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC COMMENT='Realm Character Tracker';

However, doing this join will still lead to a table scan and not using an index, hence the need for an index.

As long as the index is created, I'm happy

Bumping up.

Did you read the post two above yours? There is a link to the install docs.

I'd say just about every actively developed one works. E.g. mine (microManager), MiniManager, Spora IIRC has one...etc.