themaclady

OOohhh thanks ! It worked. I simply went into the cpanel into the IP Deny button and voila. The feed cannot be grabbed.

Thanks! I think if I use the domain name it can’t pick up the feed, make sense?

I would hate to block it guessing at the IP because that would prevent others from seeing the site.

I don’t care if they SEE the site, just don’t want them embedding the feed.
Now I have to figure out how to enter than in the cpanel, or I’ll have to get a copy of the htacess file (without the dot!) and alter it, put it back and rename it.

(I learned it will be invisible otherwise!)

Oh it works fine… but if not included that means I constantly have to move copies of the theme around.

I just wish it were a bit wider… otherwise it’s perfect for a blog that you just want to set up to match a color or two….

What version of WP are you using?

As someone who has experienced all sorts of hacks, I can tell you how to upgrade easily but the first thing you should do is ask your host to help you get back in, perhaps change the FTP password and Admin password.

The server acted fast and I have everything back. He simply put up this graphic and set permissions so you could not see anything else. I’m not sure why he can’t be traced. He is doing untold damage.

https://foliza61.com/yvz/as.jpg

But thankfully all that work was left. The server did act fast which helped.

Turns out it was a flaw in the LINUX kernel… which could explain why this particular guy has hacked 11,000 sites, around 200 of them just today….

https://zone-h.org/archive/published=0/page=15

Now it will be interesting to see if when 2.9.3 comes out I can update from within the controls.

I could just delete it again before I do?

EUREKA!!!!!!!!!!!!!!

I got it to work.

I uploaded a BLANK file, set the permissions for 777, fixed my permalinks which TOOK without giving me that bizarre ‘please edit your file now’ and then I fixed the permissions back to tight again.

WHEW.

It filled in its own directions for WP.

?? ?? ??

Another file on the SAME server has 644 and looks like this:

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName somedomain.org
AuthUserFile /home/username/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/username/public_html/_vti_pvt/service.grp

But that looks like it’s only for FrontPage… with the vti stuff and all.. It doesn’t even have WP in there.

Another one on the same server looks like this and is 644 and works.
(I don’t know why it says FRONTAGE, I don’t use that yuck!)

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName xxxxxx.org
AuthUserFile /home/xxx/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/xxx/public_html/_vti_pvt/service.grp

I just looked at another file similar and it just has

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /concord/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /concord/index.php [L]
</IfModule>

And of course the particular URL in the REQUEST.
The Perm is 644

So what is wrong with this?
I knew someothing was wrong when I could not update it via the control panel… what a pain in the butt!

I should have been able to go from .1 to .2 in a snap.. dammit.

Or just change the date to reflect the new date, but that will change the link too.

I added the stuff they said to, was I supposed to delete anything in there too?

It’s in /public_html/ but not named ‘wordpress’… would that have screwed it up?

This is not working for me… what now?

Here is the procedure I found works for me, if not updating from the control panel (such as from 2.9.1 to 2.9.2) or moving to a new server.

Back up the DB file to your HD (ex: news.sql)
Back up the customized theme files to your HD (most times I use the default theme)
Back up the uploads folder to your HD and note its location (uploads)
Create the DB/User with the same names if this is completely new and note the username prefix must be different in your wp-config.php
Rename the old wordpress folder (for example, mine might be ‘news’) to something like news (old)
Upload the new wordpress folder and rename it to news
Replace the theme and upload files
Log in and select the theme

Access the MyPHP Admin and IMPORT the sql file with the data in it for new server … the backup and restore panel won’t work even if you named the DB and folder the same I found.

If this is on the same server that you are upgrading manually with a whole new version of wordpress that doesn’t allow you to do it from within the old, you can just use the ‘restore’ feature in the backup panel, but chances are you won’t need to. YOur files should show up and theme should be restored.

Now if your archives cannot be brought up or your .css file lacks the update button, you need to go in and make sure your folders are permissions 755 and files 644 or 666 (you can change back to 644 after updating)

This is what I have had to do.

NEVER USE 777

Corrections and additions anyone?