Bug #232
[PATCH]lack of support for extended entries
| Status : | Closed | Start : | ||
| Priority : | Normal | Due date : | ||
| Assigned to : | tobi - | % Done : | 0% |
|
| Category : | frontend | |||
| Target version : | 2.5 | |||
| Resolution : | fixed |
Description
The very nice mt3.rb import script properly imports extended entries from previous MT setups, but typo completely ignores them.
Should these merely be appended to the body of the entry and leave everything else alone? Or add an entry_html column, update transform methods, and modify read.rhtml templates?
Just seems like a waste to completely ignore this text, or leave this feature out completely.
History
07/10/2005 05:14 AM - kevin-sb-org -
Ok, I've attached a patch that fixes this ticket. It also fixes a problem with the live search, where it was putting the order of the arguments wrong, but I didn't bother separating that out because I modify the same line to add searching of extended entries as well.
The patch adds a migration, so be sure to run
rake migrateafter updating.
07/10/2005 03:44 PM - tobi -
- Status changed from Assigned to Closed
- Resolution set to fixed
(In r300) added extended entries support and fixed search (kevin@sb.org) closes #44, #129
07/19/2005 06:52 PM - tobi -
- Resolution set to fixed
(In r300) added extended entries support and fixed search (kevin@sb.org) closes #44, #129
07/19/2005 06:53 PM - tobi -
- Resolution set to fixed
(In r300) added extended entries support and fixed search (kevin@sb.org) closes #44, #129
