Connector submodule form Description is highlighting buggy WAMP install

Are you still having the issue ?

A lot of installation issues have been fixed recently !

Try the acquia dev desktop.
I see no concrete php warnings / errors that point to Kickstart, which makes me believe it's WAMP's fault.

Unfortunately, those notices don't give us enough information.

I'm having the same issue with my wamp setup. It appears to be caused by the connector module.

The sub-module info file connector_action_default_register_form.info has a long description name. For whatever reason this is what seems to be causing it. When the description is shortened it works just fine.

@segovia94

Operating system? Version? Amount of RAM?

connector_action_default_register_form is 38 characters long, which is not really much.
Still sounds like it's a bug in WAMP.

Not sure there's anything I can do.

@segovia94 & @bojanz -- This is a very credible bug in Windows, depending on whether you are running WAMP on Fat32, or perhaps using Microsoft Server 2003.

@segovia94, can you please post the FULL path to that file in your system? Down to C:/

http://superuser.com/questions/439387/specific-issue-with-long-pathnames... suggests that the limit is 259 characters long...

Josh

@joshmiller

Windows 7 64, 4g ram, WAMP 2.2, Apache 2.2.21, PHP 5.3.8

memory_limit = 300M

Here is the directory path.
C:\Users\Mark\Documents\Websites\d7\profiles\commerce_kickstart\modules\contrib\connector\modules\connector_action_default_register_form\connector_action_default_register_form.info

I use a virtual directory which is why this path is not in the C:\wamp\www directory.

This is obviously for a completely different module, but it appears that this is a description length issue out there as well. http://drupal.org/node/1165674.

Hey, I had the same problem, it crashed on the Second step in the installtion but I solved it now.

Go to the connector_action_default_register_form.info file and change the description to something shorter.

For example:

description = "Adepts the default action for new accounts. It does not create account by itself, but shows the register form, pre-filled with profile information from the connection. After register, it connects the connection to the new user account (for login in the future)."

To:

description = "Adepts the default action for new accounts."

#10 worked for me after not being able to get past step 1 of the 7.x-2.0-beta1 install.

Changing title and passing this issue to the module maintainer that has commit access to the description.

FWIW, this is a hard sell to "fix" something that is clearly "not broken" -- WAMP is choking on a paragraph of text? Really?

#10 rocks with an other slight modification of maximum execution time from 30 to 90

works for me.
i couldn't pass "Verify requirements", i change the description for a shorter one and it works.
\contrib\connector\modules\connector_action_default_register_form\connector_action_default_register_form.info
tanks christian P

I am also experiencing this error when installing on WAMPSERVER 2.2. I get the initial welcome screen. When I hit the "Let's Get Started" button, I get "This webpage is not available."

Tried to set the recursion limit in php.ini. The syntax looks a little different in my php.ini:

;PCRE library recursion limit. 
;Please note that if you set this value to a high number you may consume all 
;the available process stack and eventually crash PHP (due to reaching the 
;stack size limit imposed by the Operating System).
; http://php.net/pcre.recursion-limit
;pcre.recursion_limit=512

I also changed it in settings.php and default.settings.php as follows:

/**
 * If you encounter a situation where users post a large amount of text, and
 * the result is stripped out upon viewing but can still be edited, Drupal's
 * output filter may not have sufficient memory to process it.  If you
 * experience this issue, you may wish to uncomment the following two lines
 * and increase the limits of these variables.  For more information, see
 * http://php.net/manual/en/pcre.configuration.php.
 */
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 512);

Going to give the acquia deal a try next.

Derrr . . . Just realized I didn't uncomment those lines. Let's give this another shot.

php.ini snippet:

;PCRE library recursion limit. 
;Please note that if you set this value to a high number you may consume all 
;the available process stack and eventually crash PHP (due to reaching the 
;stack size limit imposed by the Operating System).
; http://php.net/pcre.recursion-limit
pcre.recursion_limit=512

settings.php/default.settings.php snippet:

