Call for Beta Testers

Thanks very much for you work… It helps me ! Just a small bug corrected in the file FormElement.class.php at line 475-477 the built link for the files (file-upload field) is broken (for edit-participant admin page) it’s actually using the wp_upload_dir() that is the wrong page. I put the line
$field->link = get_bloginfo('url') .'/'.Participants_Db::$plugin_options['image_upload_location'] . $field->value; instead and it’s better now ??

Cheers

Good catch…thanks!

PHP Fatal error: Access to undeclared static property: Participants_Db::$css_prefix in /public_html/wp-content/themes/newstyle/templates/pdb-single-default.php on line 31

When trying to use templates, even just copy-pasting your default templates to the styles dir.

And check your e-mail for my updated translation ??

participants-database/classes/PDb_Signup.class.php on line 296 : Participants_Db::$plugin_options[‘primary_email_address_field’] instead of Participants_Db::$plugin_options(‘primary_email_address_field’)

??

Cheers

See, this is what betatesting is all about. thanks!

One note : I fixed it temporary in an ugly way that I will not post here ;-)… but a layout problem is that hidden fields are printed inside “<p>” tags and also are separated with line breaks (
). This put vertical spacing that could be annoying for the subscription page layout. You should consider using a special method for printing hidden field in ths signup form.
Regards

Got it. I know why that’s happening.

Just a suggestion more : in the new version you made a test of uploaded-file and generate an error if it’s an known image format. I suggest it should be an option. In my case I want to let people upload either a PDF or a JPG file.

Cheers

You can set the file types that are accepted by an upload field by putting a comma-separated list of the extensions into the “values” field of the upload field.

Yes of course but in participants-database.php on line 2297 you test if the uploaded file is $valide_image and then return an error if it is. I think the idea of that is that we should use an image field for images… but in my case I want to accept PDF or JPG.

OK, well, the way to handle this is to allow image files to be uploaded using the “file-upload” field type. Because the plugin displays files uploaded with the ‘image-upload” type as images, there’s no point in allowing a file that can’t be displayed as an image to be uploaded that way. Also, the statement you are looking at is needed for security reasons.

To make this change, I commented out the statement at line 2303:

if ( $type == 'image' and !$valid_image ) {

      self::_show_validation_error( sprintf(__('For "%s", you may only upload image files like JPEGs, GIFs or PNGs.', 'participants-database'), $field_atts->title ), $name);
      return false;
    }
//    elseif ( $type == 'file' and $valid_image ) {
//
//      self::_show_validation_error(__('The file you tried to upload is not of an allowed type.', 'participants-database'),$name);
//      return false;
//    }

Hello yes it’s exactly what I did too (commenting those lines). But my suggestion is to add an option in the plugin to bypass those options, somthing like this :
elseif ( $type == 'file' and $valid_image and !$option) {

Cheers

My reasoning is a PDF cannot be displayed as an image, so you’d get broken functionality if you had PDF files uploaded as images. But maybe I am missing something…is there a specific reason you want to be able to upload PDF to an image field?

No it’s the opposite : I try to upload an image to a file field ! So I want to put a jpg “for download” not “for display”.

Oh, OK, well that is in…the file upload field can upload any type of file now (well, it will when I update the repository)