Where possible, I have been tagging extensions in 'radiant' github user
with 0.6.9 before making updates for 0.7. I suggest developers tag
their extension repositories similarly to reduce confusion.
Sean
Tim Gossett wrote:
On Sun, Dec 28, 2008 at 9:31 PM, Nate Turnage <pixeln...@gmail.com> wrote:
With the most current version of the copy_move extension and v. 0.6.9 I get
this "error" for every page in the list of pages:
*`copy_move_extra_th' default partial not found!
I have used this extension in the past without any problems at all, but in
building (rebuilding) a project this weekend I am having this problem. I
can
only imagine it is because of this comment in three places from the latest
commit: "used the new
admin_pages_url<
http://github.com/pilu/radiant-copy-move/commit/07015cd85bca4af44a182775e7979e965f1acc94
"
. Again, I imagine this is to allow for the extension to work with v. 0.7
but it seems to break compatibility with 0.6.9. Am I wrong?
Actually, it was the commit before that:
http://github.com/pilu/radiant-copy-move/commit/b7d93af32fc8fbaa97611d0697ab33f606d2eef1
pilu updated his extension for Radiant 0.7.0, breaking it for 0.6.9. Just
rename RADIANT_ROOT/vendor/extensions/copy_move/app/views/pages to "page".
--
Tim
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant