Discussions

Error message

  • Warning: include_once() [function.include-once]: Unable to allocate memory for pool. in drupal_settings_initialize() (line 712 of /mnt/www/html/dcorg/docroot/includes/bootstrap.inc).
  • Warning: require() [function.require]: Unable to allocate memory for pool. in require() (line 520 of /mnt/www/html/dcorg/docroot/sites/default/settings.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 20 of /mnt/www/site-php/dcorg/dcorg-settings.inc).
  • Warning: require() [function.require]: Unable to allocate memory for pool. in require() (line 78 of /mnt/www/site-php/dcorg/dcorg-settings.inc).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in acquia_hosting_db_choose_active() (line 194 of /mnt/www/site-php/dcorg/D7-prod-dcorg-settings.inc).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in acquia_hosting_db_choose_active() (line 231 of /mnt/www/site-php/dcorg/D7-prod-dcorg-settings.inc).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 45 of /usr/share/php/Net/DNS.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 46 of /usr/share/php/Net/DNS.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 47 of /usr/share/php/Net/DNS.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 48 of /usr/share/php/Net/DNS.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 49 of /usr/share/php/Net/DNS.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 21 of /usr/share/php/Net/DNS/RR.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 22 of /usr/share/php/Net/DNS/RR.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 23 of /usr/share/php/Net/DNS/RR.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 24 of /usr/share/php/Net/DNS/RR.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 25 of /usr/share/php/Net/DNS/RR.php).
  • Warning: require_once() [function.require-once]: Unable to allocate memory for pool. in require_once() (line 26 of /usr/share/php/Net/DNS/RR.php).

Log In new user account for anonymous after checkout

Is it possible to log in a newly created user after they checkout and an account is created with their email address? The summary shows links that the user can click on if they are logged in, but they aren't accessible to an anonymous user.

Posted: Jun 13, 2012

Comments

Simon Georges on July 9, 2012

Hi,

I've published a sandbox that adds a "immediate login" rules to new account creation so the user ends up logged in. Let me know if it doesn't work for you.

domineaux on July 9, 2012

I got the git file. I forgot to init my local folder.

I notice you mention needing a rule for immediate login.
Maybe you could do a walk through for building the rule as you have it working.

Also, I think a password should be created ASAP when customer creates account.
Email should be used as login UID, entering email twice is not a bad idea either. It will eliminate errors for users.
Email for UID will usually eliminate any possible dups or nicknames that people don't keep up with on sites they don't use often.
All the back and forth to email annoys people.

Verfication of email is critical for sure, but I'm not sure of a best way to verify without customer responding to email clickon or something along those lines.

Simon Georges on July 10, 2012

Unfortunately, the Rules action uses some Drupal core code, so I had to programmatically create the action. That said, once the action is created, you just could manually add it through the interface to the appropriate existing Commerce rule. I try to do it automatically to limit the actions needed by the module user to have it working, but it's totally do-able.

drupalcommerce Check out the #Drupal Commerce 2.x Roadmap to see where you can get involved: http://t.co/WAc3jmXY2a
drupalcommerce A new blog discussing the new showcase listing http://t.co/FHOzhAg3tl http://t.co/J5C87imjhb
drupalcommerce RT @drupalcon: Thanks @CommerceGuys and @CommerceJohn for your support, and for #CommerceKickstart! Take the tour http://t.co/ivKEYH7k0o
drupalcommerce Updating our extensions directory: 665 new or updated modules, distributions, sandboxes, & themes. http://t.co/6NMMofYo12 #weloveyouguys