On a windows machine with wamp-apache-server:

Can't install the 'Intlinks' module by "Install new module" nor can I reach the Module page when I put the 'Intlinks' module into the mysite/sites/all/modules map.

Did it on a fresh install!

Anybody?

Comments

LoMo’s picture

Is that your directory structure: "mysite/sites/all/modules" ?

Normally added contrib modules should just be placed in "/sites/all/modules" or "/sites/mysite/modules".

By "fresh install" do you mean that no other contrib modules have been added?

franksweb’s picture

Yes I meant that my directory structure is /sites/all/modules (other wise my whole website would be blank.)
And by a fresh install I mean that I first tried the module on website full of Modules when the problem started. So I downloaded and installed drupal 7.12 fresh without any other module. So now I'm sure that it was not an interaction with an other module but the 'Intlinks' module Itself.

LoMo’s picture

Title: Can't install 'Intlinks' or reach the modulepage if 'Intlinks' is in modulemap » Can't install 'Intlinks' or reach modules page with 'Intlinks' in modules directory
Component: User interface » Code
Status: Active » Closed (cannot reproduce)

Yeah... I was just checking. I'm not sure what kind of problems that would cause, but since I've not seen any kind of problem like you describe (and there are over 400 sites using it), I could only suspect something might just be different on your system. I've have not tried using the "install new module" feature, but I just tried downloading the normal release (to replace a symlink to an in-development version I was experimenting with in m localhost D7 testing setup), just to make sure nothing was odd with the repository version here. I'm using Drupal 7.12, also... and I can't replicate your issue. The module doesn't seem to cause any problem when installed and it works.

I've no idea what else could be configured differently or what else could result in the problem you are experiencing, but with over 400 sites using the module, and no changes made to it recently, I can't imagine others are experiencing this same issue. For now, I'll close this as "cannot reproduce", but if you figure anything else out or can provide further details for how someone else might reproduce this issue, we can open it back up.

phoehne’s picture

Status: Closed (cannot reproduce) » Active

i can reproduce this.
like the op i'm using wamp(2.2) on win7.
i've broken down the problem to the description line of the info file.
simply shorten this line helps.
this is not a bug of intlinks. the infofile is syntax-correct.
there must be a weird constellation of wamp-config and the regex of the info-file parser, which kills the apache-php module.

perhaps this helps somebody

LoMo’s picture

Priority: Critical » Normal

If the problem is only for WAMP (it works in MAMP, so I'm surprised), I'll put the priority back on "normal", but that should be a very easy fix if all we have to do is shorten the description line in the info file.

How did you change it (how short) to be functional?

LoMo’s picture

Status: Active » Closed (fixed)

The current release has a much shorter description. Hopefully this should resolve the issue. Since this is a "fringe case" (apparently requires a dev environment with WAMP to replicate, and I don't have that here), I will mark this "fixed" — if it’s not resolved by the shorter description, please reopen this issue and indicate the length of the description which is necessary for this issue to be resolved.

LoMo’s picture

Title: Can't install 'Intlinks' or reach modules page with 'Intlinks' in modules directory » Can't install 'Intlinks' or reach modules page with 'Intlinks' in modules directory (WAMP)

Changed title to remind us that this is likely a WAMP-related issue (and help others using WAMP identify it and respond to it, e.g. whether or not current changes resolve the issue).

franksweb’s picture

This shorten the description line in the info-file did the trick!!!
Funny for me it was with the module 'Nap': Node access product.
Don't know why but it works

LoMo’s picture

Great news! Then marking this "fixed" was not (too) premature. ;-)

franksweb’s picture

Nope indeed. phoehne (http://drupal.org/node/1492510#comment-6282610) had the answer!

I also posted the solution in the issue queue of this module 'Nap': Node access product.

http://drupal.org/node/1777954

LoMo’s picture

Great work, franksweb. Thanks for confirming the adjustment fixed things. I wasn't sure how long was too long and how much trimming was enough.

FWIW — if others want to know how short I made it, i.e. what worked here, the current value of the description line is:
description = "Input filters which add node titles, as HTML 'title' attribute to internal links or unlinks unpublished nodes."

Including the description = and quotes, etc, that's 126 characters.

franksweb’s picture

Thnx LoMo,

And your description max characters is:

description = "Input filters which add node titles, as HTML 'title' attribute to internal links or unlinks unpublished nodes. yuioj kuh ijj yhnm jhyuio hjkhjui ttt hhhh okhggf ghjk iujhnbgthj yuioj kuh i"

i.e. 189 characters

N.B. Without the " " you can make it as long as you want !!!
i.e.
description = Input filters which add node titles, as HTML 'title' attribute to internal links or unlinks unpublished nodes. Input filters which add node titles, as HTML 'title' attribute to internal links or unlinks unpublished nodes. Input filters which add node titles, as HTML 'title' attribute to internal links or unlinks unpublished nodes. etc

This rule applies to the description information of all modules!!!

LoMo’s picture

Interesting. I noticed that the .info file in the latest Features-generated custom modules for a larger project I'm working on had changed when we updated to the latest version of Features and now no quotes are used to enclose the "value" for anything in the .info file. Anyway, I'm happy it's working and perhaps I'll even remove the quotes in a future release.

Thanks, again, franksweb. :-) And to phoenhe for the initial answer that helped resolve this.

@everyone: Please do reopen this issue if the latest release does not resolve this.