| Post |
|
Admin
| Oliver Munich, Germany posts 6237 3:02 pm December 18, 2011
| |
|
|
….in case you're interested, pls leave a note here.
the upcoming version (cformsII v13.0) will ensure WP 3.3 compliance, using the internal date picker (required now!) and will address other issues that are related to the WP 3.3 release (only the plain vanilla release is considered with the default theme!).
|
|
|
|
|
Guest
| NickR 6:14 pm December 18, 2011
| |
|
|
Hi, I'll volunteer to test the new version.
I have a site running in a live environment with a duplicate running in a test environment. I updated the test site to WP3.3 and the date picker is broken so I'll happily test cformsII v13.0 in that environment. I'm keen to resolve any issues before I update the live site to WP3.3 from WP3.2.1.
Please let me know if you want me to do this.
Thanks
Nick
|
|
|
Guest
| frances 6:00 pm December 19, 2011
| |
|
|
I'm also running a live and dev-server with the latter upgraded to WP3.3 and would offer to test v13.0 also
Frances
|
|
|
Admin
| Oliver Munich, Germany posts 6237 6:12 pm December 19, 2011
| |
|
|
That's great, the more the merrier.
It'll take a few days, but once I'm ready to send a first beta, I'll have it sent to your email addresses.
In the first beta release, I'll cover:
*) date picker support
*) dashboard enhancements
*) general UI improvements
*) several bug fixes
Note: v13.0 will required WP 3.1+
|
|
|
|
|
Guest
| Vincent 12:07 am December 20, 2011
| |
|
|
I have a few sites that utilize your wonderful plugin, I also would like to be a tester.
Tried to upgrade to WP 3.3 and no luck on the date picker also.
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:15 am December 22, 2011
| |
|
|
QUICK UPDATE
I'll be sending out a first beta hopefully by tonight.
If anyone could, please test with WP 3.2 or WP 3.1 as well. I expect it to work just fine, but it'd be great if someone could confirm.
Important Note (once you have the beta code):
- Backup your existing cforms DIR & make a backup of your WP DB
- Properly deactivate the plugin, upload and reactivate
- Clear your browser cache
- Follow the instructions of the note below in red to enable the new admin/autoconf email layout
(sorry there is no automatic update possible, but I may think of a button to reset it to default)
Here is roughly what's been addresses by cformsII v13:
*) WP3.3 compliance
*) other: WP 3.3 jQuery / jQueryUI is now being used for the date picker!
*) other: link to supported date formats added to global settings screen
*) other: enhanced dashboard layout / listings
*) bugfix: checkbox "default state" setting fixed
*) bugfix: checkboxgroup "default states" & "new line" settings fixed
*) bugfixes: several admin screens related fixes
*) bugfixes: tracking page, download options fixed (header, URLs etc.)
*) other: checkbox fields now include a "checked symbol", instead of the word "on"
*) other: email layout enhancements (optimized for gmail & HTML capable clients)
!!! NOTE: in order to fully enable the new layout for old forms, you MUST
create a brand new form and copy/paste the HTML message parts (admin &
auto-confirmation message) from this new form to all your old forms !!!
|
|
|
|
|
Guest
| NickR 12:07 am December 23, 2011
| |
|
|
Thanks for the update. I hope it's OK to post information about v13 beta observations here.
I still need to carry out extensive testing but my initial experience is:
1. Date Picker – Displays correctly but the chosen date displays with the year twice e.g: 30/12/20112011 (with the date format set to dd/mm/yy in the global settings)
2. A minor typo – In the new WP3.3 admin bar "Safe & update form settings" should read "Save & update form settings".
I'll carry out more testing over the next day or so and report back.
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:11 am December 23, 2011
| |
|
|
Posting feedback here is fine, thanks for the quick turn-around time.
I'll revisit your points raised.
re. 1) where does it appear twice? In the input field or later in the email(s)?
it usually is a sign that the old "yyyy" definition was used instead of the newly supported "yy"
EDIT: I figured out what the issue is. Thx.
re. 2) done.
|
|
|
|
|
Guest
| NickR 11:02 am December 28, 2011
| |
|
|
I didn't discover any more issues with the v13 beta so I went ahead and updated my live site with the release version of v13.
Since doing that I've noticed that user input resulting from radio button selection does not appear in the Admin email.
I think this was also a problem with the beta release but I hadn't noticed it.
|
|
|
Admin
| Oliver Munich, Germany posts 6237 10:12 am December 31, 2011
| |
|
|
I haven't seen any issues during my testing, but will recheck.
|
|
|
|
|
Admin
| Oliver Munich, Germany posts 6237 8:42 am January 5, 2012
| |
|
|
you're right NickR, I'll have an update out asap. thanks!
|
|
|
|
|
Guest
| Frances 6:14 pm January 5, 2012
| |
|
|
Hi Oliver,
I've tested this out on my local install and live site (same site, different theme). All the data carried over ok and I haven't seen any problems. I'm not using the date picker.
One thing I did notice in the admin bar is, 'Safe & update form settings' should read 'Save'.
Grüß aus Berlin,
Frances
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:33 am January 6, 2012
| |
|
|
Thanks Frances, the spelling should be corrected in the current release already, but I'll double check to be sure.
|
|
|
|
|
Admin
| Oliver Munich, Germany posts 6237 4:16 pm January 6, 2012
| |
|
|
v13.1 is out now, fixing the radio button issue.
|
|
|
|
|
Guest
| NickR 5:27 pm January 6, 2012
| |
|
|
Thanks for the update. The Radio Buttons are working fine now. Much Appreciated.
There's just one other minor point I've noticed. In version 12, the user input in the admin emails was formatted according to the style attributes in the "Admin HTML message (Header)" section. In version 13 only the header (i.e. "A form has been submitted on…") picks up this style; the user input remains unformatted. Is the format for this controlled elsewhere now? This is not particularly important but it is nicer if the whole email is styled in the same way.
Regards
Nick
|
|
|
Admin
| Oliver Munich, Germany posts 6237 5:34 pm January 6, 2012
| |
|
|
Per the (yellow) upgrade note on the form settings page (it should have appeared after re-enabling cforms) you need to reset both the auto conf message and admin message to the new default template.
If you've made custom adjustments to these, you need to re-introduce those afterwards.
|
|
|
|
|
Guest
| NickR 1:41 pm January 7, 2012
| |
|
|
Yes I did that (by clicking the reset button above the admin form settings?). I re-tried it and I have also tried copying pasting the HTML/CSS from a new form just to make sure it was identical, but it didn't make any difference.
I added a fresh install of cforms to a test site and created a simple form to test and that worked fine there. The HTML in the test form is the same as my live site.
As I say it's not particularly important because the information is there but having now seen the improved email format I can see that they look really nice.
|
|
|
Admin
| Oliver Munich, Germany posts 6237 1:50 pm January 7, 2012
| |
|
|
quite odd. but since a new form doesn't work either, my suspicion is that something went wrong during the upgrade.
what you can try (not without a tiny risk though) is to
- make a "global settings" backup of all cforms settings,
- uninstall cforms (global settings),
- disable and renable the plugin
- see if it works then
- then restore the global settings backup (again under global settings: restore all data)
|
|
|
|
|
Guest
| benny 6:09 pm January 9, 2012
| |
|
|
Hello Oliver,
We wp version 3.3.1 running on Linux, we updated to version cform 13 but there is no key input in the 'article, the strange thing is that the form by entering the string can not see, you got any solution?
thanks
|
|
|
Guest
| NickR 8:10 pm January 10, 2012
| |
|
|
Hi Oliver
Thanks for the advice on backing up, reinstalling and restoring – I've done that and it worked like a dream. Everything is good now.
Much appreciated.
Regards
Nick
|
|