Hi Wes,
Yeap pretty much.
On Oct 5, 6:36 pm, Wes Gamble we...@att.net wrote:
So you need to maintain two distinct sessions from one browser? Is
that right?
W
On 10/5/10 6:22 PM, swartz wrote:
I have a 0.9.1-based radiant install that uses a custom end-user auth-
system. It uses
Hmmm...
Some thoughts:
1) You could maintain multiple independent sessions logically by simply
establishing some naming convention of session key values in the one
session. All admin session keys are session[:admin_xxx] and all
regular session keys are session[:regular_xxx]. You could
If anyone has *any* insight or suggestions, that would be SUPER
helpful.
Thanks,
STan
On Oct 5, 8:08 am, Stan Rawrysz smoo...@gmail.com wrote:
Beat my head against the wall with this problem all day yesterday. Not
sure what's going on.
I'm running Radiant 0.8.2 (along with webrat 0.4.4,
Have you look at at this file?
/home/stanr/projects/radiantapp/cms_core/vendor/extensions/ip_redirect/features/step_definitions/customer_comes_to_us_helios_steps.rb:18
On Wed, Oct 6, 2010 at 11:51 AM, Stan Rawrysz smoo...@gmail.com wrote:
If anyone has *any* insight or suggestions, that
I had a similar issue when I was moving extensions from dev-server to
production.
One of the issues was that I had a typo in the migration scripts and
one of the table fields was misnamed when migration was executed. So
when I attempted to retrieve data from it, it had that same error
regarding
Hi Wes,
In fact I already do 1) as you propose. Mainly to remember proper
redirects after login and similarly for flash messages etc.
Here's my issue:
In my environment.rb for Radiant I have,
config.action_controller.session = {
:key = '_appname_cms_session',
:secret = 'mysecret'
On 5 Oct 2010, at 19:04, Jim Gay wrote:
or
b) using something else and challenges faced by using that something else
alongside Radiant.
Many thanks,
Wes
We will eventually pull out the editor auth stuff and make it
configurable too, but check out the extension registry to see how
