CRED 1.2.6 (beta1) for WordPress 3.9

   Amir

Announcements

April 18, 2014
22

We’re ready with a beta update of CRED 1.2.6 to WordPress 3.9. This release addresses several older glitches, as well as major WordPress core API changes.

WordPress 3.9 came with a number of major API changes and this version of CRED addresses them. Here is the list of changes in CRED 1.2.6b1:

  • Added Compatibility to WordPress 3.9
  • Replaced mysql_real_escape_string deprecated method
  • Fixed add Notification issue on WordPress 3.9
  • Fixed missing Body Shortcodes on CRED Notification
  • Fixed missing Hierarchical Taxonomy numeric values on Notification mails
  • Resolved missing Send to Author notification on Post status Change
  • Resolved hiding posts after auto expires
  • Fixed – PHP Fatal error: Call to undefined function wpcf_form_simple() in admin post edit for post expiration
  • Fixed – Notice: Array to string conversion in … CredPostExpiration.php
  • Fixed – Fatal error and warnings when I set Automatic Expire from Post Edit screen
  • Resolved issue on Import/Export cred_post_expiration_settings
  • Resolved missing Hierarchical relations for Categories when I tried Numeric values
  • Fixed – PHP Notice: Undefined index: author

For production sites, if you haven’t yet upgraded to WordPress 3.9, we recommend to hold with this release until next week and allow for more testing. Adjusting to these big API changes in WordPress 3.9 may take a bit longer for CRED and other plugins your site runs.

If you can test CRED 1.2.6b1 on development sites, running WordPress 3.9, it would be great. This will give us more feedback on different cases.

Download and upgrade

Since this is a beta version, it will not update automatically on your sites. Please log in to your wp-types.com account, go to Downloads, scroll to the bottom and get CRED Beta.

Feedback? Questions? Ideas? Leave your comments and we will get back to you.

 

Comments 22 Responses

  1. Great news… however I understand that you are still using Zebra Form.

    Wasn’t this third-party plugin supposed to be replaced by something new ?

    • Right, this is an intermediary release for WordPress 3.9 changes. CRED 1.3, without Zebra forms should be ready by the end of this month, as beta.

  2. Hi, its great the way you keep things up to date so promptly with the versions of wp. But, I’m still hoping for a version of Cred that does not use zebra, doesn’t mess with the p tags and has blockquotes as a choice on the editor. I really haven’t been able to use Cred for these reasons. Not really complaining, I love toolset but just getting a bit desperate!

    Cheers, Mark

    • Coming soon. CRED lead developer had a little family accident last week, setting us back a little. Everyone’s Ok, except the schedule. We’re doing our best to make up for it with more developers helping.

      • Amir,

        Hope your CRED lead dev and his family are all OK.

        May we have the chance to know what’s going to be in include / exclude in the next CRED release ?

        I am definetely looking to get ride of Zebra form which result in many errors related to Date fields values and other output error with Views…

        I am working on a classifieds and bookings website right now and rely on Toolset to handle content creation for front end users but I can”t make it public until the issues with CRED are solved.

        I’d like to be able to know if I can count on Toolset or if I have to choose another plugin (such as Gravity form) to take care of the booking and posting forms ?

        Thk you

        • They are all feeling a lot better. Thanks for asking. I’m saying this with all seriousness.

          We are finally pretty close to this clean CRED release, which comes without the Zebra library. I’m waiting to see the first beta myself, before I proudly announce dates for it.

          Yes, you can plan on Toolset doing this work properly. It may take just a little more, but we are certainly going to live up to our work and provide the product that you paid for.

          We are going to write an update about this, hopefully with a first beta, this week.

  6. I got the new version of CRED (1.2.6) and now my forms are busted (WSoD)

    My Apache logs show this error:
    cred-frontend-editor/classes/common/Mail_Handler.php on line 57

    Is this version only supported in PHP 5.4+?

    • This shouldn’t happen. Francesco, CRED’s developer, will be in contact very shortly to check what’s wrong. We’ll make sure that it gets back to normal functionality for you.

  7. Hey Amir,
    is there any change the the handling of image uploads will be fixed soon?
    I hate to sound like a broken record, but it’s really holding me back.

    • Can you remind me which issue that is? If it’s in our forum, please paste a link, so that I can review it and see what’s happening.

      • In a nutshell, images are being uploaded twice, once to see if they were actual files, then uploaded again. The process also didn’t allow for the Resize Before Upload plugin (http://wordpress.org/plugins/resize-images-before-upload/) to work, which is a must for a real estate site where the agents are creating their own listings.

        I was told in the support forum “This is how it is supposed to work”. which is just ridiculous. I was then told to use your paid Professional Development Services, submitted my request and was ignored.

        What I would like to see happen is for CRED to use the built in WordPress upload functions.

        I will pay to have this happen. I really need this to work and I’ve been waiting with my “feature request” on the to do list for over a year now.

        • Types actually has a pretty nice image resize feature. Why do you need another plugin to resize images?

          If you upload the full-size images with CRED, they will not necessarily be displayed like that. Types would create the resized versions of these images and store them on the server. This way, you or authors don’t need to worry about the image sizes at all.

          This functionality is also fully integrated with cache plugins that use CDN, so the resized images can be served very efficiently.

          I’m not trying to argue that this is the best approach. Can you tell me what approach you prefer and what are its benefits?

          Thanks

          • Want to second Darryl’s comment.

            What *seems* to happen, and the explination I’e seen on the boards, is that the image is uploaded once, to verified it’s allowed (which doesn’t make much sense to me), and then a second time, to actually move the file where it’ supposed to be.

            This means the user has to wait, twice, and it’s really hard to justify to them. Fixing this would be a huge improvement.

            • CRED 1.3 will use a new (and good) fields library, which will not have this issue of double file uploads. I was curious to learn why you also prefer to use an additional image resizer, rather than that one built into Types. If there’s anything that we should do to improve our image resizer, I want to know.

          • If I use the standard WP upload methods, the plugin “Resize Before Upload” (link above) resizes the image -*BEFORE*- it’s uploaded. I think it uses HTML5, but as far as I’m concerned it’s magic and I love it.

            When someone is trying to upload 30 photos that are all 24 Megapixels for a real estate listing, this is very handy 🙂

            • I’m just slow today. Of course this helps, thanks for explaining it again. Yes, it’s a lot more handy for you to upload smaller files to begin with. Let’s see how this works with CRED 1.3 and our new fields library. The old Zebra forms had their entire own UI. Now we should be using the native WP API, so things may just work together.