Discussion:
[Typo3] Indexed Search - Content not indexed
Jose Cortina
20 years ago
Permalink
Hi list

I have been strugling with the indexed search plugin for several hours, and I am pretty sure the problem lies in the cache options of the pages, but I need a coupple of pointers. Here my scenario:

The server has TYPO3 version 3.7.0 with Indexed Search Engine (2.1.3) and Cache All (0.2.2) extensions installed & loaded. Additional information about other extensions is provided at the end of this post (in case some other extension might be creating the problem).

After configuring the indexed search as described in the documentation, I browsed several pages (also after logging out from the Typo3 backend), but I can't get the content to get indexed (Indexing module stats show all zeros and Web->Info->Indexed Search shows no records at all).

I now believe this has to do with some cache problem, since I installed the Cache All, and that is unable to cache any page (I have even monitored the typo3 database directly with a simple "select count(*) from cache_pages" query, but still returns zero).

I have reviewed all my templates and scripts in search for the no_cache directive, but found nothing which appears to be active... Some references are also included in the standard templates I use (such as styles.content) but still as far as I can tell they are inside some condition block which is not applicable. I have also logged into the frontend to check the Cache page of the Admin Panel, and the checkbox from "No caching" is cleared.

Is there any other way of determining if a page is being cached or not, and to try to determine where the behaviour comes from?

- Jose

Current loaded extensions
-------------------------------------
CSS styled content
Template auto-parser
Page Template Selector
Page PHP Content
Address list
Web>Plugins
New front end login box
LDAP
Page HTTP/HTTPS Enforcer
Press center
Web>Plugins, Direct Mail
Direct Mail Subscription
Meta tags, extended
Web>Plugins, Direct Mail - Extended
Indexed Search Engine
Cache All

-----------------------
The mailing list archive is found here:
http://typo3.org/documentation/mailing-lists/english-main-list-archive/
Dmitry Dulepov
20 years ago
Permalink
Hi!

Do you have "page.config.index_enable = 1" in constants of your template?

Dmitry.
...
Mathias Schreiber [wmdb>]
20 years ago
Permalink
Post by Dmitry Dulepov
Do you have "page.config.index_enable = 1" in constants of your template?
this normally goes into "Setup" not "Constants"

all the best
mattes
--
if ($GLOBALS['TSFE']->fe_user->user['ahnung'] == 0) {
$this->fresseHalten = 1;
}
Jose Cortina
20 years ago
Permalink
Hi Dmitry, Hi Mathias,

Thank you for your replies. I have indeed set the index_enable as described in the documentation (and above by you) but still no luck... I think my problem is not really related to the indexing, but rather to the cache, and I need to find why TYPO3 is not saving the cache.

I have looked at all the TSConfig's and template codes I have, as well as many page configuration options, and I found no no_config = 1 or a checked box for "No Cache". I'm sure there is one - somewhere deep in the code - but I don't feel like spending hours looking for it.

Is there any (easier) way to determine why is the cache from TYPO3 not saving?

Thanks!


- Jose
-----------------------
This thread is located in the archive at this URL:
http://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/110129820/
Jane Larsen
20 years ago
Permalink
Have a similar problem, nothing shows in the indexing page (zeros or
nothing) and when I try to search I get "no results" all the time (even if
some pages should be indexed).

The basic search plugin (not indexed) works fine but as soon as I switch the
problem shows again. I have made the:
config.index_enable = 1
entry in setup section (tried with page in front too)

Hope you find a solution to you problem (hopefully mine too)

