Momekh

I got an email 5 minutes ago, saying:

Alert generated at Wednesday 3rd of September 2014 at 04:59:27 AM

Warnings:

* Modified plugin file: wp-content/plugins/akismet/readme.txt

Is it the same repo mirror confusion? Or should I run for the hills? I dont like hills.

I am using JetPack from WP along with this. And FB scraper tells me that now there are two OG:URL values. Jetpack is adding on its own… can’t figure out from WHERE, and how can I fix this ??

That’s effectively what I’ve done now. I have used Chip Bennet’s advice found on this page. The way it’s done is that it technically does render the front-page.php file useless.

Now I really don’t know why I have it in the theme. ??

Thank you so much for your advice @emsi. It helps me gain a bit of confidence in what I have ended up doing.

Isn’t that the million dollar question!!

I kid you not, this will probably be the first and the last time I have them!

For the reason as to why I have them? Well, WP had them. I thought they were there for a good enough reason for me to emulate.

I am right now thinking that at most I need a home.php to stylize the blog list view. And then have as many template I want for the front page display, that the user can set in the Setting>Reading section.

What would you recommend @esmi?

Well I am trying to REMOVE all media buttons except the IMAGE button. I am trying to do this within the P2 theme.

Wonder how can I filter these? hmmm…

I tried Cruth’s advice, as plugins usually are the culprits in these cases (which is understandable of course).

but if it is any help, I had the wp-spamfree plugin that was causing the trouble. I also run a few blogs and many of them were not upgrading automatically.

Wp-spamfree is a super plugin, I think, as it makes spam fighting very easy. But they have not upgraded their plugin to work with wp 3.0. which is bad. :/

anyways, hope this has helped.

@mercime: you, my friend, probably have a cape around your back, don’t you? Thank m’man. I renamed the theme folder, and then FTP’ed the original theme folder, but for some reason, WP automatically changed to keep the ‘renamed theme folder’ as the selected theme. Thanks to you, now I know WordPress jogs too :/ ??
Check out my site at https://www.feztrick.com ??

GREAT post! Exactly what I was looking for! YAYYY!

I was facing the same problem. I googled it and it seems Fantastico has a bug, this EDGE is something not many people can relate to (read: they dont know what the hell it is). And the point to note in all of the above is that I said “I WAS facing a problem”… now I am not!

tada!

While installing WordPress from Fantastico, DO NOT install in a domain’s root. Instead specify a folder. I tried that and it worked. I hope it works for you guys.

I am using CPanel X with Fantastico and I was installing WordPress 1.5. The first installaion came ok. It was the second installation that gave me this error.

hope it helped
peace
M.