Good luck to you, it was last updated 4 years ago.
“This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.”
https://wordpress.org/plugins/thesography/#developers
Maybe you can fork it?
@airdrummer thanks, I will check it out. Can’t give a time frame, but appreciate the suggestions!
Just off the top of my head while on my phone, if you’re turning labels off you could also just remove the separator in the HTML settings of the plugin, or am I missing a use case?
I usually use the Regenerate Thumbnails plugin to reprocess images and fetch additional meta data from them, but that wouldn’t reset the settings of this plugin, so good idea.
@swoolrich while a lack of updates might mean a plugin is abandoned it is not always the case and I am monitoring these support requests.
I see that you had a request that is not yet resolved. I apologize for that. FWIW I had a baby a year ago (around the time of your request), so I spend very little time at my computer these days. But it is my intention to update the plugin.
-
This reply was modified 7 months, 3 weeks ago by
kristarella.
@swoolrich: i did fork it, and i’ve been running it under the latest wp (6.0.1?-) with no problems (except for a missing map image) i’ll update the readme
@kristarella: welcome to parenthood!-) now u know why ur parents were sleep-deprived cranky…it gets better when the grandkids come (& then go home;-)
“just remove the separator in the HTML settings” true but not a satisfying solution, and is still an issue with the nolabels keyword i’ve added.
pls check it out in action @ https://cardinalglen.org/lonely-lily/
btw, the html fields are escaped with addslashes, but in https://www.php.net/manual/en/function.addslashes.php
The addslashes() is sometimes incorrectly used to try to prevent SQL Injection. Instead, database-specific escaping functions and/or prepared statements should be used.
perhaps mysql_real_escape_string should be used instead?
@airdrummer
perhaps mysql_real_escape_string should be used instead?
Thanks for the tip! I believe I was following the official WP documentation on security at the time, but it might have been updated since then.
I have finally started revisiting work on the plugin, so hope to incorporate these changes and update soon.
