<div dir="ltr">Yep. That's the point of what I was saying: not hosted at WPORG => use filter to exclude from the update API check.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Dec 22, 2013 at 4:41 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Her Theme is not hosted at WPORG :) This is to avoid <div>updates from <a href="http://wordpress.org/themes/polaris" target="_blank">http://wordpress.org/themes/polaris</a> </div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, Dec 22, 2013 at 3:38 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Theme developers can simply exclude their Theme from the update API check, through a simple filter. Given how deeply the Theme and Plugin directories are integrated into the WordPress user admin, I would strongly recommend that developers of Themes/Plugins not hosted by WPORG implement such filters, as a matter of course. (Note: there is a similar method for hooking a third-party update *into* the update API, so that non-WPORG-hosted Themes/Plugins can make use of the automatic update/upgrade functionality.)</div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Sun, Dec 22, 2013 at 4:27 PM, Morgan Kay <span dir="ltr"><<a href="mailto:morgan@wpalchemists.com" target="_blank">morgan@wpalchemists.com</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This might be slightly off-topic for this list.... but I just ran into a problem on a client's site that I have seen happen more than once. The client has a custom theme, and the theme's name is "Polaris." The client was being diligent about doing updates on their site, and WordPress told them that they needed to update the Polaris theme, so they did. Unfortunately, "Polaris" is also the name of a theme in the WordPress theme repository, which has a later version number than the custom theme named "Polaris" on the client's website. So they thought they were updating their current theme, when actually they were installing a whole new theme which completely broke their site.<br>
<br>
This isn't the first time I have seen this happen. Apparently WordPress only compares the theme name and the version number, and then prompts for an update.<br>
<br>
So I have two questions here:<br>
1) Is there anything that theme authors who write bespoke themes can do to prevent this from happening? Other than only using really obscure names, or giving our themes artificially high version numbers?<br>
2) Can we change how WordPress looks for theme updates so that it checks Author name or some other required parameters to make sure that it is actually the same theme? (I know - you're going to tell me to fix it myself. I would actually be happy to do that, but there seem to be some policy questions involved here, such as whether authors are likely to change their author name or URI, and whether these changes would prevent themes from being updated when they should.)<br>
<br>
Thanks!<br>
Morgan.<br>
<br>
-- <br>
Morgan Kay<br>
WordPress Alchemists<br>
<a href="http://wpalchemists.com" target="_blank">http://wpalchemists.com</a><br>
<br>
Alchemy Computer Solutions<br>
<a href="http://alchemycs.com" target="_blank">http://alchemycs.com</a><br>
<br>
Skype: wp-alchemist<br>
<a href="tel:206-321-1742" value="+12063211742" target="_blank">206-321-1742</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>