Problems & Errors
If encounter any error which seems to be caused by TSEP please let us know!
Please see the FAQ topic about this: When trying to index a (php) script the contents, not the result of the script is indexed - why?
This could have probably 2 reasons: Either your pages are really large - or you are trying to index too many pages at the same time.
"The same time" means here with the same profile. You should try to split the indexing of your site into different profiles. Each profile could handle specific files and/or directories of your site.
For example you could index all pages in /catalog with the profile called "Catalog" and all pages in /staff with the profile called "Staff" - thus splitting the workload, the time and memory TSEP needs to create an index for the pages in question.
If your pages are very large for example you could encounter a memory error. This is due to the memory restriction for php scripts set by the php.ini.
If you have access and are allowed to make changes to the php.ini file, you can change the value for memory_limit. The value is the number megabytes a single script is allowed to allocate. Example: memory_limit = 8
Since version 0941 we have introduced a what could be called protection state. Since in future of TSEP it could be fatal to the indexed data if the indexer is run twice at the same time we write a timestamp to the database once indexing begins. When indexing finished, you can index again as the value is set back. If the script stalls, e.g. the browser is closed the value can not be reset of course. You will have to wait a few minutes (see the maximum execution time of scripts on your server in configuration.php) before you can run the indexer again.
Please remember, that we did not put this check into the indexer to bug you but to ensure safety of your TSEP database (index).
Related topics / See also: "Maximum Execution Time Exceeded" error
This happens when you are trying to index a site but the indexing process takes too long. Too long means the script (in this case indexer.php) would need more time to complete running than allowed by PHP. There are several solutions to this:
- If you have access and are allowed to make changes to the php.ini file, you can change the value for max_execution_time. The value is the number of seconds a single script is allowed to run. Example: max_execution_time = 1200
- You can split the indexing process by defining several profiles and index those one by one.
Related topics / See also: I can not index!
We have been told that it can occur that you must switch of the "Before showing file in results test if it really exists?" setting in the configuration. This is probably due to a PHP safety setting (allow_url_open is probably disabled).
Please see PHP safety denies: Check if file exists
You need to open configuration.php once again - no changes are needed, but you must open the file once! That is where the TSEP path is saved. Now your installation should work fine again.
"Warning: set_time_limit(): Cannot set time limit in safe mode in /..../tsep/admin/indexer.php on line 110"
This is nothing really important. It shows only in the admin area. The error occurs when the safe-mode on the server is on. No problems except this are known at this time (concerning the safe-mode).
You might run into problems with MySQL v3.23 or lower. If you are running such a version we would be happy to hear if TSEP is working for you or and what kind of problems you have encountered.
We strongly recommend a MySQL database version >=4 !
Also see other FAQ: MySQL restrictions
It seems that with MySQL 5 alpha there are problems concerning the indexer.php. We will assume for now that is an issue of the new MySQL version and has nothing to to with TSEP.
Try populating the $db_table_prefix.config table by hand (using phpMyAdmin for example) with the values you find in the SQL scripts in the admin directory.