• ResolvedPlugin Author phd38

    (@phd38)


    The migration to the newest 4.0.1 should be fine now – even in case of error message, be aware that your tagging data is unaffected. Just the table name was changed. I check this when activating the plugin.

    Please report if you still encounter errors.

    https://wordpress.org/plugins/wp-mediatagger/

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author phd38

    (@phd38)

    Consider 4.0.4.

    When I do a search in explorer mode, results never load it just processes/page acts like loading but never shows results. Perhaps a problem with the number of images I had but it didn’t have a problem before. Otherwise, plugin working smoothly.

    Plugin Author phd38

    (@phd38)

    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.

    I’ve been having Mysql has gone away error messages since reactivating the plugin. I was told by my host it’s excessive database queries timing out. It happens when the plugin is activated, not when I’m using it but just activated. I’m beginning to think maybe I have too many images to use this plugin. Is there anything that I can do to make this work so I won’t keep getting Mysql errors?

    I am using Query Monitor to find where the queries are coming from. One 1 page I counted 244 queries from Media Tagger. There are only 20 images on this particular post and none of the images are tagged yet.

    This is a selection of what Query Monitor shows:

    225	SHOW TABLES LIKE "wp_mediatagger"	wp_mediatagger->check_table_exists()+	Plugin: wp-mediatagger 	1 	0.0003
    226	SELECT *
    FROM wp_mediatagger
    WHERE term_taxonomy_id = 697	wp_mediatagger->run_mysql_query()+	Plugin: wp-mediatagger 	23 	0.0001
    227	SHOW TABLES LIKE "wp_mediatagger"	wp_mediatagger->check_table_exists()+	Plugin: wp-mediatagger 	1 	0.0003
    228	SELECT *
    FROM wp_mediatagger
    WHERE term_taxonomy_id = 583	wp_mediatagger->run_mysql_query()+	Plugin: wp-mediatagger 	328 	0.0001

    Plugin Author phd38

    (@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.

    121 tags, so I guess that’s why there are so many queries? Why would it do that on post pages and not just query when using the player?

    Plugin Author phd38

    (@phd38)

    I will investigate this – the player is calling the same routine as the shortcode inserted on your page.

    I will use the same Query Monitor – should be able to easily duplicate.

    Plugin Author phd38

    (@phd38)

    I just checked – at least I could observe the same number of query from the “player” page and from a site page.

    Plugin Author phd38

    (@phd38)

    Have ideas to decrease – will implement in the next days.

    You’re fantastic, appreciate your work!

    Plugin Author phd38

    (@phd38)

    I created the 4.0.5 – available as development version so far.

    You should see a very significant decrease of the SQL transactions. On the “player” page with no tag selected, I moved from 100 to less than 20. So the plugin is more “quiet” when no operations are required.

    http://downloads.wordpress.org/plugin/wp-mediatagger.zip

    Then running image search involves heavy SQL computing, although down to the minimum with this version. That’s intrinsic to the plugin function, I cannot change this – unless working on a dump of the media database, which I already tried : in this case the SQL server is much less loaded, but the load is transferred on the PHP. At the end my take is that the SQL server is typically profiled for sustaining this kind of computation.

    At least the load is now directly driven by the number of media and tags.

    Let me know if you notice any involvment, or any other side effect. I tested in all possible situations, should be fine.

    I will then promote it to 4.0.5.

    Way less queries on the front end, yea! Will test it further and see if that fixed everything. Appreciate it!

    You’ve been the most responsive plugin developer I’ve ever experienced since using WP, thank you!

    Edit: When tagging images in the explorer, this will pop up on occasion at the top: “Cached taxonomy outdated – RECALCULATING”
    Don’t know what it means, but thought I’d let you know.

    Plugin Author phd38

    (@phd38)

    My pleasure. I did something initially for me that I then developped a bit further for making it useful for others, very simple πŸ™‚

    Something I found. Since I was not able to search media through the explorer (result page is blank) I thought maybe I could delete that particular tag and start all over with those particular tagged photos. I thought the images would revert back to “No tag associated to this media” instead the image tag shows blank and is not included in the list of untagged media.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘In case still issue with the mediatagger table when upgrading please post here’ is closed to new replies.