Conflicts: db/migrate/093_add_redirections_model.rb db/migrate/096_add_origin_to_redirects.rb db/migrate/098_add_users_settings.rb db/migrate/100_adds_content_settings.rb db/migrate/101_adds_content_type.rb db/migrate/102_fixes_existing_articles_with_no_type.rb db/migrate/103_really_update_existing_articles_with_nil_or_empty_post_type.rb db/migrate/109_drops_typo_references_for_publify.rb db/migrate/111_moves_statuses_to_notes.rb db/migrate/112_fixes_notes_redirects.rb
Some techniques used: * To generate a clean schema up to 113: `rake db:drop db:create db:migrate VERSION=113` * All name: options for indexes were removed * To check match of the generated schema after the rollup: `rake db:drop db:create db:migrate`, followed by `git diff`
This migration does the following: * Picks up each category * Checks if a tag having the same permalink exists * If not, the tag is created * Every article using that category is added to the mentioned tag. * Category model is dropped There's no way back. Issue #332
…r version of Publify. Issue #246.
article Some specs refactoring too and new tests case
…tes perma short links
Indie Web "Standards" use the term "note" for "status" as it is less linked to a particular silo and does not have the timely meanning. Comes with a migration to move statuses to notes. Should I add one to rebuild all the perma short links as well? Also fixes the push to Twitter that was broken.