Has anyone gotten the Admin Tree Structure extension to work with
0.6.6? I have it installed, but when a page is set to archive, I get
nothing. No errors, just nothing.
thanks!
Keith B.
[email protected]
Are you loading admin_tree after the archive extension (and also after
shards)?
Are you sure that there’s no errors either in your js console in your
browser or in your server logs?
Where can I find this extension? Cause I can’t find it anywhere! I’d
like to try it out.
Well, I wasn’t loading the archive extension first, but once I do
that, I get a no method error:
Showing admin/page/_node.html.erb where line #10 raised:
undefined method `url’ for
#ArchivePageTreeStructure::ArchiveYearTreePage:0x25f0e04
Extracted source (around line #10):
7: <%= icon %>
8: <%= node_title %>
9: <% else -%>
10: <%= expander %><%= icon %> <%= node_title %>
11: <%= page_type %>
12: <%= spinner %>
13: <% end -%>
I will dig into it, but so far, I haven’t gotten it to work. This is
using the 0.6.6 Gem, not edge.
Keith
Arik J. wrote:
Where can I find this extension? Cause I can’t find it anywhere! I’d
like to try it out.
The server were it was originally hosted seems to be down. I’ve dug up a
version i had lying around and put it on github here;
http://github.com/jomz/radiant-admin-tree-structure/tree/master
Keith B. wrote:
Well, I wasn’t loading the archive extension first, but once I do
that, I get a no method error:Showing admin/page/_node.html.erb where line #10 raised:
undefined method `url’ for
#ArchivePageTreeStructure::ArchiveYearTreePage:0x25f0e04
Extracted source (around line #10):7: <%= icon %>
8: <%= node_title %>
9: <% else -%>
10: <%= expander %><%= icon %> <%= node_title %>
11: <%= page_type %>
12: <%= spinner %>
13: <% end -%>
I will dig into it, but so far, I haven’t gotten it to work. This is
using the 0.6.6 Gem, not edge.Keith
I don’t use the extension anymore as it was published, but re-used a big
part of it in another extension. I’ve also had to add an ‘url’ and
‘status’ method to get it to work under 0.6.6. The updated version on
github should work, confirmation appreciated.
Regards,
Benny
I don’t use the extension anymore as it was published, but re-used a
big
part of it in another extension. I’ve also had to add an ‘url’ and
‘status’ method to get it to work under 0.6.6. The updated version on
github should work, confirmation appreciated.
For some reason the version you have on Github does not load for me.
But when I add the url and status methods to the version I have, then
it works fine. Mysterious. Did you change anything else?
Keith
Keith B. wrote:
I don’t use the extension anymore as it was published, but re-used a
big
part of it in another extension. I’ve also had to add an ‘url’ and
‘status’ method to get it to work under 0.6.6. The updated version on
github should work, confirmation appreciated.For some reason the version you have on Github does not load for me.
But when I add the url and status methods to the version I have, then
it works fine. Mysterious. Did you change anything else?Keith
Could be…, as said i got the extension out of an old project. I tried
and also failed to get it working, for some reason the _node view is not
picked up. Changing the extension to .html.erb did not change this.
If you will, put up your (fixed) version of the extension somewhere,
i’ll remove it from my github account.
Benny
I will go ahead and put it on Github when I get a chance. It seems to
be working, though if you have previously opened the archive pages
without the extention, it is very important to clear the cookies
first. This made me loose an hour or two…
Keith
Keith,
Seems to work great for me. You might add to the README that until
0.6.7, the “shards” extension is necessary.
Sean
Can’t seem to figure how to get it to work. Can anyone shed some light
on this?
Sean C. wrote:
Keith,
Seems to work great for me. You might add to the README that until
0.6.7, the “shards” extension is necessary.Sean
This is now on Github at
It would be great if someone could chekc it out and see if it works
for them. I have it working under the 0.6.6 Gem.
Keith
Nevermind, got it. Thanks.
Okay, I got it to work and it works beautifully. But it doesn’t stay.
When I got to edit a page (with or without saving the page) and then
return to page admin tree, the extension breaks and puts me back to the
normal blob of posts without year and date drill downs.
I think, but I haven’t really explored this, that an expired cookie is
messing things up. When I clear out my cookies and log in again it
works. Give it a try and let me know.
I delete the cookies, log back in and it works. But after it working I
try and edit a page and then return back to page admin tree list only to
find that the extension bottomed out again.
Keith B. wrote:
I think, but I haven’t really explored this, that an expired cookie is
messing things up. When I clear out my cookies and log in again it
works. Give it a try and let me know.
Anton,
git is a bit hard to install. It’s possible something is broken in your
installation. Our reasoning for moving to git is to promote
participation. Branching, merging and patching are MUCH easier than
Subversion. As soon as we come up with a solution for our Trac
installation, Radiant will be moving fully over to git.
Sean
Keith B. said the following on 14/05/08 10:02 AM:
This is now on Github at GitHub - kbingman/admin_tree_structure: Extension for Radiant CMS that sorts children of ArchivePages by year and by month on the backend
It would be great if someone could chekc it out and see if it works
for them. I have it working under the 0.6.6 Gem.
I’m really unhappy with GIT.
The manual pages are sparse and it keeps throwing “Can’t Chdir” errors
for no apparent reason and won’t give me a debug trace.
What’s the business justification for moving to GIT?
–
“Preconceived notions are the locks on the door to wisdom”.
– Merry Browne
There is, that’s not the issue. If we can avoid doing a complete
conversion, we’d much prefer that.
Sean
There has gotta be something out there that does trac to lighthouse
conversion or something.
Sean C. wrote:
Anton,
git is a bit hard to install. It’s possible something is broken in your
installation. Our reasoning for moving to git is to promote
participation. Branching, merging and patching are MUCH easier than
Subversion. As soon as we come up with a solution for our Trac
installation, Radiant will be moving fully over to git.Sean
Can someone try using this extension with 0.6.7? I am not having any
of the cookie problems I was having before, but I am suspicious that
it still may break.
Thanks!
Keith