Ladies, and gentlemen, may I present to you, WRX 1.73 RC1!

Aside from the many changes from Roster 1.7.2 to 1.7.3 I have made a few other changes for this version of WRX.

-Added RealmStatus block and MOTD block
-Fixed a minor bug in wowdb.php causing update deletions to fail
-Added French, German, and Spanish translations of WRX
-Revamped the User Login functions
-Changed WRX Version to reflect latest Roster Version
-Fixed wrapping for guildbank in inventory mode
-Fixed issue with View Account in Xoops displaying as a blank page
-Fixed issue with character pages not displaying properly (PVP data, spelltree data)
-Added Xoops Group Permissions
-Fixed issue with path error on install
-Added the ability to upgrade from WRX 1.25->1.73
-Addon Table Uninstaller (currently uninstalls tables for SigGen, AltMonitor, EventCalendar, Madeby, and RosterGallery)


You can download it at the Dev Site
Also you may download WRX 1.73 RC1 from the Downloads Section here!

*** An install error may occur on versions of WRX 1.73 RC1 distributed earlier! This has been fixed and the downloads have now been re-packaged. If after install you can not see any config setting in roster config then please download the patch HERE. ***

I can't wait.

This is just what the Doc ordered lol

can't wait to test this out for you.

Thanks

A Demo Roster is now available on the Dev Site. Also if you notice the Dev Site is also using the MOTD Block and RealmStatus Block!

-The Roster may not appear properly on all Xoops Themes!

Please note that with the addition of page permissions I have restricted anonymous users from accessing Roster Config, Roster Diagnostics, and the Update Page. It even gives a wonderful redirect error and everything. I really hope you all enjoy this new version. Please remember to report bugs so they can get fixed.

Hi,

After upgrading to 1.73 I get this message when entering the main index of the roster.

Code: Select all

Fatal error: Call to a member function stopTime() on a non-object in /usr/home/web/web176621/footer.php on line 33

However, I can go through the admin panel and get to the config area just fine.

Any ideas?

Also, in Firefox I don't get the text or image up in the MOTD block, and in IE it only uses the image, regardless of whether I set it to text in the config.

I've seen that error a few times before during development. However Xoops never really seemed to care so I have ignored it. However if it is causing a Fatal error it might be time to fix it.

What version of Xoops are you running and what does your footer.php file say at line 38? Any extra info you can give would help.

With Firefox I'll have to start testing for errors, and I'll have to see if I can add a text function in the block options. Currently the block just links to the realmstatus.php as an image.

I'm running 2.0.16 of Xoops. Line 33 says:

Code: Select all

   $xoopsLogger->stopTime( 'Module display' );

Problem with linking to an image in the MOTD is that if it's too long it'll mess up the page width.

Really love the job you're doing on this by the way. Thanks a LOT for the effort. Next you may want to port a DKP solution, eh?

Ok, after further research of the code I have determined that the StopTime() error is caused by the XoopsLogger, your particular error is that the logger may not have run the startTime( 'Module display') in the header.php file. That is most likely why it gave you an error.

Also, I am aware of the MOTD block being too long in some cases, I'll have to look into making some kind of two line text wrap for it as a block option.

Finally, I would love to do a DKP solution for Xoops, but WReX is the next item on my list, followed by UniAdmin X and UniAdmin eX. However I can tell you that there were two other Xoops Roster projects started after mine that hoped to incorporate EQDKP into their module, though I have seen nothing from these developers.

Look at the realmstatus code for line wrapping in GD

Code: Select all

        // Ouput centered $server name
        $maxw = 62;

        $output = '';
        $box = imagettfbbox($serverfontsize,0,$serverfont,$realmData['server_name']);
        $w = abs($box[0]) + abs($box[2]);

        if ($w > $maxw)
        {
            $i = $w;
            $t = strlen($realmData['server_name']);
            while ($i > $maxw)
            {
                $t--;
                $box = imagettfbbox($serverfontsize, 0,$serverfont,substr($realmData['server_name'],0,$t));
                  $i = abs($box[0]) + abs($box[2]);
            }
            $t = strrpos(substr($realmData['server_name'], 0, $t), ' ');
            $output[0] = substr($realmData['server_name'], 0, $t);
            $output[1] = ltrim(substr($realmData['server_name'], $t));
            $vadj = -6;
        }
        else
            $output[0] = $realmData['server_name'];

        $i = 0;
        foreach($output as $value)
        {
            $box = imagettfbbox($serverfontsize,0,$serverfont,$value);
            $w = abs($box[0]) + abs($box[2]);
            writeText($top,$serverfontsize, round(($topwidth-$w)/2), 54+($i*8)+$vadj,$textcolor,$serverfont,$value,$shadow);
            $i++;
        } 

