search index problem with product weight

[zabamich]

Since update from 1.6.0.9 to 11 I see problem with search index.

 

I trying set product name weight value but after saving is the same. blank field.

 

Any idea how to fiX this huge issue.

 

 

[NemoPS]

The back office seems a bit broken, try re-uploading the admin theme

[helldog2004]

Do the following and see if this fixes your problem.

Go to preferences --> Performance and at the end of the page disable caching.

save and go back to your product weight page to see if problem is resolved.

[zabamich]

admin theme re-uploaded and cache clean as well adt still the same.

[NemoPS]

Re-uploaded from a clean package? Try switching to another browser. Are you using anything like Cloudflare?

[tecnico-bl]

I have the same problems.

Not one word from prestashop.

It's incredible.

 

Some products are not shown in search results.

[NemoPS]

at this point it might be worth investigating the cause. Get the searchcron.php link from preferences>search, right where indexation is.

Enable error reporting and try running it. See if you get any error.

If not, open search.php (the class), look for the indexation() method, and start debugging from there. See which product breaks

[tecnico-bl]

Thank you for your help.

I've found a general problem in searchcron.php

 

This is the code:

 

if (!defined('_PS_ADMIN_DIR_')) define('_PS_ADMIN_DIR_', getcwd());
include(_PS_ADMIN_DIR_.'/../config/config.inc.php');
Context::getContext()->shop->setContext(Shop::CONTEXT_ALL);
if (substr(_COOKIE_KEY_, 34, 8) != Tools::getValue('token')) die;
ini_set('max_execution_time', 7200);
Search::indexation(Tools::getValue('full'));
if (Tools::getValue('redirect')) Tools::redirectAdmin($_SERVER['HTTP_REFERER'].'&conf=4');

 

 

The module set a max_execution_time wich is already defined in our server configuration (or in php.ini, if you use this).

 

Actually I don't know if this may create problems, but if I rem the line time is not taken from server configuration but automatically go to 30s.

[janoo]

Problem still remains. In PS 1.6.0.13 and 1.6.0.14 too. After changing number in Product name weight and saving form is there again empty field, or even worse - number is changed, but after refresh page or view page again through admin menu,

(BO > Preferences > Search) is this field empty again.

 

In database this field is not rewriten to new changed value but there is still old default 6 and also "date_upd" is zeroes.

Other values, like PS_SEARCH_WEIGHT_REF and so on are changed correctly.

 

PS_SEARCH_WEIGHT_PNAME is ignored and not on the form only. Searching on FO gives not exact results for searching product names.

So in product indexing is this problem too.

 

I´ve started issue:

http://forge.prestashop.com/browse/PSCSX-5739

Edited May 28, 2015 by janoo (see edit history)

[janoo]

Problem still remains. In PS 1.6.0.13 and 1.6.0.14 too. After changing number in Product name weight and saving form is there again empty field, or even worse - number is changed, but after refresh page or view page again through admin menu,

(BO > Preferences > Search) is this field empty again.

 

In database this field is not rewriten to new changed value but there is still old default 6 and also "date_upd" is zeroes.

Other values, like PS_SEARCH_WEIGHT_REF and so on are changed correctly.

 

PS_SEARCH_WEIGHT_PNAME is ignored and not on the form only. Searching on FO gives not exact results for searching product names.

So in product indexing is this problem too.

 

I´ve started issue:

http://forge.prestashop.com/browse/PSCSX-5739

 

.. after looong investigation and testing:

 

in my case is problem in database table 'ps_configuration_lang' where localization from sql file with wrong 'id_configuration' values for second language was imported.

 

So it was not about version or bug in files. It was 'typo infection' if sql is used for localization of many sities  

 

So for my case is this problem solved.

 

But maybe not for all other written above...

 

For compare wrong and repaired good data table check this image: