Hi,
Thank you for the information. Do you know what the Drupal Module does
exactly? Is it only a wrapper in order to present the result (from SOLR), or
does it have further function(s)?
----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 31 May 2011 08:29:49 -0600
> From: Karyn Cassio <karyn(a)karyncassio.com>
> Subject: Re: [development] SOLR
> To: development(a)drupal.org
> Message-ID: <4DE4FB5D.6040803(a)karyncassio.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I just used apachesolr_multisitesearch and it worked excellently.
> You will need to install drupal.org/project/apachesolr first, and then
> configure apachesolr_multisitesearch to work with it.
>
> The latter extends the basic apachesolr module, which is based on apache
> solr.
> So, the first thing you will need to do is install apache solr on your
> system, or whichever system you would like to act as your apache solr
> server. (Yes, it can be the same server as you host your site.
>
> Read the documentation, especially if you are new to Drupal and Apache
> Solr. The instructions are pretty clear as to how to set everything up.
>
> Hope this helps.
>
> Karyn
> (Techgirlgeek)
>
> On 05/29/2011 11:31 PM, Cameron Eagans wrote:
> > c'mon...http://tinyurl.com/4yqbley
> >
> > apachesolr_multisitesearch is what's used on drupal.org
> > <http://drupal.org>. You might start there.
> > --
> > Cameron Eagans
> > http://cweagans.net
> >
> >
> > On Sun, May 29, 2011 at 23:10, Dragomilov <dragomilov(a)gmail.com
> > <mailto:dragomilov@gmail.com>> wrote:
> >
> > Hi,
> >
> > I need a multi-site search system but I am new in Drupal search.
> > Firstly I tried http://drupal.org/project/multisite_search however
> > it didn't work well, some words wasn't indexed. So I began to
> > planning on setting up SOLR in order to use
> > http://drupal.org/project/apachesolr_multisitesearch. (Google
> > option is not sutiable for us.) Then I notice that there is a
> > module such as http://drupal.org/project/nutch. So I am confused.
> >
> > Is there anybody who could explain difference between these
> > modeule (even pure SOLR search)? I am also open to any suggestion
> > about search, any module, SOLR w/o Drupal modules, any other
> > search options...
> >
> > Thank you all in advance...
> >
> >
>
>
>
Hi,
I need a multi-site search system but I am new in Drupal search. Firstly I
tried http://drupal.org/project/multisite_search however it didn't work
well, some words wasn't indexed. So I began to planning on setting up SOLR
in order to use http://drupal.org/project/apachesolr_multisitesearch.
(Google option is not sutiable for us.) Then I notice that there is a module
such as http://drupal.org/project/nutch. So I am confused.
Is there anybody who could explain difference between these modeule (even
pure SOLR search)? I am also open to any suggestion about search, any
module, SOLR w/o Drupal modules, any other search options...
Thank you all in advance...
Hi all,
I have a module that uses quite a few variables and would like to remove
them in my hook_uninstall() function, but I don't want to have to list
them all manually...
I see three ways to do this:
1 - Run variable_del() for each variable manually
2 - List all variables then remove the ones that start with my module's name
3 - Delete variables directly from the database that start with my
module's name
I'm obviously trying to avoid #1.
I've used #2 before (http://drupalbin.com/18718) but am worried about
the possible performance implications of running a foreach() on every
variable in Drupal... Is this good or not?
I'd prefer not to resort to using SQL to delete variables from the
database directly as in #3, but this may be the only recommended option...
What is the recommended way to call variable_del() on a bunch of
variables? I'm using D7 if that helps.
Thanks.
--
Kind regards,
Peter Anderson.
http://panda.id.au
Hello developers,
We're building a site that has a form in a block in one of our
sidebars. If the user enters incorrect values, the form validation
happens correctly, and errors are flagged up. However the messages
such as:
'The title field is required'
Appear in the main messages region, at the top of the page content,
which is nowhere near our form on the page, which is in a sidebar. The
fields in the form are highlighted, so the user can see that something
is wrong with the input, but the messages are a mile away.
Is there any module or method for getting the validation messages for
the current form in the location of the form itself, and out of the
global messages? Or any effort to get something like this into core?
I'm happy to code something if I need to, just wondered if anyone had
tackled this before?
Regards
Steven Jones
ComputerMinds ltd - Perfect Drupal Websites
Phone : 024 7666 7277
Mobile : 07702 131 576
Twitter : darthsteven
http://www.computerminds.co.uk
thank u all for comments, this really helped. But I'm still curios how I can
really do this anyway? There's a lot of other tokens I can use exept date.
On Wed, May 25, 2011 at 5:46 AM, Lee Rowlands <contact(a)rowlandsgroup.com>wrote:
> in your preprocess_node hook set the date time how you want it with
> $vars['mydate'] = format_date($vars['node']->updated, 'custom', 'd/m/Y');
> change the d/m/Y to suit
>
>
>
> On Wed, 2011-05-25 at 05:39 +0430, Pooya wrote:
>
> Thank u :) I want to have "node submit time" the exact way I want, so I
> checked out tokens available in devel(when viewing story node type) and
> found out there are already enough details I need in tokens(like small day,
> long day name,...). All I want is to <span> some of these tokens the way I
> want in template, I'm gonna check out this token_replace() to see what I can
> do with. maybe finish the job in preprocess and then use it in
> node-story.tpl.php
>
>
>
> Never done this before, not sure if it's even possible to use tokens
> passed to node.
>
>
>
> If I'm missing sth or there's anything u can help me with share, It's a
> lot time saver at this point. Thanks for your time :)
>
>
>
>
> On Wed, May 25, 2011 at 5:10 AM, Michael Favia <michael.favia(a)gmail.com>
> wrote:
>
> On 05/24/11 18:08, Pooya wrote:
> > Is it possible to print tokens( I can see in Token tab of devel module
> > in a node) in theme? like simple echo or something?
> > I want to use it in node-story.tpl.php
>
> While you can probably call a token replacement function token_replace()
> they are usually reserved for plaintext user input in the UI. You have
> direct access to most variables required inside the template or
> preprocess function. If you elaborate a little further about your goal
> id be happy to help you do this ina more "drupalesque" fashion itll also
> give you more power in your regular theming.
>
> --
> Michael Favia michael(a)favish.com
> tel. 512.669.5650 http://www.favish.com
>
>
>
>
> --
>
> Pooya Sanooei
>
> Twitter <http://twitter.com/sourcesoft> - Facebook<http://facebook.com/pooya.sanooei>-
> Website <http://www.javabgoo.com>
>
>
>
>
>
--
Pooya Sanooei
Twitter <http://twitter.com/sourcesoft> -
Facebook<http://facebook.com/pooya.sanooei>-
Website <http://www.javabgoo.com>
Good morning,
Using Views 3 and Drupal 7.
I have created a page display with a single exposed filter for taxonomy term id. There is a feed display attached to this view. When I click on the link for the feed the filter settings e.g. ?tid=2 is passed onto the feed's path e.g. /blog.xml?tid=2
Is there a simple way for me to allow the feed display to be filtered by this argument? I tried using a contextual filter (argument), but it appears to be looking for /2 and not for ?tid=2
Thanks in advance,
Everett Zufelt
http://zufelt.ca
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
I am working on the Content Migrate module to migrate field data from
D6 to D7. Many things are now working nicely but I have a nasty
problem that has erupted in various ways around what value to use for
the 'language' in the fields that are migrated.
Here is what happens on a fresh D7 install, without migration:
- If you create new fields in the UI, all every field is created with
the flag 'translatable' set to TRUE. There is no apparent way to
create a field in the UI that has 'translatable' set to FALSE.
- If you create new fields using field_create_field() 'translatable'
is set to FALSE, unless you explicitly set a value for 'translatable'
and set it to TRUE,
This looks like a bad idea, having opposite defaults for the two
methods of creating fields. So any process that uses the API to create
fields will create fields that are inconsistent with fields created in
the UI, unless it follows the UI pattern of forcing every field to be
translatable. Plus every process that creates fields programmatically
has to explicitly set that value to avoid unexpected results.
Core has already been bit by this confusion -- the migrated node body
field is marked as translatable but the migrated comment body is *not*
translatable.
Plus there really should be some way for a field weigh in on this.
Things like number and date fields should probably not be
translatable, but there seems to be no way a field module can control
that.
I have been trying to sort through the migration issues in
http://drupal.org/node/1063852, if anyone wants to help. I tried to
see if any core issues were filed around this but couldn't see any.
I'm trying to get my head around which of these are 'bugs' and which
are just things I have to work around. I do not even use translations
myself, so it's very hard for me to be sure I am drawing the right
conclusions. I hope someone who does understand the translation system
can jump in here.
