All fields missing in registration pages after upgrade [#2968648]

Comment #1

2 May 2018 at 00:24

brandonlvFIT created an issue. See original summary.

Log in or register to post comments

Comment #2

rickj commented 2 May 2018 at 07:52

I think this may be a duplicate of #2961481.

Please apply the suggestion there in comment #2, and let me know the result. I hope to create a 1.5 release soon, once I've resolved these anomalies. Thanks.

Log in or register to post comments

Comment #3

brandonlv commented 2 May 2018 at 16:23

Assigned:

brandonlv

» Unassigned

Could you please link me to the latest dev build?
I assume this patch file? (https://www.drupal.org/files/issues/2018-03-29/profile2-dedupe_pre_rende...)
As a new user I'd be grateful for a guide on how to apply the patch in a Ubuntu LAMP environment.

Log in or register to post comments

Comment #4

rickj commented 2 May 2018 at 16:55

You can always find the latest dev version of a module (and any other versions) at the bottom of the main project page (https://www.drupal.org/project/profile2 in this case). You'll see a link "Development version: 7.x-1.x-dev updated ...", it will take you to a page with download buttons for the tar or zip file.

There isn't a way in the admin UI to update a module to a dev build. Do you have shell (command line) access to your server, and/or FTP or WebDAV access? The simplest way to update the module is simply to unpack the download into the existing module directory, overwriting the existing files (the directory is /sites/all/modules/profile2). To apply a patch, copy the patch file into the module directory and run the command: "patch -p1

You can either do this on the server, or locally then copy the files over, which one is easier depends on your configuration.

After updating the files it's usually best to clear the caches (in admin->performance).

There are other ways, but require other tools, such as drush (very useful, but something else to learn!).

Log in or register to post comments

Comment #5

brandonlv commented 2 May 2018 at 18:06

Would that work for downgrading the module as well? I only have a production server at the moment and am in the process of creating a dev environment where I could test the dev module. Reverting to the backup created before the update wold be counter productive as too much time has passed.

Log in or register to post comments

Comment #6

rickj commented 2 May 2018 at 18:24

Yes, you can downgrade this way, it will also work to upgrade instead of going through the admin UI. When Drupal lists the installed modules and versions, it is reading the .info files directly out of the module directories. it's not overly complicated.

The main rules are to clear the cache after any changes, and run update.php after an upgrade. This will perform any database updates that may be required by a new version, though if you know there are none you can skip this.