conflict with "rise" theme

[yahniselsts]

conflict with "rise" theme

[YahnisElsts]

I'm reluctant to break backwards compatibility just to work around a buggy theme.

Look at it this way: you could rename the query parameters and force everyone who uses them to update their code, but who's to say that the new URL won't conflict with some other buggy theme or plugin? Maybe another theme uses the same path suffix ("_versions") or file name ("update.json"), or looks for a "members." prefix in the domain name. Maybe some poorly written plugin breaks all HTTP requests that use a particular timeout setting or where the URL is more than 100 characters long.

Would it really be a good idea to stuff a plugin full of workarounds for every buggy WordPress product out there?

[seyfro]

did not think about that changing that parameter would break backward compatibility - if that is the case, I wouldnt change this either. Just thought, I let you know about this issue. Will contact the theme developer instead and tell him about this issue...

[YahnisElsts]

Yeah, if plugin-update-checker was a brand-new library I would just change the parameter and be done with it. However, "checking_for_updates" and "installed_version" were introduced more than two years ago. There are probably developers who rely on them. In this case, contacting the theme author seems like the best approach.