IainPurdie

Wow – I see what you mean. Very unusual.

If you go to “Manage” in the Admin panel, are the pages still there? If so, have you tried re-publishing them?

Evyatar,

I had a look and it’s a little strange…

I can see no comments. I posted one of my own and I can see that, but no others at all. I did notice, however, that your Meta section on the right includes “Register” as an option. Do you have the option set that all users must be registered before they can leave a comment? It is not an option I have ever used, so I wonder if the system is “broken” slightly?

As I am not registered, it is still letting me place a comment which it should not. But as I am not registered, it does not show that comment. Which is correct. Only it should not have let me place the comment in the first place!

I would suggest looking at the options you have selected under Options / Discussion in your Admin. It could simply be you have a conflict of options.

I’d be happy to help more, but I am off for dinner! I will be back in a while, though. Feel free to contact me via my blog (www.moshtour.me.uk) as it’s sometimes difficult to keep track of the topics on this forum!

Iain

I’ve had similar problems with 2.5 on one host, but not on another. Changing permissions has made no difference.

One thing to try, which did work for me:

1) Ensure you are not trying to upload the files into a folder that already exists. Let the system create a new one. It does mean that your files may be separated from the old ones, but that’s a small price to pay to get it working!

2) Make sure your path for the directory does *not* begin with a “/”. This will ensure that you create the directory within the WordPress folder structure to which you should have access.

Sounds to me like the edit-form-advanced.php file could be corrupt. Did you upgrade by uploading all the WordPress files via FTP? Sometimes this isn’t the most reliable way (even if it’s the only method available – I know it is for me).

I am, of course, assuming that the error message means that the error is with that file and not with the one where the function it’s trying to call resides…

I’d try re-uploading this file individually and overwriting the one that’s there. See if that helps. If not, try uploading the whole wp-admin folder again, and if not *that* then the rest of the core files.

I don’t think it’s possible to do an automatic redirect as you’d have to use the .htaccess file (you don’t have access to it) or mess with the DNS (you also don’t have access to it).

The best bet would be to put a post at the top of the “old” blog, redirecting people to the new one. Simple as that. It’s what I did for my old Blogger ones.

Unless someone else wants to correct me!

1) Not too sure – I’m on 2.5.1 and haven’t seen that message before (other errors, yes – but not that one)

2) Won’t be a database update issue if your friends can see it. Could be a caching issue with your browser. Try going to the post and hitting CTRL-F5 to force your browser to reload the page rather than drag a copy from the cache.

No worries. Best of luck!

You could always try connecting to the DB another way? Do GoDaddy supply you with PHPmyadmin or anything similar?

*blushes*

No problem – sometimes all it takes is another pair of eyes.

If you can, mark this problem as “resolved” over on the right there – thanks ??

By “install” I assume you mean “upgraded”? May be useful to know what version you upgraded from ??

And what is the URL? Again, can often help to have a look at the problem directly.

I’d listen to the error message it gives you – the database could be down, in which case check with GoDaddy’s support. You might find it pops up by itself shortly!

Ah – you’ve put GoogleAds in there. The gap corresponds with your Google Ad code. Firefox is ignoring it, whereas IE is rendering the empty space:

<div class="entry">
					<div style="text-align: center;margin: 3px;"><script type="text/javascript"><!--
google_ad_client = "pub-";
google_alternate_color = "FFFFFF";
google_ad_width = ;
google_ad_height = ;
google_ad_format = "_as";
google_ad_type = "";
google_ad_channel ="";
google_color_border = "";
google_color_link = "";
google_color_bg = "";
google_color_text = "";
google_color_url = "";
google_ui_features = "";
//--></script>
<script type="text/javascript"
  src="https://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>This is a test</p>
<p>This is a test</p>
<p>Test</p>
				</div>

Looks like an Internet Explorer problem. I’ve checked it with Firefox (2.0.0.14) and it’s fine and dandy. View it with IE6 and I get the same problem as you.

Have you made any changes to the default templates?

Go to Settings on the right hand side.

Select Discussions on the large menu on the left that appears

Third section down (“Before a comment appears”) ensure that the top box isn’t ticked (“An administrator must always approve the comment”)

May also be worthwhile clearing the other two boxes.

Quick check – do you have Pretty Permalinks on? That is, within WordPress should you be able to go to (example):

www.myblog.com/2007/10/04/this_blog_post/

If so, check to see that you don’t have a similarly-named directory existing in “real” terms. I’ve found that this can cause problems with WordPress’s “virtual” system, though I normally get 403 Permission Forbidden errors.

Hope that makes sense!

I know this was posted 7 months ago, but it doesn’t hurt to put the answer in. I found a few solutions including one that involved a small edit to a core file. Worked a treat, but meant you had to re-edit with every upgrade.

The following one means editing one of your template files, so as long as you don’t over-write these during an update then you’re fine.

Go to the solution at https://www.ads-software.com/support/topic/116985 and scroll right to the bottom. The solution there is to remove only “Private:” but can easily be adapted into two functions to remove both “Private:” and “Protected:”.

I found placing the routine right at the top of the Kubrick file (just after the opening php line). You can edit the file through Theme Editor within WordPress. No need to fiddle around with text editors and FTP.