Download & Extend

Please release filefield_paths 6.x-1.5 for multiple fixes

Project:File (Field) Paths
Version:6.x-1.4
Component:Code
Category:task
Priority:critical
Assigned:roball
Status:fixed

Issue Summary

The current latest official 6.x-1.x version of "File (Field) Paths" - 6.x-1.4 - does not properly work with the latest official 6.x-1.x version of the "Comment Upload" module - 6.x-1.0-alpha6, at least under PHP 5.3.x.

With filefield_paths 6.x-1.4 (which is already two and a half years old) I am receiving the error

Parameter 2 to filefield_paths_filefield_paths_process_file() expected to be a reference, value given in /usr/share/drupal6/includes/module.inc on line 497.

and the uploaded file will stay directly under the files directory instead of being moved to the configured target location.

This bug has been fixed on 6 Feb 2012 - thus the latest dev snapshot (6.x-1.4+9-dev) must be used in order to properly work with the "Comment Upload" module.

To avoid relying on a dev snapshot, it would be nice to have a new official 6.x-1.x version (6.x-1.5) released. Thanks.

Comments

#1

Any progress here?

#2

Title:Please release filefield_paths 6.x-1.5 (to support Comment Upload)» Please release filefield_paths 6.x-1.5 for multiple fixes
Priority:major» critical

We're closing in on three years since the last stable release.

Among other items that have since been fixed in dev is #635854: Node links to original file path after creation until the node is saved again, which seems like a critical bug to get fixed.

Can we please get moving toward a new release? RC, beta, something?

#3

Still no updates? Is this module still being maintained?

#4

Hi guys,

Sorry to disappoint, but I have no need to FileField Paths ion Drupal 6 as I don't do any new builds in Drupal 6, and being very much of a scratch your own itch sort of community there really is no reason why I would continue working on the D6 branch.

I'm happy for someone to put there hand up to takeover the D6 development though.

#5

Could you just take the latest dev and commit it as a beta? As mentioned above, there are numerous fixes ready to go. You don't need to continue working on it -- just roll what's already there.

#6

Given that there's no difference between making a beta from the dev and just using the latest dev I think it's somewhat unnecessary, but I'll consider it when I have a bit of time free.

#7

Hello Deciphered,

good to know your development status. I am an active D6 developer and would care about maintaining the 6.x-1.x branch and release 6.x-1.5 after having it tested carefully.

#8

Assigned to:Anonymous» roball

#9

Status:active» fixed

Done. Version 6.x-1.5 has been released.

#10

Awesome, thank you!

nobody click here