Created attachment 7404 thunar-media-tags.patch Please find attached a quick port to Thunarx-3. No further testing was done with this because I needed the plugins to be buildable again.
Created attachment 7406 thunar-media-tags.patch including configure adjustments
Created attachment 7408 thunar-media-tags-plugin.patch against GIT
Created attachment 7409 gtk3 and thunarx-3 port Are you sure that just bump thunax version in configure.ac.in is enough to make this plugin work? Anyway, here goes a WIP patch.
No! But I was able to get the stuff compiled again... I commented on the thunar-volume report on my motivations for this: https://bugzilla.xfce.org/show_bug.cgi?id=13967#c4 But thanks for the patch. Would it be possible for you to commit the changes to git.xfce.org master ? Sooner or later the plugins need to be ported anyways, so better have them in git master...
It compiles but very likely fails at runtime, actually it's not even loaded by thunar-git since it looks for extensions in <prefix>/lib/thunarx-3. Regarding the WIP patches, I'll merge them this weekend or next week, they are off the tree because I wanted some feedback before merging. Also notice that these patches are incompatible with thunar-git, since the API changes are also in a personal repository. Please wait a few days and those problems will be gone :)
I had some free time today, so I merged everything (thunarx-3 and media-tags-plugins changes) to master, please test and report any bug found.
Getting this error after compiling from GIT. tag-renamer.c: At top level: tag-renamer.c:896:34: error: unknown type name 'ThunarxMenuItem'; did you mean 'ThunarxRenamer'? tag_renamer_edit_tags_activated (ThunarxMenuItem *item, ^~~~~~~~~~~~~~~ ThunarxRenamer make[2]: *** [Makefile:545: thunar_media_tags_plugin_la-tag-renamer.lo] Error 1 make[2]: *** Waiting for unfinished jobs....
This issue also spwans in other areas of tag-renamer.c
Probably installs into /lib/thunarx-2 like thunar-archive-manager
Please ignore my feedback before. There was an issue with one of our scripts causing the issue by overwriting the new master.tar.bz2 download with an old version. We fixed that issue on our side. Your changes were all correct and working. Also correct installation.