Great, really great modules!
It would be nice to have it on D7!
Are there plans to port it?
TIA!
aleagi
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | maskedinput-not-saving-field-value.patch | 1.87 KB | primsi |
Great, really great modules!
It would be nice to have it on D7!
Are there plans to port it?
TIA!
aleagi
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | maskedinput-not-saving-field-value.patch | 1.87 KB | primsi |
Comments
Comment #1
twooten commentedHi Aleagi,
Yes I do intend on porting, just gotta get the time.
Tim
Comment #2
Jerome F commentedSubscribing
Comment #3
felipepodesta commented+1
Subs...
Comment #4
bjlewis2 commentedsubscribing
Comment #5
causalloop commentedany idea on a time frame for this?
Comment #6
helior commentedI've contacting the maintainer about merging a Drupal 7 version of this functionality –– maybe as a 2.0 release? for now you can find that version here http://bit.ly/mC5xyV as a sandbox project, for now. I hope this is helpful to others.
Comment #7
primsi commentedI was having problems with the saving of the field data. As far as I understand, it seems that hook_field_widget_form didn't follow the field schema, that expects a 'value'.
Although the sandbox disappeared I am attaching a patch that fixes (needs review) the issue.
Comment #8
helior commentedYeah, just this morning I moved the sandbox project to an official release found here: http://drupal.org/project/maskedinput. Unfortunately, I never heard back from this project's maintainer so I guess a merge is not possible right now.
Thanks primsi for that patch! I added your issue to the Masked-Input issue queue: #1210212: Field widget not matching up with field type schema. I'll roll this fix out on version 1.1.
Comment #9
twooten commentedUmm, actually I'm the maintainer and no one ever contacted me. Anyway, @helior I just tried out your D7 version and it seems to work well so no reason for me to port mine.
Tim
Comment #10
pedrorocha commentedHi guys,
do you agree that 2 modules for the same goal and using the same jquery plugin is a nightmare for general users?
What about merging the new 7.x version with the oldest and with more users(this one here), enabling long date users to update to Drupal 7 without further problems? This type of forking is bad for the community.
Let`s share efforts and make this module even better, making an API, etc, that it`s what we can do better!
I created an issue in the other module: http://drupal.org/node/1454150
Comment #11
helior commentedHey @twooten, took you long enough to reply! :P
Yeah, I'm all for it! I wanted to merge these two modules over half a year ago, but I thought maybe this module was abandoned. At any rate -- Tim, do you want to give me co-maintainership so I can add a 7.x-2.0 branch? Or, you're more than welcome to swipe the code and add it yourself. Once that happens I can tag my module as obsolete.
Comment #12
twooten commentedHelior, I added you as a co-maintainer. Let me know if you run into any issues. I'm curious to know how you're going to handle those that currently use your module?
Tim
Comment #13
helior commentedI'll redirect new users over to this project. My project will still exist for all their current users; any patches that go towards it will also be applied here, but probably not vise-versa.
I'll go ahead and commit it tonight!
Comment #14
helior commentedI finally tagged the 7.x-2.x branch with an official release. We finally merged!
(ᵔᴥᵔ)