aboutsummaryrefslogtreecommitdiffstats
path: root/lib/ephy-profile-migrator.c
Commit message (Collapse)AuthorAgeFilesLines
* ephy-profile-migrator: allow running migration in non-default profile ↵Claudio Saavedra2012-09-041-1/+9
| | | | | | | | | | | | | directories This is necessary since we add new columns to the history database in step 8 of migration. However, non-default profile directories don't have a .migrated file right now but, since up to step 7 it was possible to use these profiles without migration, it is safe to assume that a non-default profile without a .migrated file can be migrated starting from step 8. https://bugzilla.gnome.org/show_bug.cgi?id=681679
* ephy-profile-migrator: add a "requested version" option to the migratorXan Lopez2012-09-011-0/+9
| | | | This will allow us to catch mismatches between browser and migrator binary.
* ephy-profile-migrator: New migrator for history backend changesClaudio Saavedra2012-09-011-1/+46
| | | | This adds a couple of new required columns to the urls table.
* ephy-profile-migrator: do nothing if there's no profile dirXan Lopez2012-08-291-0/+12
| | | | | | | | If there's no profile dir there should not be anything to do for the profile migrator (since in theory epiphany has never been executed). This might backfire for people that manually mess with their profile dir (removing it), but those people hopefully know what they are doing.
* ephy-profile-migrator: allow to run just one migration stepXan Lopez2012-05-101-7/+53
| | | | Use --do-step/-d and an index.
* ephy-profile-migrator: migrate Web Applications to new profile locationXan Lopez2012-05-091-1/+86
| | | | | | | | | | We need to update their desktop files (they had references to the profile directory) and the symlink of the .desktop file in the Shell applications directory. It would be much easier to just delete and re-add the applications, but unfortunately that would wipe out the existing profile data in the apps (like cookies).
* ephy-profile-migrator: better safe than sorry in history migrationXan Lopez2012-05-091-11/+9
| | | | Do nothing if the destination history file already exists.
* ephy-profile-migrator: migrate the profile dir location before anything elseXan Lopez2012-05-091-4/+4
| | | | | Otherwise we'll read the .migrated file *before* we move the old profile. Not OK, it will make us start from scratch all the migration
* Based on a patch by Jon McCann.Xan Lopez2012-05-081-0/+63
| | | | | | Migrate profile directory to XDG config dir https://bugzilla.gnome.org/show_bug.cgi?id=522810
* Allow for more fine-grained file helpers initXan Lopez2012-05-081-1/+1
| | | | | | | | | | Since we are about to migrate our profile dir, allow file helpers init to not ensure the profile dir exists (it was hardcoded until now). For this we get rid of the ugly boolean parameters and add a flags parameter, which preserves the old behaviors and allows for this new option. We update all the callers in the tree.
* Create a new 'tabs-bar-visibility-policy' settingXan Lopez2012-04-161-1/+17
| | | | | | We need this to be an enum, since we'll a third option in the future for the Overview (to never show the tabs bar). For now just add the two values we have now and migrate the code and the user data.
* profile-migrator: do not freak out if the history is emptyXan Lopez2012-03-211-4/+6
| | | | | | | If the old history file exists but has no actual visits we'll enter into an infinite loop. https://bugzilla.gnome.org/show_bug.cgi?id=672547
* ephy-history-service: make the async API cancellableClaudio Saavedra2012-03-131-1/+1
| | | | | | | | | | | The main purpose of the cancellable API in ephy-history-service is to let the user notify when the results of the operation are no longer needed and the callback call can be omitted. Since performing a read operation, in such cases, makes no sense, we cancel them altogether. However, given the nature of the service, we don't cancel write operations. https://bugzilla.gnome.org/show_bug.cgi?id=671901
* ephy-profile-migration: only create ad-hoc hosts for non-default zoom levels.Xan Lopez2012-03-071-6/+4
| | | | | | Otherwise the default code path is enough. Also, the host is always going to be NULL for newly created URLs, so double check this is the case and don't try to handle anything else.
* Store zoom levels per host, not per URLXan Lopez2012-03-071-6/+18
| | | | | | | | | | Zoom levels have always been stored per host in Epiphany, not per URL (otherwise you'd have to re-apply the zoom level again and again when visiting, say, every news entry in your favorite newspaper). Change things to work like that. Note: this changes the SQL table format for the history, so you'll need to re-migrate your history.
* ephy-profile-migrator: update to migrate also zoom level preferencesClaudio Saavedra2012-03-071-0/+7
|
* ephy-profile-migrator: migrate history to the new formatXan Lopez2012-03-071-1/+194
|
* ephy-profile-migrator: use new g_utf8_substringXan Lopez2011-07-051-19/+2
|
* ephy-profile-migrator: call g_type_init explicitlyXan Lopez2011-05-131-1/+1
|
* ephy-profile-migration: separate migration code into another binaryDiego Escalante Urrelo2010-12-071-0/+470
The migration code is now in the ephy-profile-migrator binary, this means: - epiphany is not linking to NSS anymore - lib/ephy-profile-migration.c was split into: + lib/ephy-profile-migrator.c: the new ephy-profile-migrator binary + lib/ephy-profile-utils.c: convenience _ephy_profile_*_form_auth_data functions. - testing for migration is done without running ephy-profile-migrator Bug #636685