hello
i’m looking at /admin/pages
does anybody know what view is currently used for
that page?
/app/view/admin/page/index.rhtml ?
/vendor/radiant/…/index.rhtml ?
/vendor/extension/extension[1…1000]/…/index.rhtml ?
/radiant_gem_folder/…/index.rhtml ?
did somebody made translation for radiant admin part?
why god damn why??
i put all of admin views into /app/views directory and
it does not use them…
is not it highest priority folder?
i don’t understand that 
It depends on which way you have Radiant installed for the given
site/project/instance.
I can tell you with certainty that it’s most likely 2 or 3. If you
installed something like the reorder or copy-move extensions, it’s
probably 4. Hope that helps!
Sean
thank you, yes i’m using frozen version of Radiant but still
IMO such behaviour is very strange and unnatural…
why not define priorities of directories and search for specific
view in that order?
i mean
/app/views/
is definitely much important than
/vendor/extensions/…/views
or
/vendor/radiant/…/views/
it could be easy solution for holding merged views for conflicting
extensions as well
It is designed in this way for several reasons.
We assume you’ll be running in instance/project mode. This means that
the majority of the Radiant code will be loaded from one location. This
is helpful for shared hosting or multiple-site environments where the
sysadmin can install the Radiant gem and have the code shared across all
sites on the server.
Sometimes you want to have a specific version of Radiant. Maybe the
newest gem breaks your site or maybe you need a feature from the latest
codebase. This is the purpose for vendor/radiant. If it is present, it
will be used instead of the gem.
Extensions are designed to change the way Radiant behaves, therefore
they should have precedence over anything Radiant provides, including
views. This does not prevent them from breaking each other, however.
In the case where there’s a conflict (multiple extensions defining the
same view), the lexically first extension is chosen.
app/views is pretty much only present when someone is developing for the
core. You might have a look at RadiantOnRails though, and the work
being done to greater integrate Radiant with other applications. They
are able to use code out of app/.
Down the road, we will have a greater compartmentalization of Radiant’s
views, reducing the number of conflicts between extensions. Some work
on that was done in an experimental branch in January called facets, but
it was too ‘alpha’ to be included in 0.6.
So there’s the overview. Maybe you could describe what specific problem
you’re having?
Sean
the problem is i’m trying to translate administrative part but
i don’t know what files should i change.
this is pretty common problem - if i want something to look
in different way it is natural to add replacement into /app/views
folder and happily see that application is using my changes.
I have actually translated about 95% of Radiant using the Gibberish
plugin. There is a patch on the dev site, but I need to add a few
things, then you can change the language using a yaml file. This of
course does not address any extensions, but these are easily added.
The main problem would be the very popular (and great) copy/move
extension and the reorder extension. I have these both done as well,
but have not submitted patches for them.
Email me and I will give you the latest patch. I have been meaning to
submit a new one, but as I am swamped with work, I haven’t had time.
Once you figure out how radiant works, this is all very easy. If I am
changing something in the core code, then I do not use the gem, but
rather an svn checkout. The avoids one of your problems. Then as Sean
says, be sure to check your extensions, they override everything.
Read Sean’s post carefully and you will figure out where everything is.
Keith B.
[email protected]
Tel: +49-7731-7983830
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs