I didn't see an issue for this in the queue so I thought I would start one. I've got an interest in using this module starting about 2 months from now, so I may be in a position to help with this (or find someone else to help). It seems like most of the dependent modules (Biblio, Views) are pretty stable for 6.x so I don't think anything is "blocking" this right now, but due to my lack of familiarity with this module that could be entirely wrong.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | millenium_6.patch | 56.6 KB | dawehner |
| #1 | millennium 5 to 6 coder messages.jpg | 467.69 KB | janusman |
Comments
Comment #1
janusman commentedGreat! Be sure to tell me how you're coming along.
I just installed coder module and a D6 instance (i was just being lazy). Perhaps this will be easy =)
Below is a snapshot of all that needs to be fixed...
Comment #2
dawehnerComment #3
dawehnerfirst i just enabled 5.x to 6.x in coder module
then i tought, i would have to use code style and WOW there are an incredible count of mistakes
i fixed definitve not all, but the author should read defintive read about http://drupal.org/coding-standards
patch to cvs head
Comment #4
janusman commentedI admit I made this module without knowing about coding standards; I know better now =)
This looks like early christmas!! Thanks a lot for your hard work. Will test soon!
Comment #5
janusman commented@dereine: for some reason you patched agains a very, very old version of the module. Probably I did something wrong to mantain HEAD (to me the updated branch is DRUPAL-5 and not HEAD)... this was my first project and a number of things have been/are still wrong =|
Your help is deeply appreciated! Can you help me figure out this?
Comment #6
dawehneryes thats definitive the problem
i checked out the current head of the module so....
can you tell me how to check out a specific version? i forgot it
Comment #7
janusman commentedThat's
Comment #8
janusman commentedI have just updated HEAD. So you can also start from that now =)
Comment #9
janusman commentedI have just updated HEAD. So you can also start from that now =)
Comment #10
dawehnerport has to wait for biblio module...
Comment #11
janusman commentedBeta of Biblio for D6 is available:
http://drupal.org/node/277712
Comment #12
greggles@janusman - from the project homepage - "NOTE: I have withdrawn the 6.x release until I can fix some critical bugs"
I guess that's what dereine is referring to.
Comment #13
janusman commentedOoops =) Right.
Perhaps it is still possible to test Biblio 6 in a test environment and proceed with the port; when Biblio 6 is released Millennium 6 can too...
Comment #14
oriol_e9gCould be useful to create a new 6.x branch in the CVS. Is it possible?
@greggles . Are you working with the porting? If not I can play with the Coder module this weekend :D
Comment #15
gregglesIf I'm working on this I'll steal the "assigned" column ;)
However, it seems like the first thing we need to do is make sure that the Biblio module is solid so that we can properly test/integrate with it. I'd suggest folks interested in seeing millennium upgraded start with biblio.
Comment #16
janusman commentedI will try to make the module compatible with CCK, so we don't necessarily have to wait for the Biblio module. Began working on this today... hopefully a preliminary dev version might be ready this week =)
Comment #17
janusman commentedI have a working module for D6; I'm still pondering whether removing biblio dependency is enough to warrant a change into a "2.x" version, which will probably have support for CCK and Biblio (when/if it comes out). Any thoughts? =)
Oh BTW the 6-dev version will probably become available by tonight or tomorrow morning.
Testers are MOST welcome!
Comment #18
janusman commentedOk, si I went and did it =)
The new version for D6 will be 2.0. The dev version is available now from this url:
http://drupal.org/node/333101
This is a currently working (bug free?), albeit non-optimal, version for D6.
UPGRADING INSTRUCTIONS
* If you are upgrading your site to D5 and D6, CURRENTLY there is NO DIRECT upgrade path, since
the Biblio module is not yet ready for production. An option is to "simply" re-import all your nodes from Millennium using the manual queue option in /admin/settings/millennium/queue_add
CHANGES FROM version 5.x-1.4
* New field added to millennium_node_opacitem table (must run update.php if you're upgrading your site from D5 to D6!)
* Now you need to specify a Content Type to import records into, in admin/settings/millennium. Your imported items inherit the workflow settings for that Content Type (e.g.: Promoted to home page, Published, Stickyness)
* Removed dependency on Biblio module. For now biblio data is written into the node's body and teaser; this will be changed to either the node body or mapping to CCK fields.
* New general.pot file for translation
* Added a link to the MARC version of item
* A lot of code cleanup
A demo is available at: http://prod68ws.ruv.itesm.mx/dev/6/
Comment #19
greggles@janusman - great work. I suggest adding all these notes onto the project page and/or the release node so that people ugprading will see them. Otherwise...folks could be in for a surprise ;)
Comment #20
janusman commented@greggles: done!
Comment #21
janusman commented