bamajr

@roger Theriault – apparently there are two spots where the compatibility of a plug-in is identified. Also, any one who uses the “Better Plugin Compatibility Control” plug-in on their WordPress site will identify this issue.

Your readme.txt file shows:

Requires at least: 3.0
Tested up to: 3.0

If you have tested it this plug-in upto 3.0.1, it should read:

Requires at least: 3.0
Tested up to: 3.0.1

Just an observation: If this would have been done correctly, it may not have taken so long for the compatibility to update on the WordPress Plug-ins Directory.

Before you ask, I do know where to change this at, but it is a hassle. A bunch of plug-in developers seem to forget this one little spot.

The errors are definitely gone. I like the security of your plug-in. Great job.

I have a question though. I want my web site and blog to be wide open to everyone, except I want to force visitors to register in order to comment, and I want to restrict access to a specific set of pages to people who are logged in and are of the administrative group.

Can your plug-in accomplish any of this?

Yeah, the problem with the whole “AVATAR” thing is that Services such as Gravitar aren’t taken into consideration when the theme is built.

I have a Gravitar account listing the four different email addresses I use online. I have an account on a WordPress based web site under the username of BAMAJR. My username on Facebook, Twitter & Linkedin is also BAMAJR. Yet if I log into the same WordPress based web site with my Facebook, Twitter or Linkedin accounts, they all create a different user profile for me, with my name displayed in three different ways. And none of them bring over an email address which can be used within the WordPress based web site.

Yet, my Avatar is the same on all three of the new user accounts created by logging in with my Facebook, Twitter & Linkedin credentials as it is with the original account I have created directly on the WordPress based web site.

There needs to be an integration between the Avatar services and the Gigya services, or it is just a pain in the ass!

I’m interested in the Plug-in developer’s response as well!

mendocinotim

Your email password is in plain text, in the error log you posted. You may want to consider changing it.

Also, are you sure “mail.swing-thing.com” is your SMTP server, rather than just swing-thing.com?

In addition, are you sure your email address is your username, and not just the first part of your email address?

Pretty funny how it only displayed other plug-ins correctly, and not the NextGEN Gallery… Oh, I mean until the issue was fixed in the last update to NextGEN Gallery.

So, let me see, no change to “Better Plugin Compatibility Control” – but an upgrade to NextGEN Gallery = problem with “Better Plugin Compatibility Control” I must be doing my math/logic wrong ??

I don’t see the need for the specific css being used, causing the validation to fail. It doesn’t just fail validation in Firefox, but also in IE, Opera, Safari and Chrome. I understand that the W3C CSS validation is for “site-wide” validation, but that is the point of having CSS standards.

What do you loose if you ditch the un-needed css which is causing the validation to fail?

What browser is that code for? It doesn’t seem to effect the plug-in differently for any of the browsers I’ve tested on.

If you install this plug-in and activate it, with no content and no changes in the settings, the plug-in FAILS css validation.

I have verified this many times by installing a theme, activating the theme, and then testing css validation to make sure it passes.

Next, I install only your NextGEN plug-in and activate it, and css validation fails. If I disable and delete your plug-in, css validation passes again.

I also reviewed the failures listed in my first post, and they are all CSS code which is found in your plug-in.

The missing </div> either didn’t make it to the plug-in site, or it did not repair the problem.

WordPress 2.9.1
Version: 2.0.2.9.2

I have the SEARCH widget above your GO GREEN TIPS widget and THEM MY LOGIN below your widget. If i leave the TITLE: blank, it disrupts the remaining sidebar content (after GO GREEN TIPS widget)!

I do like the idea you have here though. Great thought!

These sites are all running on Debian Linux 5.0 servers with the BigMem kernel installed.

PHP5-GD – GD module for php5 – Running latest 5.2.6.dfsg.1-1+lenny3

libfreetype6 – FreeType 2 font engine, shared library files – Running latest 2.3.7-2+lenny1

I think the problem I discussed should be listed in the Really Simply CAPTCHA support area.

Found at: https://www.ads-software.com/support/topic/320319

After doing some more digging…

I’m using Contact Form 7 (Version 2.0.5) plug-in
w/
Really Simple CAPTCHA (Version 1.0) plug-in

On all the sites, if I disable the “Really Simple CAPTCHA” plug-in, the problem goes away.

…So it seems the issue is in the “Really Simple CAPTCHA” plug-in and not the Contact Form!

After the most recent upgrade offered for Contact Form 7, I’m getting a similar error. I am getting it on multiple sites where Contact Form 7 is being used. Every site is giving me the same error!

https://www.sapphiresolutionsltd.com/contact-us/
Fatal error: Call to undefined function imagetypes() in /../../../wp-content/plugins/contact-form-7/modules/captcha.php on line 201

https://www.fumc-ottumwa.org/contact-us/
Fatal error: Call to undefined function imagetypes() in /../../../wp-content/plugins/contact-form-7/modules/captcha.php on line 201

https://www.captivatingexposures.com/contact-me/
Fatal error: Call to undefined function imagetypes() in /../../../wp-content/plugins/contact-form-7/modules/captcha.php on line 201

https://www.mvfdonline.com/contact-us/
Fatal error: Call to undefined function imagetypes() in /../../../wp-content/plugins/contact-form-7/modules/captcha.php on line 201

Each web site is using WordPress 2.8.4 and has the following:
Apache version: 2.2.9
MySQL version: 5.0.51
PHP version: 5.2.6

This problem did not exist until the most recent update for Contact Form 7, or at least that is when we first noticed the issue on all sites!

The compatibility info is not complete for the plugin either!

apparently this isn’t an issue anyone else is concerned with.

However, I’m guessing this would require an API of some sort which would insert the WordPress functionality into a specific .TPL file.