//Jane Larsen
...
tapio
20 years ago
Permalink
Post by Jane Larsen
Have a similar problem, nothing shows in the indexing page (zeros or
nothing) and when I try to search I get "no results" all the time (even if
some pages should be indexed).
The basic search plugin (not indexed) works fine but as soon as I switch the
config.index_enable = 1
entry in setup section (tried with page in front too)
Hope you find a solution to you problem (hopefully mine too)
This seems to be bug in 3.7.0 - in 3.8.0 indexed search works fine.
EXECPT that it needs more than 16 MB in php.ini setting => doesn't
work most of my installations - infact just in one installation, which
has been set 50 MB in php.ini
...
Jane Larsen
20 years ago
Permalink
I have one 3.7.0 install (hosted so I don't know the complete setup) where
indexed search works fine...

Any known bug fixes?

//Jane
...
Dmitry Dulepov
20 years ago
Permalink
Same for me: works fine.

Dmitry.
...
Dmitrii Dimandt
20 years ago
Permalink
Post by Dmitry Dulepov
Same for me: works fine.
Dmitry.
Has Indexed Search changed for Typo3.8? If so, this could happen
because of incompatibility problems? The default Indexed Search
installation worked fine for me until I downloaded the new version fro
the repository.
Michael Stucki
20 years ago
Permalink
Post by Dmitrii Dimandt
Has Indexed Search changed for Typo3.8? If so, this could happen
because of incompatibility problems? The default Indexed Search
installation worked fine for me until I downloaded the new version fro
the repository.
Yes, that's exactly the point! Any indexed_search version except the one
that comes with TYPO3 3.8.0 is _incompatible_ with the new release.

I think the reason was that there is just a hook missing, so it could be
quite easy to fix that...

- michael
--
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
Dmitry Dulepov
20 years ago
Permalink
Michael,

if I remember correctly, plugin can be marked compatible only with a
specific version of typo3. Should indexed_serach be marked
appropriately? Or I am wrong?

Dmitry.
...
Dmitrii Dimandt
20 years ago
Permalink
Post by Dmitry Dulepov
Michael,
if I remember correctly, plugin can be marked compatible only with a
specific version of typo3. Should indexed_serach be marked
appropriately? Or I am wrong?
Dmitry.
Ok, decided to give Typo3.8 a try. Installed, no problem. And then the
Indexed Seacrh plugin started behaving erraticaly. At first it would
index _only_ menus - that left me buffled, really. All I could get out
of it was menus. It wouldn't index content.

Now it doesn't index anything at all. This happened after I put the
<!--TYPO3SEARCH_begin> and <!--TYPO3SEARCH_end> markers around my
content. I am truly buffled.

Please, those whose IS works fine, please tell us what you did (or
didn't do) to make it work. *begs on his knees*
Eva Gabriel
20 years ago
Permalink
hey I have a similar problem :
indexed search gives me every pages if the searched word is in the menu

how can I tell indexed search to search only in page content ?

I put the <!--TYPO3SEARCH_begin> and <!--TYPO3SEARCH_end> markers
too, but it doesn't change anything !
I am on typo3 3.8.0 and using templavoila

but when I search a word which is not in a menu, it gives me the good page.
maybe it can help you, here is my typoscript for the template :


# INDEXED SEARCH

plugin.tx_indexedsearch.search.rootPidList = 1
page.config.index_enable = 1
page.config.index_externals = 1
plugin.tx_indexedsearch.show.rules = 0

page.config.language = fr

plugin.tx_indexedsearch.show.L1sections = 0
plugin.tx_indexedsearch.show.L1sections = 1

hum, I don't know what's the use of these 2 final lines... does someone know ?
if I leave only one putting 0 or 1 as value, it doesn't change anything !

Saya
...
Irene Höppner
20 years ago
Permalink
Hi,
Post by Eva Gabriel
I put the <!--TYPO3SEARCH_begin> and <!--TYPO3SEARCH_end> markers
too, but it doesn't change anything !
I am on typo3 3.8.0 and using templavoila
but when I search a word which is not in a menu, it gives me the good page.
Did you empty the index-tables? You can do that with the module web>info;
choose "indexed search" on the right top function-menu and click on the
red wastebasket.
Pages are indexed only every several days (depending on your
configuration), which means, that you might get some "old information"
after you inserted the markers.
Post by Eva Gabriel
plugin.tx_indexedsearch.show.L1sections = 0
plugin.tx_indexedsearch.show.L1sections = 1
hum, I don't know what's the use of these 2 final lines... does someone know ?
if I leave only one putting 0 or 1 as value, it doesn't change anything !
Goto the advanced search form and check the selectbox where you can choose
between whole website,...
You should see some changes there ;-).
Post by Eva Gabriel
Post by Dmitrii Dimandt
Ok, decided to give Typo3.8 a try. Installed, no problem. And then the
Indexed Seacrh plugin started behaving erraticaly. At first it would
index _only_ menus - that left me buffled, really. All I could get out
of it was menus. It wouldn't index content.
Now it doesn't index anything at all. This happened after I put the
<!--TYPO3SEARCH_begin> and <!--TYPO3SEARCH_end> markers around my
content. I am truly buffled.
Just an idea: the indexer stops indexing, if he finds an opening < in the
source code. So if you use something like "< back to the list" instead of
"&lt; back to the list" you make the indexer stop working (tt_news single
view makes these problems ;-)). Might produce problems with rootlines like
blubb > flupp too?!

