deuts

@filosofo, this has been helpful in my case! thanks!

This fix actually worked for me! Thanks!

What about the indents? I hate it. I just hope to have the basic functionalities with “Press This”.

One P2 limitation is you can’t just simply post a link, or your post starts with a link. It’s because the title grabs the first “how many” characters of the post as the title, and wordpress doesn’t like it that the title starts with http.

I once had this problem. And yes, deactivating the plugins before clicking on the “Upgrade” button worked.

Actually, I just unchecked the “Rewrite Titles” option in the All in One SEO settings page, and everything seemed to work fine. Got rid of the problem.

But then, another problem arose. I’m using the post titles only to show in the archives, categories, tags, and search results pages. I unchecked the “Parsed Templates on Archive view pages” in the options. But lo and behold, the plugin parsed the template in the search results page (not in categories/archives/tags pages).

By the way, I’m also using the All in One SEO plugin, which I think usually overrides the title tag I defined in the header.php.

Uh-oh. My bad. Please forgive me for pointing fingers, when I should point my finger to me. It was not WordPress 2.6.2’s fault. It was not WPAU’s fault. It was my fault. I enabled the hotlink protection from the control panel the other day. And now my site is in a mess.

Investigating further, I noticed these lines in my .htaccess after the upgrade using the wordpress automatic upgrade plugin:

RewriteCond %{HTTP_REFERER} !^https://allsubdomains.deuts.net$ [NC]
RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC]

Multiply the first line with the number of domains and subdomains I had in my shared host (change the “allsubdomains”). There were more than 100 lines like that (the first line).

Somebody please explain what does this mean?

Thanks.

Yup, it was the WPAU that was the culprit (I’m not going to use that plugin ever again). To prove that, here what I did:

• Disabled the plugin (WPAU) and deleted the folder and other folders and files created by such

  result: same problem

• Downloaded WP2.6.2 and manually reinstalled in my current installation

  Result: same problem, couldn’t see the images.

• Went back to the 2.6 back-up i had (before running the WPAU script), switched it to the current directory and run

  Result: Everything seems went fine. I could already see my images. Some files were missing (of course) from my last upload after I upgraded to 2.6.2 by WPAU, so I just had to re-upload them.

  At first, one might think that WordPress 2.6.2 must be the culprit, but watch out for the next step.

• Now, upgrade manually

  Result: Everything’s fine.

Scary steps heh. Good thing I had back up copies.

Both directories have jpg files in them, including the /2008/03/ only that the 2008/09/ have no other non-jpeg files. It means it’s returning non-jpg files but not the jpg ones.

I actually have some leads here. It appears that the wordpress automatic upgrade plugin is the culprit. I’ve just deactivated the plugin and the images inside my stylesheet is not showing up anymore. Will try to reinstall manually and get back to on this issue.

Thanks for the help.

Yeah, they are there intact. It’s only that they are not viewable directly via web browser. They return a 404.

Also in the media files under the “Manage” Section, the files are there but no small thumbnails. Note: these are images uploaded even before the upgrade.

You can do that anyway in a single installation only. Just create posts and assign them to a particular category.

If you want posts under that category not to appear in the front page, you can do that as well. Just look for the “how-to” in the codex.

If you want posts under that category not to be included in your feeds, you can do that also. Just create a feedburner account install the feedburner feedsmith plugin (in wordpress) and forward your feed to your feedburner feed less the category (id) you want to exclude.

That’s the power of wordpress. A truly CMS to suit almost your needs. And that is the power of the community.

Yup. And that is exactly how they appear in the file structure inside my wordpress installation directory.

The plugin doesn’t seem to work in wordpress 2.6.2. I get the same error as gofree above.