Reply to thread

Message

<blockquote data-quote="ltfearme" data-source="post: 1279622" data-attributes="member: 52219">Don't worry guys, I won't let the plugin die esp. with all the time and effort I have put into it, and the fact I still use it religiously <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />The timing is not good though, the end of life for the older API's seems to be end of March 2021 from what I have read, and between now and then I have many things on my plate that are higher priority (as well as try to enjoy the Australian summer after this hell of a year).What I can probably do initially, is port to themoviedb.org API and then later look at implementing support for multiple data providers. If it becomes too troublesome to rip the old v1 API out from the importer and swap with tmdb, I just have to start working on the multiple data provider solution earlier (with at least one provider to start with).</blockquote>

[QUOTE="ltfearme, post: 1279622, member: 52219"] Don't worry guys, I won't let the plugin die esp. with all the time and effort I have put into it, and the fact I still use it religiously :) The timing is not good though, the end of life for the older API's seems to be end of March 2021 from what I have read, and between now and then I have many things on my plate that are higher priority (as well as try to enjoy the Australian summer after this hell of a year). What I can probably do initially, is port to themoviedb.org API and then later look at implementing support for multiple data providers. If it becomes too troublesome to rip the old v1 API out from the importer and swap with tmdb, I just have to start working on the multiple data provider solution earlier (with at least one provider to start with). [/QUOTE]

Verification