Greets: Irene
Eva Gabriel
20 years ago
Permalink
...
Hum yeah ! now the search doesn't find anything, just like dmitrii !
I visited some pages in frontend and searched again but still no result :(
Post by Irene Höppner
Just an idea: the indexer stops indexing, if he finds an opening < in the
source code. So if you use something like "< back to the list" instead of
"&lt; back to the list" you make the indexer stop working (tt_news single
view makes these problems ;-)). Might produce problems with rootlines like
blubb > flupp too?!
do you think that something like <td> may stop the search ? it would
be stupid but who knows...

Saya
Irene Höppner
20 years ago
Permalink
...
Has anything been indexed? The question is, if the indexer doesn't work or
if the search doesn't work...
Post by Eva Gabriel
do you think that something like <td> may stop the search ? it would
be stupid but who knows...
no!
Eva Gabriel
20 years ago
Permalink
In fact I needed to be logged out from the BE to start indexing !
now I'm back to my first problem : it indexes evertything, including
menus, eventhough I put markers of begin and end search
...
Eva Gabriel
20 years ago
Permalink
Ok, now it works !
I think it was due to a bad placement of my <begin> and <end> markers...
it was in a <td> and it didn't like it !

thanks a lot for your help

Saya
...
Gabriel Junquera
20 years ago
Permalink
Hola Jos? and cia.,

I had a similar problem too, which description you can see in the "caching"
thread of june (there's a message out of the thread due to a not anwered
mail, probably like this, as I have the receiving deactivated, by the way,
does anybody know how can I include a message in a thread without
responding?).
Post by tapio
This seems to be bug in 3.7.0 - in 3.8.0 indexed search works fine.
EXECPT that it needs more than 16 MB in php.ini setting => doesn't
work most of my installations - infact just in one installation, which
has been set 50 MB in php.ini
then you should take that into consideration, but you should also search for
any extensions, hidden or not, that may disable the cache by:

$GLOBALS["TSFE"]->set_no_cache();

My problem was I had one somewhere, but was so small that I did not take it
into consideration. You must also remember to log you off in the backend to
make the testing, because that may also disable caching. The combination of
these to issues kept me wandering for two weeks.

Hope that helps

Gabriel
Post by tapio
I have been strugling with the indexed search plugin for several hours, and
I am pretty sure the problem lies in the cache options of the pages, but I
Post by tapio
The server has TYPO3 version 3.7.0 with Indexed Search Engine (2.1.3) and
Cache All (0.2.2) extensions installed & loaded. Additional information about
other extensions is provided at the end of this post (in case some other
extension might be creating the problem).
Post by tapio
After configuring the indexed search as described in the documentation, I
browsed several pages (also after logging out from the Typo3 backend), but I
can't get the content to get indexed (Indexing module stats show all zeros
and Web->Info->Indexed Search shows no records at all).
Post by tapio
I now believe this has to do with some cache problem, since I installed the
Cache All, and that is unable to cache any page (I have even monitored the
typo3 database directly with a simple "select count(*) from cache_pages"
query, but still returns zero).
Post by tapio
I have reviewed all my templates and scripts in search for the no_cache
directive, but found nothing which appears to be active... Some references
are also included in the standard templates I use (such as styles.content)
but still as far as I can tell they are inside some condition block which is
not applicable. I have also logged into the frontend to check the Cache page
of the Admin Panel, and the checkbox from "No caching" is cleared.
Post by tapio
Is there any other way of determining if a page is being cached or not, and
to try to determine where the behaviour comes from?
Continue reading on narkive:
Loading...