On Wed, Oct 20, 2010 at 5:48 PM, swartz wrote:
> Anyone know what is the easiest way to hide certain Page Types when in
> page edit form?
>
> I'm primary interested in hiding the ones my client has no use for
> (all Archive capability) and also to hide one other type that I
> created and is merely
On Sat, Oct 16, 2010 at 9:51 AM, Bobby Johnson wrote:
> Not yet, I am still fighting with it. Mostly my newbishness around how to
> debug these problems in ruby, so at least it's a learning experience.
> Jim's response was pretty helpful in clarifying exactly what the problem was
> and helping me
I've written an extension that needs to do some processing on every
call to a page in the cms. Basically, it checks for a cookie and
redirects the user if a certain value is present. I'm running into a
problem where that piece of code is not being called after the first
call to the app. I believe i
All,
1) I read in this post from back in '08
(http://www.ruby-forum.com/topic/142224) that the SiteController had
sessions disabled by default.
Sessions are enabled in my SiteController (which is good, since I am
doing lots of user-centric stuff). When did that change in the base
Radiant
My new tag - perhaps it is of some use:
desc %{
Returns the requested element of the flash for use in layout/page
display.
*Usage:*
}
tag "flash" do |tag|
if key = tag.attr['key']
flash =
tag.locals.page.response.template.controller.session['flash']
Hi Jim,
Thank you for your suggestions.
Forgot to mention using 0.9.1gem.
What are the changes that are going to happen in the next release?
On Oct 21, 10:23 am, Jim Gay wrote:
> On Wed, Oct 20, 2010 at 5:48 PM, swartz wrote:
> > Anyone know what is the easiest way to hide certain Page Types
As far as I understand if there is a cached page already available the
radian sitecontroller doesn't even get executed. The server spits out
the generated page.
If you wish to have code executed everytime for every page access, you
pretty much have to disable caching.
If it's only afew specific pa
flash[] with :notice, :error, :success keys are already in use by the
radiant admin.
So if you have a user logged into admin and into you custom auth, you
will get msg's meant for admin interface appear on user side and vice
versa.
This, of course, may be something you that you do want or you dont.
For now, I am counting on admin. types (which are us) to be mindful
enough to not be logged into user side.
If I have to, I can add admin. logout logic as a before_filter on the
SiteController, and user logout logic as a before filter on the admin
side of things.
W
On 10/21/10 6:31 PM, swa
So do you think it's possible to add the logic to a middleware object and
add the middleware object to the stack?
Put something like the following in the extension?
extension_config do |config|
config.middleware.use GeoIpRedirect
end
I'm pretty new to middleware, so I'm not certain that
10 matches
Mail list logo
