olivers

allshookup,
I’d like to get to the bottom of this, to make sure no one else runs into the issue with cforms v8.6 and going forward.
Would you be up for some testing (if so, can you send me your email)?

Cheers,
Oliver
—
Please also visit the cforms forum »

A stupid problem actually which could have been solved much better. But hey – open source is not an ideal world.

how? what’s your better solution?

var sajax_uri = '/wp-content/plugins/cforms/lib_ajax.php';

*usually* works *as is* and doesn’t need the FQDN.

open source is not an ideal world

..but a “cheap” one.

You could use cform’s T-A-F (tell a friend feature), however for anti spamming reasons, T-A-F only allows you to add one friend to send the invite to.

—
Please also visit the cforms forum »

Similar to the way you turned it on ??

cforms Global Settings->Popup Date Picker

For testing, can you disable the cforms datepicker feature (so it doesn’t include its own version of jQuery in the header). If it work s now, you can try and move your the first jQuery include directive after the cforms header:

<script type='text/javascript' src='https://heavenlydezigns.com/myblog/wp-includes/js/jquery/jquery.js?ver=1.2.3'></script>

[ probably after wp_head(); or if it’s another plugin, you need to change the order in which the plugins are loaded and insert their header code ]

They shouldn’t be in conflict, because I’m actually running the two plugins in parallel on two blogs.
You’re above URL gives a 404.

Hi!

Did you configure the cforms header (global settings) to only show on specific pages?

Is only the CSS not loaded or also the Javascript?

Oliver
—
Please also visit the cforms forum »

This and this might help to understand the background of “-moz-inline-box“. Whether or not the validator whines about it, it follows a best practice.

—
Please also visit the cforms forum »

This is a resolved issue. Please update to the latest cforms version!

—
Please also visit the cforms forum »

…because that was the way it was coded at the time ??

But you raise a good point and I can’t even remember why I had it this way and not jump back up to the first missing/false entry.

It’ll be fixed in the next release. Shortly.

You need to set the save_path var in php.ini (or your provider needs to do it for you) properly so that PHP sessions can be saved on the server.

Alternatively, if you do not intend to use cforms CAPTCHA feature, you can also go into cforms.php and comment out the 3 lines that manage the session, look for lines that include “@session_”.

—
Please also visit the cforms forum »

Thank you onewalrus for jumping in.

With cforms v8.1 this shouldn’t be necessary anymore, because it will try to guess the proper settings during activation and will write it to cforms.js automatically.

Good news on the onclick-installer front:

With v8x cforms will be support one click updates!

Can’t really give you an informed advice about the proper setup of MAMP since I don’t use local dev environments. But the source of the problem seems to be the same: too little memory allocated.
See if you can google something on how to configure MAMP to give the PHP server more MEM to work with.

donncha,

sounds good ?? also, it be great if the wp-cache part (kicking in for known users) could invalidate – if needed – super-cached pages (if present) as well.

this would help to keep the creation/expiration process of super-cached pages somewhat automatic and one wouldn’t have to daily flush expired pages manually.

the automatic process should work fine, since one usually has a fair distribution of known and unknown visitors.

just a thought.