Was getting error "Parameter 2 to imagefield_assist_properties_form() expected to be a reference, value given in /includes/form.inc on line 377." when attempting to insert image with 6.x-1.0-beta3.

On upgrade to 6.x-1.0-beta6 received the error message "The content type ifa_upload already exists in this database. Exiting. No import performed." and now I'm able to select images but the inserted image does not match the selected image.

Several sites that I manage are exhibiting this behavior. Do we need to remove the previous content type prior to upgrade?

Comments

lourenzo’s picture

Assigned: Unassigned » lourenzo
lourenzo’s picture

I think the best choice would be to allow users to select one or more content-types to be scanned.
I'm working on that.

Regards

caesarce’s picture

Thanks for your response that sounds like a good solution moving forward. How can we resolve the incorrect image selection on sites that have already upgraded?

caesarce’s picture

Title: Upgrade Issues » Multiple Image Types Require Unique [fid_n] Replacement Patterns

Ok, after a bit of research I've resolved the issue. I've renamed this issue because the symptom was related to an upgrade but the root cause is multiple content types with images.

The view "imagefield_assist_browser" is automatically updated with an instance of "Image File ID" and "Image File" as fields in the default grid view. Imagefield Assist uses this File ID or fid to resolve which image has been selected by building a link for the image as: "imagefield_assist/properties/[fid]".

When there are multiple content types with images, views appends an "_n" to make each replacement pattern unique. The Link path for each field after the first must be modified to include "_n" in order for the link to be correctly built. For example with three image content types the fid replacement patterns should be: [fid], [fid_1], and [fid_2].

perforator’s picture

+1

perforator’s picture

Issue summary: View changes

removed host path