Recent Topics

1 Jun 10, 2013 15:32    

So I have just moved some old blogs to a new server. And by old I mean 2.4.1, 2.4.2 and 2.4.5. Yes, I know. I did this by copying the file structure directly, and by making an import of the database from the old server.

They mostly work, and display fine, allow comments to work and the backend appears to work as normal.

However in certain circumstances the posts do not display properly. I don't know why. This is something fairly fundamental and the same behaviour shows on three different blogs, all different versions and with quite different skins.

What happens is that the title and comments display ok, but the body text of the post does not show up - unless there are any links inline, in which case these do show up by themselves. Here's an example. http://wildonwight.co.uk/news/index.php/2006/11/

This happens:
- When editing a post and looking at preview.
- After editing an existing post and resaving it
- When making a new post

I have checked the database and the `evo_items__item` posts all appear correct. They can be viewed in the backend without difficulty, and changes are saved as expected. There appears to be no difference in the database between the edited posts and the posts that were imported from the old server.

I have flushed the pre-render cache, and turned off apache caching.

Now I'm wondering what to do next.

2 Jun 10, 2013 16:12

Never seen anything like this before. Who's your new web host ??

3 Jun 10, 2013 16:58

It is a dedicated box supplied by Eukhost . I too have never seen such a thing - and as you know I've been messing around with B2evo for many, many years.

CentOS Linux 6.4
Linux 2.6.32-279.22.1.el6.x86_64 on x86_64
Apache version 2.2.15
PHP Version => 5.3.3

The old server was far, far older, and was running PHP 5.1.6

4 Jun 11, 2013 02:59

Can you try with a standard default skin?

Is it possible one of your skin files was harmed in the transfer? (FTP can be a bitch and sometimes produce 0 byte files)

5 Jun 11, 2013 11:51

Good idea, and one I also tried - when I preview any skin I get the same issue; plus even if I use a_noskin.php it's the same. And of course, this is happening on three different blogs, in three domains, all across the same server. See here: http://mattandcat.co.uk/reviews/

Last night I went looking for error messages, couldn't find any MySQL errors or PHP errors that might be relevant.

Today I'm considering trying to upgrade one of these blogs, which will be a pain as the skins are very much modified. But that's life, maybe the gods are trying to tell me it is time to move on. Any advice on upgrading from 2.4.x to 4.x? Will that work out of the box? I guess I might find out!

6 Jun 11, 2013 13:03

Your problem could still be explain by a faulty skin file (one shared by all the skins you tried).

Upgrade is supposed to work from any older version to any newer version, except if you have manually modified your db of course.

(Always have a backp of course.)

7 Jun 11, 2013 13:50

Excellent advice on the backup! I have now updated the smallest installation to 4.1 (it worked perfectly) and all is now well, although I expect a bit of skin reworking to be required.

I guess I'll just have to work my way through the others - thanks for your help FP.


Form is loading...