Status of Port to Drupal 6?

I have upgraded my site to Drupal 6 and all the fields that used textfield autocomplete simply disappeared.

Is this module going to be converted to Drupal 6? Anybody is thinking / working on it?

Alternatively - has anybody had to deal with this issue - is there a way how to convert, in D6, the textfield autocomplete fields to common text fields?

I'd love to see this port to drupal 6. Is that in the pipeline?
Can i help?

This would be pretty handy for me also. I've looked over the code to try to see what needs to be done, but I'm new to CCK and haven't done any code work with drupal 6 yet, so I don't know if I have enough time to figure it out.

One option I might look at is to modify the content_taxonomy_autocomplete widget to deal with text fields instead of taxonomy.
Offhand, that doesn't seem to complicated.

rubberglove, that is a great idea - this does not need to be a separate module. Good luck, let us know of the progress!

I too would love to use this cck field on a new site... is there anyone interested in upgrading this module for 100$ ??

Patchak

I think is better to do that in the CCK core -> http://drupal.org/node/126595

Hi all,

I have contacted linuxbox for this, and to see whether he's up for porting this module to Drupal 6. If not, I would be glad to. Though, seeing that there's only a 5.x-dev version of this, I have requested linuxbox to transfer the ownership of the project to me so it will be easier to deal with any support request or bug report that may arise since then.

I plan to add options to perform the autocomplete job against already existing values or against the list of allowed values configured in the field settings panel.

Cheers

Well, for the looks of the issue queue, this seems to be a project that was created as a method to share something that linuxbox did at one point in the past, but the code is just for D5, in dev state, no aparent support given either. So I would prefer a complete transfer of the project. It would be a lot easier for me to follow if it's on my projects page, I can use the email notification feature for issue changes, etc. And so, I think it will be on benefit of everyone that may need to use this module for D6 and on.

BTW, I contacted linuxbox a few days ago, but no answer yet. :(

Hey there Markus, are there any news about this field's status yet?? Anything we could all test ? ;)

Thanks,
Patchak

I have the module ready, however I would prefer to resolve the following issue I opened to the d.o. webmasters queue: #367578: New cck_text_autocomplete project or transfer project ownership of textfield_autocomplete?

I haven't got any input from linuxbox yet.

The module I have written goes a bit further than the one published in this project. Here's the README.txt

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Textfield Autocomplete Widgets for CCK 2 and Drupal 6
;; $Id: README.txt,v 1.1 2009/02/02 07:59:08 markuspetrux Exp $
;;
;; Current maintainer: markus_petrux  (http://drupal.org/user/39593)
;; D5 module author  : linuxbox       (http://drupal.org/user/90839)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

WARNING *** WARNING *** WARNING *** WARNING *** WARNING
=======================================================

This module is pure experimental yet, and it is subject to be changed and
published in the proper repository as soon as the following issue in the
d.o. webmasters queue is resolved:

http://drupal.org/node/367578


OVERVIEW
========

This module adds 2 autocomplete widgets for CCK fields.

The "Autocomplete text field (limited)" widget can be used for Text and Number
fields and it takes candidate values from the defined list of Allowed values of
the fields.

The "Autocomplete text field (unlimited)" widget can be used for Text only and
it takes candidate values from existing values in the database for that field.


REQUIREMENTS
============

- CCK (http://drupal.org/project/cck)


INSTALLATION
============

- Copy all contents of this package to your modules directory preserving
  subdirectory structure.

- Goto Administer > Site building > Modules to install this module.

- Create or edit content types and start using the widgets for your Text and/or
  Number fields. :)

I hope to get advice on how to proceed from #367578: New cck_text_autocomplete project or transfer project ownership of textfield_autocomplete?

Meanwhile, the module can be found here:

http://cvs.drupal.org/viewvc.py/drupal/contributions/sandbox/markus_petr...

That's my sandbox space in the drupal's contrib repository. That will help me deal with any bug report or request that ay arise while the proper destination of the project is being resolved.

For information on how to checkout from CVS, please read: http://drupal.org/handbook/cvs

Cheers

This module has been tested, works fine! GREAT WORK!!!

@markus_petrux,

Could you please post the command to checkout the textfield_autocomplete port from CVS? I've read the CVS handbook, but all my attempts tend to fail miserably :|

-tnx!-

Fantastic, the CVS code works flawlessly in D6.9; please publish it as a module.

One question -- now after installing the D6 CVS version of textfield_autocomplete, fields created in D5 textfield_autocomplete do show in the content type, and when I edit the nodes.

However, these fields do NOT show up under content when I edit a view -- the other fields are all there, but not these textfield_autocomplete fields. I cleared all caches etc but they still don't show. Is there something that might be missing in the code that makes fields visible for views?

AFAICT, this module implements the widgets, which only affect the edit form. The fields are still text and/or number, and these come with their own formatters, that can be selected from 'Display Fields' page of the content type, or from the Views UI.

I am so sorry ... #16 above is not true: the patch does NOT work for me. I was so much hoping it would work that I looked at different fields. This is obviously also why it does not show in views (#17) :-(

When I go to the content type, there is a red message:

This content type has inactive fields. Inactive fields are not included in lists of available fields until their modules are enabled.

and the fields are listed further e.g.:

Editor/author (field_editor_author) is an inactive Text field that uses a autocomplete widget.

I tried to enable and disable the module but the fields are not recognized... What do you recommend me to try / look up? I am ready to help in order to solve this problem...

Hi all,

Well, linuxbox contacted me a week or so ago, but offeting only co-maintainership of the textfield_autocomplete module. I replied them that since they don't seem to be very active at d.o., and that the module they created was just a single commit that haven't had any more attention, at least apparently (see issues queue), I was more in need of full access to the module project. Too bad, I'm still waiting for an answer...

In regards to this functionality, there's also the posibility to include it as part of CCK itself. KarenS and yched showed a bit of interest in it. See: #126595: autocomplete for text field. Make suggestions like free tagging.

The module would have a different name.

So... I have now 2 options in mind:

1) This feature is included in CCK itself. Depends on CCK maintainers.
2) I create a separate project where I can freely keep things as up to date as possible, or try to.

I would be bumping the CCK issue to see which road to take. Please, see: #126595: autocomplete for text field. Make suggestions like free tagging.

Cheers

Well, since it has not been possible to further contact linuxbox, and CCK maintainers seem to be so busy, I ended up creating a separate project for this feature:

http://drupal.org/project/autocomplete_widgets

Cheers

I have the same problem as #19: I've installed the new module from http://drupal.org/project/autocomplete_widgets, but the Text fields that were created using the old module are not working anymore, I only get the errors signaled in comment #19. Is this supposed to happen? The new module requires the custom content types for D5 to be rebuilt for D6 in order to work?

These are separate modules, so there's no upgrade path from one to the other.

I believe one possible method would be to change the widget in origin to a normal text field, then upgrade CCK as normal. Once it is all working with new versions in Drupal 6, then install the new autocomplete widgets module, then use it as if it was the first time.