So this ticket is more of a bug notification and info for others searching the tickets like me.
I encountered an issue when I first installed Akeeba Backup for WP on two sites yesterday. It seems that when you create a new profile, Akeeba assigns them the ID "0", always.
The problem of course is that:
a) After the profile is created, you can't actually customise it. When you try to switch profiles, it keeps redirecting back to profile 1 (i.e. the Default Profile). I assume that's because of some logic that says "1" should be the lowest ID
b) You can't create another profile. So after the first profile you create is assigned the ID "0", when you try to create another profile, which is also given the ID "0", the database kicks up a "Not allowed to have duplicate ID" error.
My fix was to manually edit the profile IDs in MySQL (table name is something like akeeba_profiles). Once updates, normal functionality returns.
Perhaps a hotfix is needed?
I encountered an issue when I first installed Akeeba Backup for WP on two sites yesterday. It seems that when you create a new profile, Akeeba assigns them the ID "0", always.
The problem of course is that:
a) After the profile is created, you can't actually customise it. When you try to switch profiles, it keeps redirecting back to profile 1 (i.e. the Default Profile). I assume that's because of some logic that says "1" should be the lowest ID
b) You can't create another profile. So after the first profile you create is assigned the ID "0", when you try to create another profile, which is also given the ID "0", the database kicks up a "Not allowed to have duplicate ID" error.
My fix was to manually edit the profile IDs in MySQL (table name is something like akeeba_profiles). Once updates, normal functionality returns.
Perhaps a hotfix is needed?