/**
 * If you encounter a situation where users post a large amount of text, and
 * the result is stripped out upon viewing but can still be edited, Drupal's
 * output filter may not have sufficient memory to process it.  If you
 * experience this issue, you may wish to uncomment the following two lines
 * and increase the limits of these variables.  For more information, see
 * http://php.net/manual/en/pcre.configuration.php.
 */
# ini_set('pcre.backtrack_limit', 200000);
ini_set('pcre.recursion_limit', 512);

Restarted all services and tried install again - still no dice.

Installed acquia dev desktop and ran the install - worked just fine.

I don't want to install Acquia Dev (I use WAMP for other things and have found Acquia sometimes is a bit inflexible). Simply editing the description as per #10 solved the issue quite nicely for me, while just editing the pcre limit did not. Thanks!

Version 7.x-2.3 (2013-Feb-14) installation under WampServer 2.2 keeps the same old problem: it hangs at step 2) ('Verify requirements'). Applying this workaround #10 pointed by ChristianP lets the installation progress be completed.

I don't know why this trivial patch is not updated in the current distribution, instead of accusing Wamp of instability in favor of Acquia stack...

The attached patch is gonna be included in the next Kickstart release.

Attached patch that applies to .make files.

I've committed the patch from #24 and tagged a new beta-version to get around this issue

@morningtime: Seems like another issue? Perhaps open up a new issue for it so that it doesn't get lost in this issue? Especially since I think it's best to mark this one as fixed as it has gotten quite long and most seems to agree that the long description that #24 fixes is at least part of the issue and thus this should have been fixed for most.

You should have added a new line at the end of the file.
See http://drupalcode.org/project/connector.git/commitdiff/c200cee?hp=e4bbe3... it says "No newline at the end of file", this line is needed.

@jsacksick: Needed as in it won't work otherwise or needed as it being going coding style?

I know it's at least good git practise to have all files should end with a newline, but it's also good practice to keep all commits atomic so a fix for this would have to be a separate coding style commit and I'm sure there can be other coding style fixes found that can be done at the same time then. Perhaps we should start a coding style cleanup issue?

I can confirm that setting

ini_set('pcre.recursion_limit', 584);

Solves the problem in my WAMP 2.2 x64 bits installation, see comments in #16 and #25, and thank you very much morningtime !!

Still not working for me, WAMP 2.2, tried everything I could think of, including the solutions on post #16 and #25.

Any solution guys? It is quite an old bug, plenty time to fix.

Re-open? Actual for Apache 2.4 branch with PHP 5.4.14

Same bug with Win 7 64bits / WAMP 2.2 64bits php 5.3.13 apache 2.2.22
Tried above solutions without success.
Found solution applying the following on drupalcommerce.org : installing using wampserver

I could begin installation after disabling Xdebug. Maybe simply try this first :)

So, I have been having the same issue and it dawned on me after reading through all of these possible solutions and also attempting many of them, that there is a consistency in several people mentioning the usage of 64 bit WAMP as I also was. I decided to remove the 64 bit and replace it with 32 bit and VOILA!! It WORKS! So, just dump 64 bit WAMP and problem solved!

Edit: So I noticed the errors that everyone was complaining about during installation. This occurred with me during the module installation and the store front installation. What I did to resolve this:

• drop all entries from database
• delete entire commerce kickstart directory
• edit the WAMP php.ini file:
• max_execution_time = -1
• max_input_time = -1
• memory_limit = 512M
• download and extract fresh copy of commerce kickstart into wamp directory
• start a new installation of commerce kickstart

After switching over to 32bit WAMP, formatting my database and installing a new copy of commerce kickstart, everything functioned 100% without errors. Cheers! ;-)

Detailed step by step instructions for n00bs have been documented here: http://www.zrtechnologies.com/content/drupal-commerce-kickstart-installation-solution

Have fun with kickstart!
Zahir Narsisto Rodulfo
ZRTECH - ITS
http://www.zrtechnologies.com

I experienced a problem with the maximum path length (MAX_PATH) which was solved by changing the Drush temporary directory.

See: http://drupal.stackexchange.com/a/183323/16078

I'd like also to note that there are plenty of VM solutions available that aren't Acquia Dev Desktop, for example https://github.com/geerlingguy/drupal-vm