This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 20 October 2016 15:38 EEST
 Hi,

We've got problems indexing contents.
Could you please help us?
Thanks in advance.
Attachment
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Thursday, 20 October 2016 16:25 EEST
Hi there,

Please explain what exactly is the problem.
Yannis
Support Team
Thursday, 20 October 2016 17:22 EEST
I have attached the file Buscador-BOP.zip with the error and the component configuration.
Buscador-BOP.zip attached again.
Attachment
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Thursday, 20 October 2016 17:43 EEST
The generated error is:



The table '#__finder_tokens' is full



From the MySQL documentation:



If a table-full error occurs, it may be that the disk is full or that the table has reached its maximum size. The effective maximum table size for MySQL databases is usually determined by operating system constraints on file sizes, not by MySQL internal limits.


https://dev.mysql.com/doc/refman/5.7/en/full-table.html

This means that you probably have a hosting account with a very small db allocation.

Try this:
Go to administrator/index.php?option=com_config&view=component&component=com_finder
and change the setting Memory Table Limit to 20000.

If this does not solve the problem, it means that the INNODB settings in your hosting account are most probably set too low (like 128M).
(innodb_data_file_path, innodb_log_file_size, innodb_log_buffer_size)

You must contact your hosting provider, report them the error and ask them to raise the limit for the db allocation to a higher setting (like 1G or 2G).
Yannis
Support Team
Thursday, 20 October 2016 17:45 EEST
PS. You can also ask your hosting provider the raise the limit for max_heap_table_size.
Yannis
Support Team
Friday, 21 October 2016 11:12 EEST
Thanks Yannis. We have solved the indexing problem changing INNODB settings.

But the tool is not working properly now. It can't capture Onsubmit event inside the searcher. Other buttons are not working properly too (calendar button doesn't capture events for example)

Using inspector tool into navigator, following errors are shown:

Uncaught TypeError: jQuery(...).autocomplete is not a function --> buscador-nuevo:626

Uncaught TypeError: (intermediate value).spin is not a function --> buscador-nuevo:60

Could you please help us again?

Thanks in advance.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Friday, 21 October 2016 16:52 EEST
I'm trying to log in to the administrator but I get this error:



Se ha producido un error.

0 Cannot write to log file.

Yannis
Support Team
Friday, 21 October 2016 17:09 EEST
Ooops, I'm sorry. Please, try again.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Friday, 21 October 2016 20:43 EEST
Hi,

Have you been able to access into the administration area?. Have you seen which could be the problem?

Thank you very much.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Friday, 21 October 2016 23:01 EEST
Hi there,

I'm out of office at the moment. I will look into it as soon as possible and I'll let you know.
Yannis
Support Team
Saturday, 22 October 2016 19:16 EEST
There is a javascript conflict with your template when the parameter Search suggestions is enabled in the Global configuration.
The conflict may be caused by a 3rd party extension or by a script of your template.
However, when I reverted your website back to a default Joomla template (Protostar), then the Search suggestions was working fine, which leads me to beleive that the problem is caused by your template.

I had to disable that feature and now everything is working ok.
Yannis
Support Team
Monday, 24 October 2016 11:29 EEST
Ok Yannis, thank you very much. We are trying to fix the template problem.
Regards.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Monday, 31 October 2016 12:33 EET
Hi Yannis, after fixing template error, we've got a new problem:
We create filters in backoffice but not displayed at front.

Filters group attached (Buscador BOP.zip)

Thanks again.
Attachment
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Monday, 31 October 2016 16:03 EET
Hi there,

In the Minitek Smart Search menu item in your menu, make sure that you have selected the appropriate filters group in the field
General > Filters group
Yannis
Support Team
Monday, 31 October 2016 17:43 EET
Hi Yannis,

as you can see in pictures attached, the filter group is "Anuncios", and the filter "Municipios" is associated to Filters group "Anuncios".

But the tool is not working properly.

Is there anything else we can do?

Thanks.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Monday, 31 October 2016 17:45 EET
I already explained what you must do:

In the Minitek Smart Search menu item in your menu, make sure that you have selected the appropriate filters group in the field
General > Filters group

The images you are showing me have nothing to do with the menu. You must go to your menu, and find the menu item Minitek Smart Search.
Yannis
Support Team
Monday, 31 October 2016 18:53 EET
You're right. Thank you very much, Yannis.
It works fine.

Regards.
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Monday, 31 October 2016 19:00 EET
You're welcome.

Let me know if you need more help.
Yannis
Support Team
Friday, 04 November 2016 12:28 EET
Hello again Yannis,
Yes, it's me, your worst nightmare ;)

We've got new troubles:

The searcher tool doesn’t work searching by a specific date using “Exactly”.

Other trouble: We’d like searching by "Municipios" k2 extrafield. The tool shows the extrafields assigned for each k2 item (json array), but only Municipios’s literals are needed to show.

Could you please help us with these matters?

Front and backoffice captures attached (Desktop.zip)

Thank you very much.

Regards. Mar López
Attachment
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.
Monday, 07 November 2016 12:43 EET
Hi Mar,

I have fixed the issue with the exact date in version 1.0.3. It should be ok now.

In current version the component can not render the K2 extra fields values as filters
but I am planning to add extra fields compatibility in one of the next versions.

Yannis
Support Team
Wednesday, 09 November 2016 19:17 EET
Hi Yannis,

thanks for your help. We are expecting the extra fields compatibility in next versions.

Kind regards
Mar López
Ayla Diseño y Tecnología, S.L. Ayla Diseño y Tecnología, S.L.

This website uses cookies so that we can provide you with the best user experience. By clicking "continue" you agree to cookies being used in accordance with our Cookies Policy.

Search