next »

[mattelems]

Previously:

Yesterday, I checked my website, and it worked just fine.

Today, I get this:
Fatal error: Corrupted encoded data detected in /www/110mb.com/m/a/t/t/3/1/1/_/matt311/htdocs/index.php on line 0

The index.php modified date is correct, and it hasn't been changed since the last time I modified it (2 days ago).


I'm not sure if that's how 110mb always handles these paths, or if something has gone pear shaped.

Also, admin.php is no go as well, only it just won't show anything, error or otherwise.


I'm hoping this isn't, in fact, corrupted data, and I won't have to redo the site...

Now, it did it again.  I re-did the site from scratch this morning (23 Sept), and by 1:40, it was again corrupted.  Am I the only one having this issue?

[inp o҉rtb]

You might get a hint at what's going on if you downloaded and checked out that file in a text editor. You can also reupload and overwrite that file and see what works.

[mattelems]

Well, I tried to open it in notepad, and it somehow managed to freeze my computer to the point of needing a forced restart. 

[edit]
Well, I tried opening it in wordpad...  not much help:

Code:

ŒF¦H&ÎZÝ룛Cҡő͈_&)K–mlÎ^œÙÒžÙ“½÷P¢$Ê0`?p€c

I'd re-upload the file and see if that works, but I don't have a local copy to upload.

[Myles Grey]

Well, it looks like it's corrupted beyond repair. I don't know how that happened. You said:

I'm not sure if that's how 110mb always handles these paths, or if something has gone pear shaped.

You're talking about the file path right. That's just a standard file path for 110mb. It's the path on the server to your file, the files that are at the root of your site are usually in htdocs or at least for Apache servers.

[mattelems]

Well, it looks like it's corrupted beyond repair. I don't know how that happened. You said:

I'm not sure if that's how 110mb always handles these paths, or if something has gone pear shaped.

You're talking about the file path right. That's just a standard file path for 110mb. It's the path on the server to your file, the files that are at the root of your site are usually in htdocs or at least for Apache servers.

Yes, I was talking about the path given in the error.  I was more interested in whether the /m/a/t/t/3/1/1/_/ bit was right.  That answered, though, it seems I'm somewhat screwed.  Curses.  I'll leave this not resolved for another hour or so in case someone has another idea.

[mattelems]

It did it again.  At 9:50, I had it nearly completed, and decided to come back later.  At 1:40, it was corrupt again.  Any ideas as to what might be causing this?