whenyou

YES
Try si-captcha-for-wordpress
Plugin Ver 2.5.2 works for me while using WP 2.9.2
It works for WP 3.0 RC1 and 3 also but I have other issues there.

It works very well – Almost totally killed spam-bots. One got through in the last week or so.

WP 3.0 RC1 and RC3 have given me a similar problem:
In the Dashboard screen, plugin updates are shown as being available but when we click on the Plugin radio button to select the List of Plugins with their Active/Deactivated status, there is no indication of WHICH plugins have updates available.

I installed RC3 to see if the problem was still there:
It showed one (1) of two updates was available in the Dashboard view but no indication in Plugins as to which (1) was available.

I had previously Deactivated and manually deleted the two Plugins and re-uploaded earlier versions of the two plugins I was testing with.

At this point I have reverted to WP 2.9.2, having tested quite happily and safely RC1 and RC3 but I have to say it sucks. That simple facility of being able to see WHICH Plugin updates are available is now totally missing in BOTH Release Candidates I have tested.

OK! I had a similar problem wil All-In-One-SEO (sp) and it took a while for my Host and I to sort it out. The instruction that I (me) was given, to pass to my Host, was as follows:

1 “This error indicates that your host has enabled the PHP open_base_dir setting on your server. Your host needs to add your WordPress and/or All in One SEO Pack installation folder to the allowed paths for this setting (i.e., add the file path referenced in the error as ‘not within the allowed path’).

The open_base_dir setting is primarily used to prevent php scripts for
a particular user from accessing files in another user’s account. So
usually, any files in your own account should be readable by your own
scripts.
For Reference:
https://www.php.net/manual/en/features.safe-mode.php#ini.open-basedir

2/You’re getting the error because one of the changes in this plugin is to have the SEO class in it’s own file. Including that class isn’t
allowed by your paranoid host. You’re going to have this problem with a lot of plugins.

& etc.

We got it sorted but I have not tried any ‘automatic upgrades’ since then. My Host left SEO Upgrade in the installed condition (he also found a syntax error in a folder name, which caused a problem for the Plugin to be able to ‘Activate’. Specifically, a _ instead of a – in the file or folder name of all-in-one-SEO.php [for instance])

I’m happy with my Host but Plugin Programmers, I think, should be aware of this type shortcoming and rather than advise us to go to THEIR preferred Host, give practical advice and some notice of this particular bug. I looks from this thread that I am not the only one taken by surprise.

https://www.wenublog.com

OR do I go to wp-admin/header.php

and change require_once

to

require_twice

??

Not confused, just stupid but curious cos I wanna.

Mine says:
Fatal error: Call to undefined function: add_thickbox() in /home/owner/domains/theblog.com/public_html/wp-admin/page-new.php on line 10

So. What is suggested that I add inside () at add_thickbox()

I found line 10 in wp-admin/page-new.php

buuuuuuut . . . .

suggestions? nebodeh?

Romulo, did you try selecting All Posts – to see if you can view them and update their published status?

Because Published # is a seperate link to All Posts.

2.6 seems to have some weird hasserlz

Seems like everything with the Automatic Upgrade Plugin is fine if you are an expert on WP and have everything ‘cleaned out’ properly before you use the Plug-in. But for those of us who just use Blogs and want minimum fuss upgrading to the next version – Auto-Up is a dog!

The alternative, manually uploading a thousand files to about fifty folders is a bugbear. So I am left with a message on my Dashboard asking me to please upgrade to 2.6 – and there are only 2 files in my installation that are still 2.5.1 (wp-login.php and wp-settings.php)

It’s assumed, when 2.7 comes along, that won’t work because 2.6 never got back from the bathroom.

I bet itsa guy thing! ggrrr

Raidie

Ya! Think I’ll stick to developing omelettes.

Rai

Hi Gangleri ! I’ll go to that link and see if it makes sense to meh.

I’m really the one who puts the tracklist together for our music player!! But I know about as much as Guran (meaning my mistakes are just as disasterous and my lucky guess as sweet) ??

What I can’t understand is why it calls for ssl in the first place. It’s a feature on the page intended for the use of visitors (I think – it was on the old blog but that ran in Joomla.) Should have no reference, I feel, to either login or page loading at the site.

RaiofOz

Wow! What a beautiful response, arwen54 !

You are so coo ??

RaiofOz

I found the “Audio Player” was mean and only wanted me to play one track. Currently I HAVE only one track playing but if you go to the IMVU Tweaks site you can use their FREE Code Generator (you WILL need to have the actual mp3 files at your host so you can insert the URL).

Then the process I use is to insert the code just near the bottom of the ‘sidebar.php’ file in my Theme folder. I use Orangepeel 10 or something, which is a folder in the Themes folder, alongside Classic and Default (from memory).

Usually I delete the IMVU promo text and the <CENTER> script from the Code but I credit IMVU with the generator where we print the Track List.

You will have to be able to:

Upload MP3 files of your music to your Host. (Might as well be your blog host as that usually makes play/downloads faster)

Copy the URL from your Host

Past the URL into the code generator (there are others but the one at IMVU Tweaks allows you to put a long playlist onto your page)

Copy the Code from the IMVU Tweaks generator. I copy them to a word document so I have the code safely for future use.

Backup the file you plan to put the code into – such as sidebar.php I mark the originals such as /sidebar-orig.php That way, when I make the inevitable boob – I can go back to where I started. ALWAYS BACKUP

Paste the Code into whichever element of your page where you want the music player to appear. I use the sidebar but it’s a matter of personal choice and also may depend on what Theme you choose.

Have fun and keep the volume down or the neighbours will want to come over and drink rum.

OK – another day. Where I am at.

At present I have all the files in the public_html folder at ver. 2.6 except wp-login.php and wp-settings.php

When I upgrade those I get the fatal error message. It says:

Fatal error: Call to undefined function: force_ssl_admin() in . . . and then refers to the two above files, via their root and dependencies.

ie. Fatal error: Call to undefined function: force_ssl_admin() in /home/Host/domains/OURblog.com/public_html/wp-login.php on line 15

The identical problem crops up in ‘settings’ at line 390.

Any suggestions? Or if there was a way to disable that call to ssl, would that simply let the login routine run until it found the NEXT inconsistency?

The blog is up and running (has not auto-upgraded on login) with, so far as I know, only these two files still being at ver. 2.5.1

*confused*
*unhappy*

That was easy!
Now I am TOTALLY confused.
It’s only 45 minutes to tomorrow sooooo

yep ??

Ahhhhh *smiles*
My FTP Transfer thingy has spaces for “Host” “Username” and “Password”

PORT will throw me but it’s only a speriment eh?

hmm

The FTP I use in my Direct Admin only allows selection of files – as many as I like but still I hafta do the job one sub-folder at a time and there are lots!

I know the basic procedure – just you use the term ‘upgrading with FTP’ as though I could simply select, for instance, wp-includes , with all its sub-folders and upload it directly to my domain. I’m not sure that’s even possible, given the access protection protocols of WP and my Direct Admin application.

I’ll ‘speriment’