Index broken??
Permalink
I think I broke the search index. I modified the index_search.php to add the line:
$is->addSearchableArea('Main Content 1');
The thing I did wrong was I had added the line first to the to the very end of the file and ran the search index update which didn't work. Then I searched the forums and saw where to put the line in the middle of the "function run()" section.
My final code:
Now after 2 hours the site is still indexing and when I refresh the page it says "Currently Running (Since 12:49:20 PM)"
Does anyone know how to fix this?
$is->addSearchableArea('Main Content 1');
The thing I did wrong was I had added the line first to the to the very end of the file and ran the search index update which didn't work. Then I searched the forums and saw where to put the line in the middle of the "function run()" section.
My final code:
<?php /** * * Responsible for loading the indexed search class and initiating the reindex command. * @package Utilities */ defined('C5_EXECUTE') or die(_("Access Denied.")); class IndexSearch extends Job { public $jNotUninstallable=1; function getJobName() { return t("Index Search Engine"); } function getJobDescription() { return t("Index the site to allow searching to work quickly and accurately."); }
Viewing 15 lines of 26 lines. View entire code block.
Now after 2 hours the site is still indexing and when I refresh the page it says "Currently Running (Since 12:49:20 PM)"
Does anyone know how to fix this?
Ryan,
Thanks for the fast solution. Sorry I'm not very well versed in sql - where do I run the query?
Thanks for the fast solution. Sorry I'm not very well versed in sql - where do I run the query?
Do you have phpMyAdmin installed? It's usually setup on hosted accounts in cpanel or account manager.
Does it not like spaces in the content area name? ("Main Content 1")
check that a apache or php timeout isn't occuring.
Sorry for my novice question. I'm am running on a shared server at arvixe.com. I have cPanel access. How do I check for a timeout?
That'll reset the job, basically when a job has completed it sets the status back to ENABLED, but if it dies mid-way it's status is left running.