| Re: 2.0.13.2 to 2.3 upgrade. Blocks cannot be moved around |
| by sailjapan on 2008/10/6 2:56:00 Well, I ran the upgrade script as suggested, and was surprised to see it report that it was necessary to upgrade from 2.0.18 rather than from 2.3 Maybe this will fix things, I thought. No such luck ![]() I still have total hit and miss luck with the blocks, as before, the bottom left and right block settings squeeze over to the left of the page as if waiting for another block to the right. Newly created blocks may or maynot end up where I want them, and long established blocks are unpredictable. Wondering what on earth could be causing this... |
| Re: 2.0.13.2 to 2.3 upgrade. Blocks cannot be moved around |
| by Marco on 2008/10/4 17:20:27 try first to run the upgrade script again |
| Re: 2.0.13.2 to 2.3 upgrade. Blocks cannot be moved around |
| by sailjapan on 2008/10/4 17:13:22 That was quick Nicely done!Do you think I should Quote: will have to force back your actual website release number to your old XOOPS instance release number |
| Re: 2.0.13.2 to 2.3 upgrade. Blocks cannot be moved around |
| by Marco on 2008/10/4 17:08:41 now you can test with 2.3.1RC |
| Re: 2.0.13.2 to 2.3 upgrade. Blocks cannot be moved around |
| by sailjapan on 2008/10/4 14:23:30 Cheers for the advice Marco, and the offer of help John. I'm wondering, is there a way to force XOOPS to regenerate it's blocks? Since I last wrote, I've noticed that the block behaviour is stranger than I thought. For example, the bottom blocks crowd them selves over to the left, almost as if there were an option to add a third block, over on the right. I also find that if I clone a block, there's a 50/50 chance I can move it around as I would expect... I've actually found rather a nice theme that I'm going to try and use, so it won't be the theme I need to modify. Which files might I go and have a look at to see if I can sort out the blocks. Maybe some tables need adding into the db... what should the table "block_module_link" hold? |