I'm running the wordpress migrator, and one thing I noticed is that
the model files shouldn't be run in order. User.rb first, then
Post.rb, etc. I'll document it in the README until I have time to
fork/batch/pull req.
Anna
___
Radiant mailing list
Post:
Thanks for your help. I will look into updating the wiki when I understand
it a bit better myself, but right now I'm pressed for time, and getting the
site up and running is my first priority. I originally hoped to learn ruby
and rails better before this point, but it was not possible.
Fortunately
On 25.01.2010, at 15:58, Paul Fox wrote:
> I don't have write access to the apache config,
> and the admin doesn't know anything about rails,
The admin do not need to know anything about rails. It is all standard
apache ssl config stuff.
> so I really need to be able
> to hand him a working co
by "explicitly loads that text filter" you just mean having:
def activate
KramdownFilter
end
right?
i'm at loss now for why it's not appearing in the drop down when
loaded as a gem. no errors or anything unusual just a missing filter.
On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs wrote:
> Act
both suggestions seem to fix the boot problem but now i don't see the
new filter in the drop down. although i do see the extension listed on
the extensions page.
On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs wrote:
> Actually, I imagine :lib => false would do the trick -- gem requirements
> are lo
Actually, I imagine :lib => false would do the trick -- gem requirements
are loaded before extensions. As long as your extension file explicitly
loads that text filter, you should be fine.
Sean
On 1/25/10 1:51 PM, Jim Gay wrote:
> On Jan 25, 2010, at 1:08 PM, john muhl wrote:
>
>
>> i hope
On Jan 25, 2010, at 1:08 PM, john muhl wrote:
> i hope someone can point out what stupid thing i've done in my first
> attempt to package an extension as a gem.
>
> http://gist.github.com/286072
>
> the extension works fine as a regular extension.
> i'm trying this on the edge (current as of abo
On Mon, Jan 25, 2010 at 11:17 AM, James Maskell
wrote:
> Thanks - solved the problem. I had assumed ray would have made the necessary
> migrations when I installed the extension.
ray should have; and does as far as i can tell.
rake ray:i name=settings
...
rake -q RAILS_ENV=development radiant:ex
i hope someone can point out what stupid thing i've done in my first
attempt to package an extension as a gem.
http://gist.github.com/286072
the extension works fine as a regular extension.
i'm trying this on the edge (current as of about an hour ago).
Thanks - solved the problem. I had assumed ray would have made the necessary
migrations when I installed the extension.
2010/1/25 banane
> Hasselwanter is right, in your Radiant root run
> rake radiant:extensions:settings:migrate RAILS_ENV=[your environment
> dev, test, prod, etc.]
>
> On Mon, J
Hasselwanter is right, in your Radiant root run
rake radiant:extensions:settings:migrate RAILS_ENV=[your environment
dev, test, prod, etc.]
On Mon, Jan 25, 2010 at 9:07 AM, Haselwanter Edmund
wrote:
>
> On 25.01.2010, at 18:00, James Maskell wrote:
>
>>
>> ActionView::TemplateError (undefined met
On 25.01.2010, at 18:00, James Maskell wrote:
>
> ActionView::TemplateError (undefined method `description' for
> #) on line #21 of
> vendor/extensions/settings/app/views/admin/settings/edit.html.haml:
> 18:
Did you run the migration for the settings extension? You miss a column in the
config t
Hi all,
I've got a problem with the setting extension. It seems to have installed
fine. I can click on the settings tab, but whenever I go to edit a setting I
get an error 500. This is the error from the log:
Processing Admin::SettingsController#edit (for 81.99.59.16 at 2010-01-25
16:55:43) [GET]
That extension looks like what I need, but I still have some questions.
Can I merely point apache to the "public" folder as webroot for the 443
vhost and configure ssl for the vhost? Is there any configuration I need to
do in radiant to change the port for the admin console, since the docs
suggest
Hi all,
A client needs kind of a directory website, like an employee directory, with
pages for each employee. I'd like to propose a solution using Radiant. However,
due to the amount of employees and the repetetive structure of those pages, it
would be uncomfortable and hard to handle to create
'https' is always configured in apache (or nginx, etc). To make
radiant work with ssl you can use this extension:
http://github.com/jfqd/radiant-ssl_requirement-extension
On 24.01.2010, at 22:11, Paul Fox wrote:
> I need the admin console to be accessible from anywhere via https on
> port 443
16 matches
Mail list logo
