olivers

thanks for the offer eharris! on my latest wp 2.7 install I can already see the issue with Javascript.

essentially cforms is breaking the JS popup/dropdown feature of WP2.7 – which is also based on jQuery.

I’ll fix this as soon as I can – luckily it’s only an annoying bug (when accessing the cforms tabs) and not one that breaks WP altogether.

eharris, I’ll take a closer look at the final 2.7 release. There indeed seems an issue with conflicting jQuery instances (>> when using “iconified” admin UI )…funny that this wasn’t an issue with the beta 2.7 version…oh well, wonder what will break next in WP 2.8…

easy there. before you make any claims like that, back it up with facts:
(your anti virus software & what type of trojan *apparently* you saw)

ps: for ease of mind: some hyper paranoid antivirus software engines may report certain *packed* javascript code erroneously as malicious.

pps: the site is validated just fine by McAffee and Symantec

use the RoleManager plugin to control cforms permissions for particular users/groups

cforms v9.3 is indeed compatible with plain vanilla WP 2.7 it may however not be compatible with your setup (e.g. other admin plugins/settings you’re using)

This has comes up now a few times in the cforms forum (see link below).

The short: you need to access your wp_options table directly and remove the one entry “cforms_settings”. Then reactivate.

I’m not sure what causes WP to apparently not treat the saved settings as an array anymore after “some specific action”.

If you can reproduce or recollect on how you did it, I’d be grateful for any hints.

—
Please also visit the cforms forum »

Simply turn on DB Tracking, which will (and this is the way it’s meant to work) add a unique form submission ID as a prefix, so you’ll always know what file belongs to what submission…

I was planning on upgrading PHPMailer to 2.1.1 with the next release, which then supports POP before SMTP.

Send me an email (in cforms.php) if you’re interested to test.

—
Please also visit the cforms forum »

Usually I would leave it at that. However for sake of completeness here is my take, especially since you’re publicly accusing me and not even sharing the context, Donna or Drawer.

I told Oliver how I followed his directions in the FAQ, and he had no idea what I was talking about!

I had no idea how what you’ve tried stood in context with your problem, since you didn’t give me much data to work with…that’s why I asked a simple question which you refused to answer.

The FAQ by now contains a lot of information and as I pointed out, you probably followed the wrong steps. Especially for a vague statement such as ‘I have the same problem‘ chances are there are more than one sources of error.

You’re right, his forums are very difficult to read. In Oliver’s Faq he says to do this:
The form hangs after submit (SMTP)

You should’ve read on to the area where it says: “One momemt please…“

When I told Oliver this, he said he never told me to do this, and to try to reboot – as a joke. How funny.

I’ve offered help, I asked for more information, you decided to not give the info, at this point, a pinch of sarcasm was my only way out ??

In all honesty and after reading you post here and seeing all the other support request in your profile, I *sincerely & without sarcasm* suggest you try an easier-to-setup contact form plugin, there are plenty out there.
Good luck.

resolved. gmail doesn’t respect the email REPLY-TO header data if this is the case.

[***] post went awol after editing (???), so here is it again:

when the cforms plugin is installed
purl not being defined
may appear under these circumstances:

1. WP’s own WRITE/EDIT POST/PAGE having troubles loading the cforms admin header (including the part the defines purl)
2. or some other plugin is utilizing the TinyMCE editor in a different area that doesn’t load the above mentioned cforms admin header

cforms by choice doesn’t add it’s own header data to every admin page to keep overhead to a minimum (see editor.php / ~190).
However, its button would still get added to all (admin) TinyMCE editor instances, due to the rather globally functioning ‘mce_external_plugins‘ filter.

here are the options to ‘fix’ this, or in other words make it work with other plugins that require TinyMCE to work outside of the usual place:

1. turn off the cforms TinyMCE editor button (cforms config)
2. change editor.php (~190) to make cforms include it’s header on all admin pages
3. have the other plugin call cforms’ insert_cforms_script() function to add the cforms header to their page and thus define purl

I’m still not convinced that generally adding the cforms header to all admin pages is a good thing, so I won’t change that behavior going forward, but I’ll see if I can implement a check before adding the button to TinyMCE whether or not the user is on a “write/edit post/page” page.

Which on the other hand would not allow any other TinyMCE instance to make use of the cforms icon without coding again – but I guess there is no perfect solution.

—
Please also visit the cforms forum »

General observation: Your WP or some other plugin magically introduces <br /> tags between the label and input field, hence the funny looks.

Re: your <h2> oddity, giving the your <div class="entry"> a white background seems to fix the issue, the root of the problem is likely related to your custom WP CSS styles.

—
Please also visit the cforms forum »

For one, if you want help you should tone your voice down a bit.
Secondly, skimming through an FAQ list is different than making an effort to reading and understanding FAQs.
Lastly with no URL to look at, it’d be only pointless guessing…

—
Please also visit the cforms forum »

Quite odd, since I’m seeing it running fine on so many 2.6 installs.

How much PHP Mem has been allocated on the server?
What version of cforms are you running?
Did you configure captcha?

—
Please also visit the cforms forum »

You might want to check out the FAQs, this one might be of help.

Also, what does the web server log files say re: 404?

—
Please also visit the cforms forum »