It will get blank page, but that's OK, return to your Drupal site and try searching.
Later you might want to install poormanscron.module which is easy and will do the cron.php for you for every 60 minutes or more.
Every time a new content is added, do the cron.php and immediately after that you can search for the new content
Good luck
________________________________________________________________________________
Internet for ISLAM, get to know Islam and Muslims :) May Allah brings you to the Straight Path http://muslimin.org/Islam
----------------------------
No, one should either setup cron properly (crontab, scheduler), use poormanscron or a webbased cron service. To execute cron manually is madness.
-- Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.
I think what Muslim Guy was saying is that if you want the new content indexed right away, you can call cron.php manually via a browser. Doing manual calls all the time isn't a viable answer, but works fine if don't want to wait for a cron based re-index.
Back to the original post. Is it a problem with indexing or a problem w/ the search form not returning results even after indexing? If it's indexed but the search form isn't returning results, check your logs and see if you're getting an error when trying to create a temporary table.
If it's a temporary table issue, ask your host to grant you CREATE TEMPORARY TABLE rights, or see http://drupal.org/node/49644 for a workaround.
For a newbie who is used to system like SMF Forum, it is expected that the Search function works rightaway. Alas, this is not the case with Drupal.
The newbie who doesnt know anything about cron or poormanscron or what is a crontab, will be dumbfounded.
BTW thanks to Drupal community who is alyways ready to answer newbies, any problem will be solved, turns out that it is not really a problem (nothing wrong with Drupal) but because the newbie's level of knowledge with CMS, PHP, LAMP is limited. But he will feel sense of accomplishment if he figures something all by himself :)
excuse me :) yes, it works! I tried to type ../cron.php and the search began to work after that. Well, now I intend to install the poormanscron.module and look at the result. Thanks very much! Its beautiful!
What I don't understand is why is n't indexing been done when new content is created.
At any time I can see the percentage of indexing of the site at "admin/settings/search".
So there is a way (function probably) to check if there are unindexed nodes.
Wouldn't it save a lot of resources (running a cron job every 10 or 15 minutes or even 60)
to index right after content creation ?
Not everyone has the search module enabled when content is created. Since Drupal is a modular system, there are many people who have had sites up and running for a while before activating the module in question.
For example, I created a website (www.mybragpage.com) and imported ~1500 nodes via a script . After importing all the information, I remembered that I had not turned on the search module. If the search index could not be updated via cron.php, then all of those posts would never have been added to the search.
While it might be possible to update the search whenever a node is added or updated, I am certain that it would cause many large scale node imports to fail. Some people are switching over HUGE websites to the Drupal structure, and the resources required to update the search index after each addition would most likely cripple these transitions.
In the end, I just accessed cron.php through the browser several times in succession, and had the search index up to date after a few minutes. Now, cron jobs do the dirty work. ;o)
I did not say that it should not be done through cron.php but that I find it a waste of resources on the server to be calling a cron job every hour to do indexing when in fact you have one new content every day.
And I don't judge the design or anybody but just trying to learn.
In my mind cron.php could be called after each content creation and only if the search was activated.
Is it possible to be done this way ?
Cron.php is not just for the search module. It is available to every module that might need to perform some action at a specified time interval (i.e. send e-mails, perform database operations, etc.).
Now, if you are asking whether or not the search update procedures can be called when a node is created/updated, then that is a different question.
I suppose it could be incorporated into the workflow, but then you have the potential bottleneck when doing large inserts or updates. While this may not apply to you, it could definitely be an issue with many users. I for one would not want my script to time out on my 478th out of 1500 node insert. Granted these are not an everyday occurrence, it is a very real possibility, and must be taken into account by the developers.
I am not one of the active developers (although I have enjoyed getting to know the Drupal system) and cannot fully explain all of their reasoning, but I do see some wisdom in separating the search indexing time from the node creation. Sure, it is a compromise, but one that was neither lightly decided nor sloppily implemented. It just has to be properly configured.
BTW, don't be afraid to ask questions. Very few heads have been bitten off lately. ;o)
To activate content indexing right after a content creation, the way is to manually call cron.php, and have the poormanscron set to every 60 minutes. If the site is a busy one, like Drupal.org, I am curious to know how Drupal.org indexes new contents fast.
Comments
cron.php
Did you setup cron?
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.
Cron.php
One thing for an excellent CMS like Drupal is that it still doesnt set up search indexing - newbie has to learn and do it himself :)
You have to type this in your web browser
http://yourdomain.com/cron.php
Or if Drupal is installed in a folder named `mydrupalsite'
http://yourdomain.com/mydrupalsite/cron.php
It will get blank page, but that's OK, return to your Drupal site and try searching.
Later you might want to install poormanscron.module which is easy and will do the cron.php for you for every 60 minutes or more.
Every time a new content is added, do the cron.php and immediately after that you can search for the new content
Good luck
________________________________________________________________________________
Internet for ISLAM, get to know Islam and Muslims :) May Allah brings you to the Straight Path
http://muslimin.org/Islam
----------------------------
What?
No, one should either setup cron properly (crontab, scheduler), use poormanscron or a webbased cron service. To execute cron manually is madness.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.
Index now
I think what Muslim Guy was saying is that if you want the new content indexed right away, you can call cron.php manually via a browser. Doing manual calls all the time isn't a viable answer, but works fine if don't want to wait for a cron based re-index.
Back to the original post. Is it a problem with indexing or a problem w/ the search form not returning results even after indexing? If it's indexed but the search form isn't returning results, check your logs and see if you're getting an error when trying to create a temporary table.
If it's a temporary table issue, ask your host to grant you CREATE TEMPORARY TABLE rights, or see http://drupal.org/node/49644 for a workaround.
Niosop
For a newbie who is used to
For a newbie who is used to system like SMF Forum, it is expected that the Search function works rightaway. Alas, this is not the case with Drupal.
The newbie who doesnt know anything about cron or poormanscron or what is a crontab, will be dumbfounded.
BTW thanks to Drupal community who is alyways ready to answer newbies, any problem will be solved, turns out that it is not really a problem (nothing wrong with Drupal) but because the newbie's level of knowledge with CMS, PHP, LAMP is limited. But he will feel sense of accomplishment if he figures something all by himself :)
yes, it works!
супер! класс!...
excuse me :) yes, it works! I tried to type ../cron.php and the search began to work after that. Well, now I intend to install the poormanscron.module and look at the result. Thanks very much! Its beautiful!
Best regards,
Imark
@ Muslim Guy
What I don't understand is why is n't indexing been done when new content is created.
At any time I can see the percentage of indexing of the site at "admin/settings/search".
So there is a way (function probably) to check if there are unindexed nodes.
Wouldn't it save a lot of resources (running a cron job every 10 or 15 minutes or even 60)
to index right after content creation ?
from a newbie
--
chios sightseeings
------
GiorgosK
Web Development
Not everyone
Not everyone has the search module enabled when content is created. Since Drupal is a modular system, there are many people who have had sites up and running for a while before activating the module in question.
For example, I created a website (www.mybragpage.com) and imported ~1500 nodes via a script . After importing all the information, I remembered that I had not turned on the search module. If the search index could not be updated via cron.php, then all of those posts would never have been added to the search.
While it might be possible to update the search whenever a node is added or updated, I am certain that it would cause many large scale node imports to fail. Some people are switching over HUGE websites to the Drupal structure, and the resources required to update the search index after each addition would most likely cripple these transitions.
In the end, I just accessed cron.php through the browser several times in succession, and had the search index up to date after a few minutes. Now, cron jobs do the dirty work. ;o)
-Corey
I don't really see your
I don't really see your point,
I did not say that it should not be done through cron.php but that I find it a waste of resources on the server to be calling a cron job every hour to do indexing when in fact you have one new content every day.
And I don't judge the design or anybody but just trying to learn.
In my mind cron.php could be called after each content creation and only if the search was activated.
Is it possible to be done this way ?
--
chios sightseeings
------
GiorgosK
Web Development
Clarification
Cron.php is not just for the search module. It is available to every module that might need to perform some action at a specified time interval (i.e. send e-mails, perform database operations, etc.).
Now, if you are asking whether or not the search update procedures can be called when a node is created/updated, then that is a different question.
I suppose it could be incorporated into the workflow, but then you have the potential bottleneck when doing large inserts or updates. While this may not apply to you, it could definitely be an issue with many users. I for one would not want my script to time out on my 478th out of 1500 node insert. Granted these are not an everyday occurrence, it is a very real possibility, and must be taken into account by the developers.
I am not one of the active developers (although I have enjoyed getting to know the Drupal system) and cannot fully explain all of their reasoning, but I do see some wisdom in separating the search indexing time from the node creation. Sure, it is a compromise, but one that was neither lightly decided nor sloppily implemented. It just has to be properly configured.
BTW, don't be afraid to ask questions. Very few heads have been bitten off lately. ;o)
I DONNO :) It's just the
I DONNO :) It's just the way Drupal works ?
To activate content indexing right after a content creation, the way is to manually call cron.php, and have the poormanscron set to every 60 minutes. If the site is a busy one, like Drupal.org, I am curious to know how Drupal.org indexes new contents fast.