Hey everyone. Thought I'd throw in what should be an easy question to some of you. :)

On a fresh install, it seems to install without a problem. Go to main page, header and footer displays but no left block. I can log in via /user.php and then adminster via /admin.php. Modules install fine and display fine on main page.

When in Blocks Administration it shows no blocks. (EG no User menu, no Login, etc). When I add a block nothing shows up. It says it saves (and is in the database).

Tried XOOPS 2.0.6, 2.0.7. On this machine.
Running Mandrake 9.2 - tested with:
Current (RPM installs):
PHP 4.3.3
MySQL 4.0.15
Apache-AdvancedExtranetServer/1.3.28
Register Globals: On

Tested on: Mandrake 9.2 with LAMPS built viahttp://lamps.efactory.de/e-lamps-1-3.shtml.
Was all the latest sources when I tried that one but had the same problem.

Has worked on a system with older verions of PHP, Apache, MySQL included in Slackware 9.2 (and I've had it up and fine on my old Redhat installs).

Oh also, it looks like the data is in the blocks table (xoops_newblocks). Both what should be installed and what I added.

Anyone with an idea on what it could be? It's starting to get frustrating! :) Seems like there could be some library I have that's conflicting or not working with how blocks are admin'd?

Again, I can administer most things, adding ranks works, groups, modules, etc. At this point it only seems to be the blocks.

Thanks for your time and consideration.

Do you get any error messages when turning on php debugging or block debugging?

Thanks for the quick response Bender. I had tried the other debugging but didn't see anything. The MySQL/Block debugging came up with something:

SELECT b.* FROM xoops_newblocks b, xoops_block_module_link m WHERE m.block_id=b.bid AND b.isactive=1 AND m.module_id IN (0,-1) AND b.bid IN (1,2,3,4,5,6,7,8,9,10,11,12,13) ORDER BY b.side,b.weight,b.bid
Error number: 1
Error message: Can't create/write to file '/root/tmp/#sql_52f8_0.MYI' (Errcode: 13)

Now it's just a matter of figuring this out. :) Is this a MySQL path thing or something else?

Quote:

make sure MySQL has permission to write to /root/tmp/

Excellent. Thanks guys! I now know the problem it's just a matter of finding a fix that works. Already tried a couple things. So just a little more fiddling around (creating a my.cnf file, i'm hoping). Thanks again for the quick and helpful responses.

I noticed when I googled for the problem another XOOPS user had the same problem, so I'll just reference that in here:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=19171&forum=1