gatorfantom

Derek, can you comment on the viability of the solution that temash suggested? I’ve been using OptionTree for a while now, love it, and have never had any problems with it – until today when I updated to the newest version (1.1.8). Now I’m seeing that same “Fatal / Cannot redeclare” error. The 1.1.8 update also deactivated the plugin (thus changing the site interface considerably) and will not let me reactivate it. I just keep getting the same error.

@knappen + @michaelisc + @swoledge:

Just an FYI… I’m running that same combination of versions — but am not experiencing any of the issues you’re reporting. My guess is that it’s a conflict with another plugin that you all have in common.

Good luck…

I’m getting the same error when trying to upgrade to the latest version of WordPress (3.0.4).

Looks great Mike, thanks.

Thanks Mike. When will version 2.9.1 be available? (I didn’t see it in the directory.)

Nivovas:

It may be a language barrier misinterpretation, but to me it sounds like what you’re asking for is a walkthrough or tutorial of how to use the plugin – which would be extremely time-intensive for anyone trying to help you.

You’ll get much quicker, and more thorough responses if you can be more specific about the problem you’re having. For instance, one of your goals is to be able to “build different styles,” so perhaps you could start by describing one particular element that you’re trying to style, what type of style you’re trying to apply, etc.

In my experience tinkering around with this plugin (which I think is one of the best WordPress resources available), once you figure out 3-4 different things – the rest of it starts to make sense as well.

-Tom

I’m on Safari 5.0.1.

I commented on another post where a Chrome user was (I think) having the same problem:

https://www.ads-software.com/support/topic/plugin-fast-secure-contact-form-where-are-the-fields-to-re-label-the-default-fields-like-subject?replies=8

Mike, I’m not a php expert but I think I found the problem: there’s a missing </div> on line 1512 of “si-contact-form-admin.php”

When I typed that in and resaved the file, the entire admin panel takes on a much different (and better) look.

Hope that helps.

-Tom

Guys – I just realized this post is related to one I submitted a few hours ago. I’m using Safari, which often behaves the same as Chrome, so that explains some of it.

Fiddler, try this: Locate the “Enable aria-required tags…” option towards the bottom of the admin panel, and click on the “help” link. (It’s the line just above the “Send a Test Email” option.) This should reveal the help text AND all of the hidden options you’ve been looking for. (After going crazy looking for the CAPTCHA code field label, I stumbled on this while going down the page clicking anything I could, hoping something would appear. I was just about to call it quits too.)

Here’s my post:
https://www.ads-software.com/support/topic/plugin-fast-secure-contact-form-possible-bug-in-29-hidden-sections?replies=1

I thought about doing that, but then I saw this option in the settings (which was “on” by default):

( X ) Add sitemap URL to the virtual robots.txt file.
The virtual robots.txt generated by WordPress is used. A real robots.txt file must NOT exist in the blog directory!

I don’t know what a “virtual” robots.txt is, but I’m worried about creating a file on my own based on this warning about having a “real” file in the directory. Thoughts?

Thanks Mike. My problem is that in order to exclude pages/posts using the XML Sitemap Generator plugin, it requires me to enter the page IDs. But since these two SI Contact Form captcha links aren’t actual pages that I created in WordPress, I’m unable to locate the IDs for them. Any ideas? Here some more info in case it helps:

Per the plugin FAQ page:
Exclude posts or pages
Here you can enter the IDs of posts or pages which will not be included in your sitemap. You can see the IDs of the post or pages in the corresponding management pages. Separate multiple IDs by comma.

Screenshot of plugin settings:
https://img.skitch.com/20100810-rnwt4anfemnd3s7xpqcb7wx8c9.jpg

Hi Mike. I came to the forum looking for info on this very topic, so I’m glad to see that you’ve already addressed it. Two quick questions:

1. Two pages/links from one of my sites have already been indexed:
/wp-content/plugins/si-contact-form/captcha-secureimage/
/wp-content/plugins/si-contact-form/captcha-secureimage/backgrounds/
Will the “disallow” that you posted take care of both, or do I need to add a second disallow for the “background” subdirectory as well?

2. I use the XML Sitemap Generator plugin (v3.2.4), and just read this in my settings: “The virtual robots.txt generated by WordPress is used. A real robots.txt file must NOT exist in the blog directory!” I’m guessing that means that I won’t be able to access the robots.txt file that you suggested modifying, however, there is an option in the XML Sitemap plugin for “Excluding Posts/Pages” by ID. Do you think adding the two indexed links to this plugin option will achieve the same result as what you’re proposing?

Thanks for your help!