phd38

This should be fixed with the last released – deprecated call.

Bonjour,

Je vous ai bien lu. Je suis simplement dans une phase professionnelle qui rend difficile une intervention sur le plugin.

Fixed in 4.0.8

I updated the development version, that now includes the fix. Please check and after you confirm I will generate a new version for the plugin.

It seems to be linked to a <p>… </p> pair that this new WP version puts around my JS code.

That’s a difference I could observe between the tag cloud not working (plain page), the widget and the “player”.

Duplicated issue – I fix it ASAP.

Hi,

1 – the search field is currently not implemented as a sidebar widget.
2 – go to the mediatagger-def.php in the plugin directory and change the line : $t-> search_attachment_like = ‘Search attachment like…’;
(the pb being that since it is hard coded, for every new release you will have to redo this)
3 – this is hardcoded as well in the php file

Hello,

I am using lighbox as well without noticing a problem – if you select an other setup than “plain image size”, do you still have the issue ?

I will issue a fix tonight – thanks to Miriam, this is linked to an obsolete mySQL call.

Ouch – that’s a pain, I suspect we deal with a specific server setup. I would have to equip the code with debug instruction to trace the exec. I will when time permits.

What is the image file size of the concerned image ?

It has then to be compared to the maximum allowed filesize. This is a server setup for your PHP environment. You can check it with phpinfo() ; check the upload_max_filesize parameter.

Does this happen for all your images ?

Means that the getimagesize() PHP function does not return a valid number – then null is used instead. For a reason I can hardly explain.

What is the PHP version ?

This should happen once – when the taxonomy is regenerated and then disappear. It just concerns the maintenance messages.

This can not be parametrized by the plugin – you have to dig into the code.

Tags are independant from the images or any medias which are tagged. Removing the media does not involve touching the tags, it would be too dangerous.

Then concerning the div by zero, it should not happen. I would need more data to evaluate the case.