Socially Uncensored

Akismet which is managed and developed by WordPress… I was confident it uses reCAPTCHA

SOLUTION: You’ll need to change the url to fit your needs ??

# Secure SSL (HTTPS)

RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# Force Non WWW

RewriteCond %{HTTP_HOST} !^sociallyuncensored\.net$ [NC]
RewriteRule ^ https://sociallyuncensored.net%{REQUEST_URI} [L,R=301]

# BEGIN WordPress

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

# END WordPress

I cannot remember what it was, but adding

define( 'CORE_UPGRADE_SKIP_NEW_BUNDLED', TRUE );

Blocked more than just Akismet (its documented somewhere, but I can’t seem to locate it at this time). I believe the skin / style maybe one of them.

This isn’t ideal (good) for those of us who want all the newest bundled goodies (new skin updates for example) or view what other bundles may be included.

So adding this code limits a complete beta testing (in my opinion).

As someone else said…

“I can’t see one why not to put the 3.0.2 folder in the beta package?”

I think I read some similar sentiment expressed in a trac ticket a while back, but don’t recall for sure

That someone else was me ??

And at the time it was concerning 3.0.1 and they did include the folder into the beta. I was hoping they would do the same again.

I am willing to be more hands on with things. This was me reporting something that needs to be addressed… ie… adding a new version of Akismet

Unlike everyone here, I WANT Akismet. My problem is everytime WordPress self updates, it overwrites the current installed Akismet.

The problem with this is the bundled installed version is 3.0, yet 3.0.1 has been out for well over a month. So I always have to manually update the Akismet plugin again and again.

Can we please include the latest version (sooner rather than later)?

That is what is odd… They patched it and have the fix, but did not tell anyone to apply the fix.

So if you’re using v 1.01 since it was release, they re-released 1.01 without saying a word. Meaning if you were early to adapt, you now have an unsecure copy.

That is really messed up in my opinion.

@esmi I am indeed referring to the TapaTalk plugin. I suspect WordPress will not do much about it except to maybe confirm, but which the problem is; is TapaTalk knows, but does not want to make a public announcement, even with a fix being out (their own words, that I quoted and provided source).