I just successsfully migrated from a 5.2 installation to a 6.2.
I installed the admin_tree_structure extension, and I guess (since
I’ve not found its usage guidelines) by simply declaring a page Archive
its children should automagically become organized in a tree-like
fashion. Unfortunately I got the following error: Parked at Loopia . Any ideas?
With the new 6.2 (gem) installation, regardless of the presence of
the admin_tree_structure extension, the admin tree, after I edit a
page, whenever I save it and the system brings me back to the main admin
page, the admin tree doesn’t stay expanded but become compressed into
just one line. This is very inconvienient snce I’ve to click and click
to expand it again and reach the page I was editing or a sibling of it.
Is this a known bug of this release?
Many thanks for shedding some light on these issues.
I am getting the same thing. I haven’t really investigated yet, but
it is a small test system, frozen to Edge and with the latest
extension checked out.
Are you running any other extensions? If there’s another extension
that
is overriding the _node.rhtml page, that will mess up my extension.
It looks like shards just added _node.rhtml. Make sure that
admin_tree_structure is loaded after shards (either by using numeric
prefixes or the config.extensions setting in environment.rb)
Dan.
I am getting this same problem. The “2007” folder just keeps
appearing, recursively. I just installed a new version of radiant
with the latest Gem (0.6.3) and no other extensions and a just the
“Styled Blog” in the database. No luck.
The _node.rhtml file from the extension is definitely being loaded, I
made a minor change and it showed up. Not sure exactly what is
happening here, but I would love to use this extension, so let’s try
to get this sorted out.
I froze my radiant installation but I get a sort of “recursive” admin
tree (see the attached pdf file: Parked at Loopia ).
Is there something I’m missing?
Are you running any other extensions? If there’s another extension that
is overriding the _node.rhtml page, that will mess up my extension.
It looks like shards just added _node.rhtml. Make sure that
admin_tree_structure is loaded after shards (either by using numeric
prefixes or the config.extensions setting in environment.rb)
The _node.rhtml file from the extension is definitely being loaded,
I made a minor change and it showed up. Not sure exactly what is
happening here, but I would love to use this extension, so let’s try
to get this sorted out.
I see the problem now - I’d made a change to the javascript that didn’t
get into my source control. I’ll get it checked in later today.
The _node.rhtml file from the extension is definitely being loaded,
I made a minor change and it showed up. Not sure exactly what is
happening here, but I would love to use this extension, so
let’s try
to get this sorted out.
I see the problem now - I’d made a change to the javascript
that didn’t
get into my source control. I’ll get it checked in later today.
Sorry for the delay. Latest source includes the js change.