Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When we get around to a 7.x release, #25801: taxonomy_select_nodes() hard codes limit may allow us to remove some code that we had borrowed from taxonomy a long time ago.
Comment | File | Size | Author |
---|---|---|---|
#22 | initial-7.x-621460-22.patch | 64.19 KB | valthebald |
#20 | initial-7.x-621460-20.patch | 64.07 KB | valthebald |
#15 | nodeorder-7.x.tar_.gz | 12.54 KB | valthebald |
Comments
Comment #1
mgiffordany idea when that will be?
Comment #2
mariusz.slonina CreditAttribution: mariusz.slonina commented.
Comment #3
joostvdl CreditAttribution: joostvdl commentedAny timeframe for this nice module?
Comment #4
damiandab CreditAttribution: damiandab commentedsubscribing
Comment #5
JGO CreditAttribution: JGO commentedSubscribing
Comment #6
carvalhar CreditAttribution: carvalhar commentedso?
Comment #7
mgiffordAnyone tried to put this through Coder for an "automated" upgrade? It doesn't catch everything but it is a very useful place to start with a patch.
Comment #8
Vali Hutchison CreditAttribution: Vali Hutchison commentedSubscribing
Comment #9
ccshannon CreditAttribution: ccshannon commentedsubscribe
Comment #10
Murzsubscribe
Comment #11
imonemus CreditAttribution: imonemus commented+1 for this very useful module
Comment #12
bib_boy CreditAttribution: bib_boy commentedany sign off this? moving to D7 these days and love to take this with me! Always happy to test.
Comment #13
valthebaldI'm afraid coder module won't help in that specific case.
D7 taxonomy significantly differs from D6 in that it does not store node/term relation in one table.
Instead, term reference is a regular FieldAPI field.
I'm currently digging in the code, will try to publish something working in a couple of days
Comment #14
mgiffordThanks for the update @valthebald - looking forward to seeing the patch when you have time to produce it.
Comment #15
valthebaldIt's probably not worth to make a patch against master (there are too many changes), so I attach the whole contents of the module folder.
This is, of course, only proof of concept, yet ordering works.
Would be nice if someone else (or maintainer) will try this.
Enjoy on your own risk :)
Comment #16
valthebaldComment #17
Adlatus CreditAttribution: Adlatus commentednode/add/article
Comment #18
valthebald#17: it's pretty hard to proceed without involving module maintainers.
Any news about their plans regarding this module?
Comment #19
marcp CreditAttribution: marcp commented@valthebald - Thank you for taking this on. I just cut a 7.x-1.x branch off master. Would you please create a patch off 7.x-1.x so folks here can try out the code?
Comment #20
valthebaldSure, here it is.
Here what I've done:
For sure, admin part does not work and there are many glitches.
Right now, module assumes that all vocabularies can be ordered
Comment #21
valthebaldComment #22
valthebaldAttached patch allows full node cycle (create/update/reorder/delete)
Comment #23
pgrond CreditAttribution: pgrond commentedI tried the 7.x-1.x branch with the patch from #22, but I get the following error when I try to make a vocabulary sortable:
PDOException: SQLSTATE[42S02]: Base table or view not found
It's complaining about the taxonomy_term_node table which does not exist.
Comment #24
P.Selfin CreditAttribution: P.Selfin commentedsub
Comment #25
bib_boy CreditAttribution: bib_boy commentedsub
Comment #26
bib_boy CreditAttribution: bib_boy commentedjust wondering if there was an update on a possible 7xdev deployment of nodeorder soon?
Comment #27
valthebaldI'm using patch from #22 on several sites now - it throws sometimes messages and not all admin screens are working, but basically it works.
Patches of that size are hard to maintain, so I really-really-really stuck without any input from maintainer :(
Comment #28
mgiffordHave you tried to contact him/her/them? Send them an email or note on twitter?
If they needed help maintaining it, would you be able to provide assistance?
Comment #29
valthebaldYep, see comment #19 from the module maintainer.
I'm all in to help :)
Comment #30
marcp CreditAttribution: marcp commentedThanks very much for taking on co-maintainership of Nodeorder, @valthebald -- I really appreciate it!
Comment #31
valthebaldPatch from #22 was committed to 7.x-1.x, and I created alpha1 release.
From that point, I want to make a list of things to accomplish before release 7.x-1.0.
Should this be done here, or it's better to create another thread?
Comment #32
valthebaldMultiple bugs were fixed, and there is alpha2 release now.
Please report if you experience problems
Comment #33
mgiffordThat's great. I'm just going to close this issue then.
Comment #34
DanielWashbrook CreditAttribution: DanielWashbrook commentedI just tried Alpha2 and I get the same error as #17
Somehow the module has to tell if the node type has a taxonomy field pointing to an orderable taxonomy?
Daniel
Comment #35
syakely CreditAttribution: syakely commentedmoved to
http://drupal.org/node/1595238
Comment #36
mgiffordWhy?