Ok, hopefully the final version will have all the kinks worked out of the RealmStatus block and MOTD block. I was up until 6AM working on the blocks trying to make them fully compatible with the Roster settings pertaining to them. Now my only obstacles are making the RealmStatus block appear when the MOTD Block is active. (It just returns Unknown status with no graphics) However, each block on it's own performs exactly as it should, with the exception of no text wrapping on the MOTD yet. So, there will be text support for MOTD and DIV Container support for RealmStatus. If anyone would care to help me just send me a message.

mdeshane wrote:Ok, after further research of the code I have determined that the StopTime() error is caused by the XoopsLogger, your particular error is that the logger may not have run the startTime( 'Module display') in the header.php file. That is most likely why it gave you an error.

Well, it worked fine in your last version, just came up now. I'll look a bit around tho to see if I can find anything.

And thanks for the heads up on that Zanix, I'll check it out.

Edit: Well, I looked a bit and on line 112 and 113 in my header.php is

Code: Select all

$xoopsLogger->stopTime( 'XOOPS output init' );
$xoopsLogger->startTime( 'Module display' );

So I'm stomped on that one. Has to be somewhere in the new code.. I dunno.

Have you tried doing an uninstall, re-upload and re-install? I can't get the error to come up at all. Previously when it refered to a stopTime() error it was just a misc. xoops error and never broke the module. However I haven't seen this error since earlier development. Being as I can't re-produce this error it is difficult to properly diagnose the error. If there is any more info you could give me about your server or site that could possibly help me re-create this it would be helpful.

I was hoping I wouldn't have to, but I guess I will. Have you ran this module as an upgrade to your prior versions? Hmm.. there's no need for InnoDB in wowroster, is it? The host this site is on (no, I wouldn't have picked that host if it was my choice) doesn't support InnoDB. Other than that... standard up-to-date mysql and php install.

I tested the upgrade feature as extensively as possible. I had success 98% of the time. Recently the only upgrade troubles I have seen are resulting from 2 tables not being updated (used MySQL IGNORE to keep it from stopping other queries) and from Data Corruption during file transfer. Both are easy to fix, for the tables not being updated you can manually enter the changes in to the DB (adding Primary Keys to speed up database transactions). For the second, it is easily solved by re-uploading the module.

InnoDB is not needed or required, Roster can run on MyISAM which is the default Database Engine for MySQL 3.23 and up.

Ok, here's a seriously tricky one. I uninstalled the module. Deleted the entire thing and uploaded a fresh one. Installed again. Worked fine, woohoo! Left a message to my guildies that they should now be able to start uploading their stuff.

Ok, fast forward about 1.5 hours, I get a mail from one of them telling me the same message is back. I go in to try, and sure enough, there it is.

Meaning, I'm stomped. Again. I have no idea what's going on.

Edit: I just thought of one thing. Could it be a memory issue? I only have 8 megs available to me from the host, which is giving me problems a couple of other places, but then it tends to tell me that it's out of memory, and that is not the case here.

This is a tricky one. I doubt it's a memory issue as it would of said it's out of memory. However that could mean one of two things. Either you are experiencing some database corruption, most likely around the Xoops module table. Or, it could be corrupted Xoops files that didn't quite come out right in the transfer.
You can check for database errors in various ways, you can use PHPMyAdmin by going to the table structure, selecting all tables, then in the "With selected" drop down box select "Check Table." It should then process for a bit and come up with a list of all your tables. If all your tables are error free it will say OK next to each one, otherwise it will say an error next to the damaged table(s). If you have damaged tables, go back to the Structure view and select the damaged table(s), then in the "With Selected" drop down select "Repair Table" and it should repair any damaged tables. Otherwise your hosting service may have a table check and repair utility built in to your Control Panel.
Alternately if you do not want to go through all that, there is a new Xoops Care module available from Instant Zero that will help maintain and repair your Xoops Site. The download for that is available via Xoops.org.

Other than that there isn't much I can tell you. The one post on Xoops.org pertaining to this problem was posted 2 1/2 years ago and was never replied to. I hope you can get it running properly.