Hello.
I have Japanese translation file (ja.yaml) . And I want to submit
this file.
What should I do?
--
rish(Ryutatsu Ishigami)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On 2007/07/22, at 0:58, John W. Long wrote:
> I added a new branch to the repository today named 'jargon' and merged
> Kieth
I'm in a bit of a dilemma here, and would appreciate everyone's input.
I've got a project which will basically be a photo gallery site, with
some additional "static" information pages (contact, about, etc.) For
the client's sanity, I want to build the site in Radiant so they have
easy access
Keymone wrote:
> Hello!
>
> how do i freeze radiant application to jargon branch?
>
>
rake radiant:freeze:edge BRANCH=jargon
I'll be making some changes to the branch today, by the way. I got a
patch to Gibberish accepted that obviates the need for the
extension_languages extension.
Sean
__
A designer friend of mine is looking for a Radiant expert to help
with Radiant projects - specifically installing and customizing
Radiant for clients.
This is paying work. If you're interested, contact me (Ryan at Art of
Mission .com) and I'll put you in touch with him.
Thanks!
___
Hello!
how do i freeze radiant application to jargon branch?
--
Regards, Keymone
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radia
Andreas Schwarz wrote:
> Just a guess: Admin::UserController#preferences.
>
>> only_allow_access_to :index, :new, :edit, :remove, :when => :admin,
>
> "preferences" is not in that list.
>
>> @user = User.find(session['user'].id)
>
> Unless whiny_nils is enabled (which I strongly recommend), any
Luca,
Thank you for prodding me about this. A bunch of people had problems
with this about a month ago. The issue is that attachment_fu uses a
default max size of 1MB, but in this case there should be no problem
with allowing larger attachments. The change should be complete in
about an hou
Hi, I'm using the attachments extension in Radiant CMS to upload files
and image I need to reference at inside my pages and I find it very
useful!
But there's a problem when uploading files larger than 1 MB: it doesn't
work and no error message is raised. I suppose it's because the file
size is to
Il giorno 23/lug/07, alle ore 15:44, Sean Cribbs ha scritto:
> Before we jump the gun, we have no _real_ idea how the attack was
> accomplished. The core team is pouring over the log files to find
> more
> information. I agree that the class-variable thing is kind of bad
> practice, but it's
On 23 Jul 2007, at 4:01 PM, Erik Mallinson wrote:
>>> Can anyone shed light on how the attacker would be able to do this?
>
> If it was anything like the attack on Dreamhost accounts
> (http://www.dreamhoststatus.com/2007/06/06/security-breach/) it was
> via FTP and it looks like anything resembl
> > Can anyone shed light on how the attacker would be able to do this?
If it was anything like the attack on Dreamhost accounts
(http://www.dreamhoststatus.com/2007/06/06/security-breach/) it was
via FTP and it looks like anything resembling an index page for a cms
was hit. My Radiant sites were
Honestly we should be storing the id and not the whole object in the
session. Good catch!
Sean
Andreas Schwarz wrote:
> John W. Long wrote:
>
>> Can anyone shed light on how the attacker would be able to do this?
>>
>
> Just a guess: Admin::UserController#preferences.
>
>
>> only_all
John W. Long wrote:
> Can anyone shed light on how the attacker would be able to do this?
Just a guess: Admin::UserController#preferences.
> only_allow_access_to :index, :new, :edit, :remove, :when => :admin,
"preferences" is not in that list.
> @user = User.find(session['user'].id)
Unless whi
Before we jump the gun, we have no _real_ idea how the attack was
accomplished. The core team is pouring over the log files to find more
information. I agree that the class-variable thing is kind of bad
practice, but it's set at the beginning of every request (and Rails only
handles one at a
Andrea Franz wrote:
> I've not been victim of an attack...but I think it could be better
> setting the current_user in a thread variable instead of using a
> class variable.
>
> I usually use something like this:
>
> def set_current_user
>Thread.current['current_user'] = current_user
> end
T
I've not been victim of an attack...but I think it could be better
setting the current_user in a thread variable instead of using a
class variable.
I usually use something like this:
def set_current_user
Thread.current['current_user'] = current_user
end
Il giorno 23/lug/07, alle ore
Yesterday, I noticed something in the Radiant code. You are using a
class variable in an observer to store the current_user. Using class
variables in Rails is always bad, because a class is used by more
then one user once loaded in production mode. I experienced a lot of
problems with this
17 matches
Mail list logo
