NicoMorrison

Enable Akismet, comes preloaded in WP. Will catch all comment spam, very very good.

Go to plugins & find Akismet & get an Alismet key (free) and turn it on, all you need to do.

Regards,
Nico M
London

Whoopee! I downloaded your latest from svn & although standard FTP faisl, the connection via SSH2 went A1! Read my private keyword fine & downloaded & installed the new plugin.

Thank you for your efforts, great to avoid FTP when possible.

Regards,
Nico Morrison
London UK

I’ll be short, V3.2.1 with 16 plug-ins up-to-date. Clean up-to-date Debian server also up-to-date.

I installed SSH SFTP Updater using the integrated WordPress installer which asks if I want to do it automatically and when I say yes, a screen appears asking for ftp credentials.
This is the screen which is replaced by SSH SFTP Updater which is very similar but adds the ssh options.
Should I be pulling this out of subversion somewhere? Maybe I got an earlier version?

Thanks & I’ll stay in this thread,
Nico M ??

I converted my Vandyke private key to openssh private key but yr prog says public/private key combination incorrect.

My key is RSA1024 & starts:

<snip>
—-BEGIN RSA PRIVATE KEY—–
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,F3A……..
…….99XduYgtt
—–END RSA PRIVATE KEY—–
</snip>

And have you actually tried the standard ftp option with a remote wordpress install? It does not work.

Hoping this helps your excellent project,
Nico M
London

I tried the Vandyke private key in yr plug-in with ssh2. I know from using putty that the key is not openssh compatible. Didn’t work anyway, only works with Vandyke products though connects fine with my Debian server with openssh.

What I mean by ‘standard’ is when you go to the automatic update of a plugin & click install & a browser screen asking for ftp details comes up.

When I activated yr plug-in it replaced that screen and since your ftp option did not work for me & I have the wrong key-type, I had to deactivate yr plug-in and then the standard screen reappeared and then I could update the needed plug-in ok.

Regards,
N

@terrafrost

That’s what I did, didn’t work. Says my username/password combination incorrect. Not so, tested with filezilla right away.

So to use the autoupgrade I had to deactivate your plu-in to get the standard screen for ftp update.

Thanks for the good work,
Nico M

Hi there,

I use SSH & SFTP quite a lot, Vandyke SecureCRT & SecureFX, old versions from 2003 or so but great interface & the RSA1024 key pair I generated with Secure CRT 5, was accepted fine by the debian server with all standard openssh …

Unfortunately the vandyke private key is not compatible with openssh so I couldn’t test your ssh2, which was what I wanted, I have to wait until I can convert the private key, later versions of SecureCRT can do that but it costs to upgrade.

So I went into your standard ftp option & it said my user/password were incorrect. I double-checked with filezilla and the info was correct.
Had to deactivate, but I like the idea so much, please carry on and meanwhile I’ll get me private key converted somehow.

Installed yr plugin via the blog upgrade btw, automatic, said it was v1.

regards,
Nico Morrison
London UK
https://theflowerraj.org

Removed the most recent post & all is OK now. I will now whack the saved html from that post into my local editor & find out what the blazes I did wrong & repost when corrected.

Take a look – there is nothing wrong with sidebar.php & it has not been altered.

Nico M

edit: was an unclosed <div= in the most recent post! Thank you for all your help.

Lesson is VALIDATE!!!!!

Nico M

I think it is in the most recent post, because:

All the other (3) posts look perfect when viewed in the archives:

https://nicomorrison.com/WordPress/?p=8
https://nicomorrison.com/WordPress/?p=7
https://nicomorrison.com/WordPress/?p=3

Only the most recent – go to the bottom & see the displaced bottom bar!

https://nicomorrison.com/WordPress/?p=11

MUST be the culprit – but I can’t see the error in the html & CSE Val throws up a zillion xml errors so I don’t know which the ACTUAL error-inducing error is.

Any suggestions what the error there might be please ??

Nico M

@t310s – do you mean sidebar.php in the active theme? it validates for closed unordered lists just fine??

@asechrest – I had a look at the very first post containing that <img ….
86 The tag: “img” has an XML style closing syntax for an empty element even though version: “HTML4” is not an XML tag language.

CSE Validator wrote that ……. this actually is the wysiwyg editor in WP doing the closing – not me sorry, so it aint that. Tried replacing with ‘classic’ html closing style – but no difference in sidebar pos. Doing any editing of the post inside WP reverted it to the xml style closing tab. wysiwyg editor must do its own validation.

Stil looking – it probably IS something in the Sidebar somewhere, either that or the last post after which the page went wonky.

Thanks a lot peoples – any other suggestions for further enquiry are welcomed.

Nico M

I can’t believe that I did some manual html editing & never validated it – what a wuss! Also though, embarrassingly, which page is this html error on? I checked the last posting & style.css & I feel silly I should know.

Which .php file is that error in?

I’m used to local html generation with Homesite, validate every change …. new to social networking & blogging & online editing. Confused but getting there of London,
Nico M