Recently a user gave us some feedback[1] using the integrated Get Satisfaction tab in the app (it works!) that a comparison chart of MT vs Melody features is needed. Upon review I agree! I need the communities help on this one though because making a useful one requires a delicate balance of saying too little and saying too much.
But first some news on the next release, Melody 1.0 RC2. We'll be releasing it sometime on this coming Tuesday, March 22nd. Things are shaping up nicely and we are fairly optimistic that this will be the last distribution before the big one we've all been waiting for.
Back to the comparison chart document.
I took a quick cut at it using the MT features page[2] and trying to remove what seemed to me to be too vague (read: marketing fluff). I've posted an initial draft of it on the Github wiki here:
It needs a lot of work IMO, but that's where you come in.
As I said, creating a useful feature comparison chart is a delicate balance. Defining what is a feature is a rather wide open and relative thing. Speaking for myself as a veteran developer, I could list numerous things that most wouldn't understand let alone care about. Likewise, other functionality I take for granted or think is trivial could be vital to an end user. Jay thought this was best discussed and debated as a community to avoid that sort of thing from happening. I must agree.
I've made a few additions and changes to the table.
One of the things that confuses me a little is why Multiblog Aggregation is not marked as a feature of all systems. I'm not sure if this might've simply been overlooked or if the feature you were thinking of is something else?
On Thu, Mar 17, 2011 at 9:13 PM, Timothy Appnel <t...@appnel.com> wrote: > Recently a user gave us some feedback[1] using the integrated Get > Satisfaction tab in the app (it works!) that a comparison chart of MT > vs Melody features is needed. Upon review I agree! I need the > communities help on this one though because making a useful one > requires a delicate balance of saying too little and saying too much.
> But first some news on the next release, Melody 1.0 RC2. We'll be > releasing it sometime on this coming Tuesday, March 22nd. Things are > shaping up nicely and we are fairly optimistic that this will be the > last distribution before the big one we've all been waiting for.
> Back to the comparison chart document.
> I took a quick cut at it using the MT features page[2] and trying to > remove what seemed to me to be too vague (read: marketing fluff). I've > posted an initial draft of it on the Github wiki here:
> It needs a lot of work IMO, but that's where you come in.
> As I said, creating a useful feature comparison chart is a delicate > balance. Defining what is a feature is a rather wide open and relative > thing. Speaking for myself as a veteran developer, I could list > numerous things that most wouldn't understand let alone care about. > Likewise, other functionality I take for granted or think is trivial > could be vital to an end user. Jay thought this was best discussed and > debated as a community to avoid that sort of thing from happening. I > must agree.
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
I left Multiblog Aggregation blank for a couple of reasons -- chief among them was that confused me a bit. Did it mean Multiblog and Sites or Action Streams. I'm guessing the former, but I wasn't sure. Even so, I was thinking perhaps we should clarify the differences in their implementation. <tim/>
What is the projected version when Melody will start supporting custom fields? I want to move my sites to Melody, but one of them requires custom fields support.
All available resources are be steered towards finally shipping 1.0. So not sure yet unless of course you are volunteering to get to work on it. ;)
Right Fields is open source and (I'm told) will run in Melody. It needs work though before I would personally feel comfortable putting it in core distro. For instance, I don't think there is a migration script for moving from CF to RF.
<tim/>
Sent from my iPhone
On Mar 18, 2011, at 16:38, "Reed A. Cartwright" <r...@scit.us> wrote:
> What is the projected version when Melody will start supporting custom fields? I want to move my sites to Melody, but one of them requires custom fields support.
> Cuiusvis hominis est errare, nullius nisi > insipientis in errore perseverare. --Cicero
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
Does RightFields have a home nowadays? Staggernation.com seems to be out to pasture.Speaking of comparisons, I'd love to see a feature comparison of Custom Fields, Right Fields, and Field Day ( https://github.com/movabletype/mt-plugin-field-day).
On Fri, Mar 18, 2011 at 2:54 PM, Timothy Appnel <t...@appnel.com> wrote: > All available resources are be steered towards finally shipping 1.0. So not > sure yet unless of course you are volunteering to get to work on it. ;)
> Right Fields is open source and (I'm told) will run in Melody. It needs > work though before I would personally feel comfortable putting it in core > distro. For instance, I don't think there is a migration script for moving > from CF to RF.
> <tim/>
> Sent from my iPhone
> On Mar 18, 2011, at 16:38, "Reed A. Cartwright" <r...@scit.us> wrote:
> > What is the projected version when Melody will start supporting custom > fields? I want to move my sites to Melody, but one of them requires custom > fields support.
> > Cuiusvis hominis est errare, nullius nisi > > insipientis in errore perseverare. --Cicero
> > -- > > You received this message because you are subscribed to the Google > > Group for the OpenMelody Project (http://openmelody.org) > > To post to this group, send email to openmelody@googlegroups.com > > To unsubscribe from this group, send email to > > openmelody+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/openmelody?hl=en
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
On Fri, Mar 18, 2011 at 6:06 PM, Rick <wrink...@gmail.com> wrote: > Does RightFields have a home nowadays? Staggernation.com seems to be out to > pasture.Speaking of comparisons, I'd love to see a feature comparison of > Custom Fields, Right Fields, and Field Day ( > https://github.com/movabletype/mt-plugin-field-day).
> Rick Bychowski
> On Fri, Mar 18, 2011 at 2:54 PM, Timothy Appnel <t...@appnel.com> wrote:
>> All available resources are be steered towards finally shipping 1.0. So >> not sure yet unless of course you are volunteering to get to work on it. ;)
>> Right Fields is open source and (I'm told) will run in Melody. It needs >> work though before I would personally feel comfortable putting it in core >> distro. For instance, I don't think there is a migration script for moving >> from CF to RF.
>> <tim/>
>> Sent from my iPhone
>> On Mar 18, 2011, at 16:38, "Reed A. Cartwright" <r...@scit.us> wrote:
>> > What is the projected version when Melody will start supporting custom >> fields? I want to move my sites to Melody, but one of them requires custom >> fields support.
>> > Cuiusvis hominis est errare, nullius nisi >> > insipientis in errore perseverare. --Cicero
>> > -- >> > You received this message because you are subscribed to the Google >> > Group for the OpenMelody Project (http://openmelody.org) >> > To post to this group, send email to openmelody@googlegroups.com >> > To unsubscribe from this group, send email to >> > openmelody+unsubscribe@googlegroups.com >> > For more options, visit this group at >> > http://groups.google.com/group/openmelody?hl=en
>> -- >> You received this message because you are subscribed to the Google >> Group for the OpenMelody Project (http://openmelody.org) >> To post to this group, send email to openmelody@googlegroups.com >> To unsubscribe from this group, send email to >> openmelody+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/openmelody?hl=en
FYI, I've got an MT Pro installation that I've upgraded to Melody. I didn't remove the Community.pack and Commercial.pack, and the features those offer (including custom fields) seem to work without problem. Neither of these solutions are open source and will certainly not become the "preferred" solution... but hey, it works for me.
When Tim says Right Fields I'm pretty sure he means its successor, Field Day.
Dan
On Fri, Mar 18, 2011 at 4:38 PM, Reed A. Cartwright <r...@scit.us> wrote:
> What is the projected version when Melody will start supporting custom > fields? I want to move my sites to Melody, but one of them requires custom > fields support.
> Cuiusvis hominis est errare, nullius nisi > insipientis in errore perseverare. --Cicero
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
Revision history is available in MTOS 5 Multiblog Aggregation is too
Integrated Feedback System would benefit from a link explaining what this is (when I read it I thought: "Huh? I can manage feedback from within MT as well!").
Streamlined “Compact” Entries and Pages listing: for a fair comparison, there should be an entry about the listing framework in MT/MTOS 5, since you can customize many lists (not just two) easily now (as opposed to views set in stone by the developers, as these listings might be, I guess).
Pet peeve of mine from the non-ASCII world :p : level of I18N/L10N support (e.g. how many languages supported by the interface)
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
>> -- >> You received this message because you are subscribed to the Google >> Group for the OpenMelody Project (http://openmelody.org) >> To post to this group, send email to openmelody@googlegroups.com >> To unsubscribe from this group, send email to >> openmelody+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/openmelody?hl=en
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
I'm looking to merge two MT installs together and then possibly migrate the union to Melody. Anybody have any experience doing this? What are the for doing this?
Here are my specs:
Install #1: 1 very very very large blog with 30+ authors Install #2: 8 small blogs and 2 authors together
As to MT, the main point with merging is to avoid ID conflicts, so make sure that you update your IDs in each table before combining the two databases. The real challenge is to make sure that you update the corresponding IDs as needed - for example, when you update entry IDs, make sure you update the comments that point to those IDs, etc. It is not difficult, but you need to be careful with it to make sure you get them all and that it will all be happy in the end with the combined database.
Once done, migrating to Melody should not be especially difficult.
Chad Everett Everitz Consulting
On Sat, Mar 26, 2011 at 8:39 PM, Reed A. Cartwright <r...@scit.us> wrote:
> I'm looking to merge two MT installs together and then possibly migrate the > union to Melody. Anybody have any experience doing this? What are the for > doing this?
> Here are my specs:
> Install #1: 1 very very very large blog with 30+ authors > Install #2: 8 small blogs and 2 authors together
But if you export those sites, the import process, IIRC, will take care of assigning unique IDs for everything on the receiving end. The real problem is if you have made the mistake of using those IDs as is in your templates, assuming that they'll never change.
> As to MT, the main point with merging is to avoid ID conflicts, so make sure that you update your IDs in each table before combining the two databases. The real challenge is to make sure that you update the corresponding IDs as needed - for example, when you update entry IDs, make sure you update the comments that point to those IDs, etc. It is not difficult, but you need to be careful with it to make sure you get them all and that it will all be happy in the end with the combined database.
> Once done, migrating to Melody should not be especially difficult.
> Chad Everett > Everitz Consulting
> On Sat, Mar 26, 2011 at 8:39 PM, Reed A. Cartwright <r...@scit.us> wrote: > I'm looking to merge two MT installs together and then possibly migrate the union to Melody. Anybody have any experience doing this? What are the for doing this?
> Here are my specs:
> Install #1: 1 very very very large blog with 30+ authors > Install #2: 8 small blogs and 2 authors together
> Both installs use postgresql.
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
On 3/27/2011 12:38 AM, Fran ois Nonnenmacher wrote:
> But if you export those sites, the import process, IIRC, will take care > of assigning unique IDs for everything on the receiving end. The real > problem is if you have made the mistake of using those IDs as is in your > templates, assuming that they'll never change.
Can this be done from the command line? One of my blogs is too big to do this through a webserver.
On 27 Mar 2011, at 06:38, François Nonnenmacher wrote:
> But if you export those sites, the import process, IIRC, will take care of assigning unique IDs for everything on the receiving end. The real problem is if you have made the mistake of using those IDs as is in your templates, assuming that they'll never change.
While exporting/importing is a good solution, it doesn't work if you are using custom fields.
If you want to merge two blogs then, you need to get dirty with the database.
> On 27 Mar 2011, at 06:38, François Nonnenmacher wrote:
>> But if you export those sites, the import process, IIRC, will take care of assigning unique IDs for everything on the receiving end. The real problem is if you have made the mistake of using those IDs as is in your templates, assuming that they'll never change.
> While exporting/importing is a good solution, it doesn't work if you are using custom fields.
I meant the backup feature, not the old import/export one, sorry. CF are saved through a backup (I just tested).
> If you want to merge two blogs then, you need to get dirty with the database.
Tricky and highly error prone.
Try the backup/restore, really, it's not difficult to try and see if it works :)
> > On 27 Mar 2011, at 06:38, François Nonnenmacher wrote:
> >> But if you export those sites, the import process, IIRC, will take care > of assigning unique IDs for everything on the receiving end. The real > problem is if you have made the mistake of using those IDs as is in your > templates, assuming that they'll never change.
> > While exporting/importing is a good solution, it doesn't work if you are > using custom fields.
> I meant the backup feature, not the old import/export one, sorry. CF are > saved through a backup (I just tested).
> > If you want to merge two blogs then, you need to get dirty with the > database.
> Tricky and highly error prone.
> Try the backup/restore, really, it's not difficult to try and see if it > works :)
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
On Sun, Mar 27, 2011 at 8:48 PM, François Nonnenmacher
<li...@padawan.info> wrote: > Try the backup/restore, really, it's not difficult to try and see if it works :)
Which version are you talking about? I tried to use the backup/restore in MT 4.35 and it failed. Two issues that came to mind was the generated file was too large that it choked and it created all new authors even though they already existed. I simply don't trust it and wouldn't recommend it to anyone personally.
> On Sun, Mar 27, 2011 at 8:48 PM, François Nonnenmacher > <li...@padawan.info> wrote:
>> Try the backup/restore, really, it's not difficult to try and see if it works :)
> Which version are you talking about? I tried to use the backup/restore > in MT 4.35 and it failed.
Tried 4.35, but limiting the backup to just a test blog to see if CF were exported. This was on a server with 4GB of RAM, so might not have the same limits.
Bit of a long shot this, given the general push towards 1.0, but... has anyone managed to get Field Day working with Melody?
I may have a rather pressing need for such a thing, having - possibly - been dumped in a fairly serious predicament by my long-term hosting partners. Straight from Github, Field Day installs itself and shows up in the menus, but throws "Can't call method "param" on an undefined value" errors immediately (App.pm, line 424).
If Commercial.pack works then I guess I could deploy that, but I'm assuming Field Day will eventually become the preferred option for Melody.
[context: Melody is hosting this: http://scicast.org.uk, a UK national competition for short science films, primarily from schools. Unfortunately, when I took it upon myself to rebuild the site this year I decided to tough it out with the existing film archive and leave it on our 'partner's system. A system which, as of Friday, appears to have been pulled. Fingers crossed they've messed up and can bring it back up on Monday, but it's possible they finally noticed they're still hosting us and deliberately pulled the plug.
Hence, I'm starting a crash effort to rebuild the film archive. In about a week. For 400 films. With a team of: me.]
On 22 Mar 2011, at 12:32, Dan Wolfgang wrote:
> FYI, I've got an MT Pro installation that I've upgraded to Melody. I > didn't remove the Community.pack and Commercial.pack, and the features > those offer (including custom fields) seem to work without problem. > Neither of these solutions are open source and will certainly not > become the "preferred" solution... but hey, it works for me.
> When Tim says Right Fields I'm pretty sure he means its successor, Field Day.
-- Jonathan Sanderson "If I had more time, I would have written a shorter letter" (Pascal)
> Bit of a long shot this, given the general push towards 1.0, but... has anyone managed to get Field Day working with Melody?
> I may have a rather pressing need for such a thing, having - possibly - been dumped in a fairly serious predicament by my long-term hosting partners. Straight from Github, Field Day installs itself and shows up in the menus, but throws "Can't call method "param" on an undefined value" errors immediately (App.pm, line 424).
> If Commercial.pack works then I guess I could deploy that, but I'm assuming Field Day will eventually become the preferred option for Melody.
> [context: Melody is hosting this: http://scicast.org.uk, a UK national competition for short science films, primarily from schools. Unfortunately, when I took it upon myself to rebuild the site this year I decided to tough it out with the existing film archive and leave it on our 'partner's system. A system which, as of Friday, appears to have been pulled. Fingers crossed they've messed up and can bring it back up on Monday, but it's possible they finally noticed they're still hosting us and deliberately pulled the plug.
> Hence, I'm starting a crash effort to rebuild the film archive. In about a week. For 400 films. With a team of: me.]
> On 22 Mar 2011, at 12:32, Dan Wolfgang wrote:
>> FYI, I've got an MT Pro installation that I've upgraded to Melody. I >> didn't remove the Community.pack and Commercial.pack, and the features >> those offer (including custom fields) seem to work without problem. >> Neither of these solutions are open source and will certainly not >> become the "preferred" solution... but hey, it works for me.
>> When Tim says Right Fields I'm pretty sure he means its successor, Field Day.
> -- > Jonathan Sanderson > "If I had more time, I would have written a shorter letter" (Pascal)
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
> Don't know an answer to the Field Day error, but commercial pack will work. So could be the route out if you need something to 'save your bacon'!
Thanks, Matt - good to know. Field Day looks awfully nice, but this may be a situation for expediency over engineering. Mind you, that defines my whole project to date, so...
Looks like I'll tackle Custom Fields in the morning.
-- Jonathan Sanderson "If I had more time, I would have written a shorter letter" (Pascal)
I actually asked Byrne about Field Day and he said there should be no problem. I am saddened there is a problem. I will build the latest version of Melody from GitHub and install FieldDay to see if that throws that error or not.
Ken
On Sat, Apr 2, 2011 at 6:34 PM, Jonathan Sanderson <jonat...@quernstone.com>wrote:
> Bit of a long shot this, given the general push towards 1.0, but... has > anyone managed to get Field Day working with Melody?
> I may have a rather pressing need for such a thing, having - possibly - > been dumped in a fairly serious predicament by my long-term hosting > partners. Straight from Github, Field Day installs itself and shows up in > the menus, but throws "Can't call method "param" on an undefined value" > errors immediately (App.pm, line 424).
> If Commercial.pack works then I guess I could deploy that, but I'm assuming > Field Day will eventually become the preferred option for Melody.
> [context: Melody is hosting this: http://scicast.org.uk, a UK national > competition for short science films, primarily from schools. Unfortunately, > when I took it upon myself to rebuild the site this year I decided to tough > it out with the existing film archive and leave it on our 'partner's system. > A system which, as of Friday, appears to have been pulled. Fingers crossed > they've messed up and can bring it back up on Monday, but it's possible they > finally noticed they're still hosting us and deliberately pulled the plug.
> Hence, I'm starting a crash effort to rebuild the film archive. In about a > week. For 400 films. With a team of: me.]
> On 22 Mar 2011, at 12:32, Dan Wolfgang wrote:
> > FYI, I've got an MT Pro installation that I've upgraded to Melody. I > > didn't remove the Community.pack and Commercial.pack, and the features > > those offer (including custom fields) seem to work without problem. > > Neither of these solutions are open source and will certainly not > > become the "preferred" solution... but hey, it works for me.
> > When Tim says Right Fields I'm pretty sure he means its successor, Field > Day.
> -- > Jonathan Sanderson > "If I had more time, I would have written a shorter letter" (Pascal)
> -- > You received this message because you are subscribed to the Google > Group for the OpenMelody Project (http://openmelody.org) > To post to this group, send email to openmelody@googlegroups.com > To unsubscribe from this group, send email to > openmelody+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/openmelody?hl=en
WARNING/CAUTION: This e-mail and any files transmitted with it are strictly confidential and are intended solely for the use of the individual(s) or entity to whom it is addressed. This communication may contain material protected by business-confidentiality rules and regulations. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail and any file attachments is strictly prohibited.
