phd38

I added the check_table_exist() call to secure the transition to 4.0. I will remove in a next release as it seems the transition went well.

How many tags do you have on your site ?

I will also investigate to decrease the SQL consumption, that’s a work I have to do since the plugin grew and was enhanced with many features, which consume.

This search can fail in case of huge mass of data – which I understand is your case. It happens also to me from time to time, depending on the SQL server loading.

Thanks, I will put the CSS in the list.

Consider 4.0.4.

BTW – I am a developper, not an expert in CSS. Any help to rationalize the style coding… I take.
I did as much as I could but focused my effort on providing a reliable code.

Also fixed the default mode switchable for both search and result.

I fixed the search format.

Concerning the output format, please make sure to run a new search, not just refreshing the search page – otherwise the FORM elements will be used and the default setup overwritten.

It works fine on my side, I tested it in many different cases.

Can you please confirm your issue and, if relevant, describe all the steps you are taking ?

Done – please checkout.

I will fix it quick and provide as 4.0.1.

OK – I got the point. 3.2.1 widget options are stored in options “wpit_widget” in the database.

Starting 4.0 it is stored in “mediatagger_widget”.

I need to set a bridge from one to the other. In any case, a simple copy/paste will be enough meanwhile, not too big deal.

Very sorry for the emotion and thanks for the feedback ??

Sorry to read this – I went through really extensive testing before releasing.

What’s the conclusion at the end , Did you have to work around some aspects ?

Hello,

It may be caused by an english text hard coded in the plugin, and therefore not taking benefit of the localization.

I am working on the Version 4.0 of this plugin, that would require a new translation. I will have deep look into this notice.

Will be available in english, french, spanish.

Nothing but an assumption – this kind of erratic thing may come from the SQL server in case it is overloaded. In this case a heavy SQL request (as generated by the plugin in case of many 10,000 images) does not complete before timing out.

OK thanks.

Received your donation – Many thanks.