Problem/Motivation

Getting rid of custom schema and DB queries.

Proposed resolution

We could store the user settings as a field on user, or probably easier: using the user.data service (users_data table).

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#4 comment-notity-2618172-4.patch23.61 KBgnuget
#4 comment-notity-2618172-3-4-interdiff.txt3.6 KBgnuget
#3 2618172-3.patch20.02 KBgnuget
#2 2618172-2.patch27.48 KBgnuget
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Arla created an issue. See original summary.

gnuget’s picture

gnuget
Primary language Spanish
CreditAttribution: gnuget as a volunteer and at Agaric commented
Status: Active » Needs review
FileSize
2618172-2.patch27.48 KB

Ok.

Here a first try.

This still needs a hook_update to migrate the users from the old table to the userData table.

also, it needs another hook_update to delete the old table.

gnuget’s picture

gnuget
Primary language Spanish
CreditAttribution: gnuget as a volunteer and at Agaric commented
FileSize
2618172-3.patch20.02 KB
gnuget’s picture

gnuget
Primary language Spanish
CreditAttribution: gnuget as a volunteer and at Agaric commented
FileSize
comment-notity-2618172-3-4-interdiff.txt3.6 KB
comment-notity-2618172-4.patch23.61 KB

New patch this one includes the hook_update that migrate all the settings to the user_data table.

  • gnuget committed e0c90c4 on 8.x-1.x 
    Issue #2618172 by gnuget: Switch from custom schema '...
gnuget’s picture

gnuget
Primary language Spanish
CreditAttribution: gnuget as a volunteer and at Agaric commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.