Re: [Radiant] Help With Questionnaire Extension

2010-01-09 Thread Michael Kessler
Hi Alexis

We have this extension running only on a Radiant 0.7 installation and there are 
actually no concrete plans to migration the extension. The Rails version that 
comes with Radiant 0.8.1 introduces nested forms/attributes and that would 
simplify the extension code a lot, so a migration to Radiant 0.8.1 is more 
about to remove some code than adding new one. It may be also the reason that 
the extension is actually broken with Radiant 0.8.1

Michael

On 07.01.2010, at 20:25, Alexis Masters wrote:

 Hello again,
 I have a new radiant site that needs the Questionnaire extension. The  
 site is on Radiant 0.8.1. I keep getting this error when I try to  
 create a new questionnaire:
 
 /!\ FAILSAFE /!\  Thu Jan 07 10:40:21 -0800 2010
   Status: 500 Internal Server Error
   expected Hash (got String) for param `questionnaire'
 
 Is anyone else using this extension on 0.8.1, and if so, have you seen  
 and hopefully solved this issue?
 
 ~ Alexis
 =
 Alexis Masters, author
 http://www.alexismasters.com
 
 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] sns-extension version compability

2009-07-11 Thread Michael Kessler

Mamed,

Use the git repo from the Radiant dev team at 
http://github.com/radiant/radiant-sns-extension/tree/master

If you've already installed another version, change the origin and  
pull it again:


cd vendor/extension/sns
git remote rm origin
git remote add origin git://github.com/radiant/radiant-sns-extension.git
git pull --tags origin master

Now you can have a look at the tags with:

git tag

Pre-Release
v0.2
v0.2.1
v0.3
v0.3.1
v0.4
v0.4.1
v0.5
v0.6
v0.6.1
v0.6.2
v0.7
v0.7.1

and reset to the matching tag, since head is actually for Radiant 0.8.0

git reset --hard v0.7.1

Michael


On 11 Jul 2009, at 12:05 AM, Mamed Mamedov wrote:


Hi! Who knows some information about sns extension and his author.
http://ext.radiantcms.org/extensions/53-sns

Which is current version of this extension? With is current compatible
radiant version for this extension?
On my radiant0.7.1 with rails2.1.2 - it fails on migrate with:
** Execute radiant:extensions:sns:migrate
== 2 AddDependenciesToTextAssets: migrating
===
rake aborted!
PGError: ERROR:  relation text_assets does not exist
: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
d.adsrc, a.attnotnull
 FROM pg_attribute a LEFT JOIN pg_attrdef d
   ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = 'text_assets'::regclass
  AND a.attnum  0 AND NOT a.attisdropped
ORDER BY a.attnum

And with 500 error when trying to access it:
Processing Admin::ExtensionsController#index (for XX.XX.XX.XX at  
2009-07-11

03:00:18) [GET]
 Session ID:  
BAh7CDoMY3NyZl9pZCIlN2Q4ZjA2MzJmYzVlZDNjMmE1OTYxNjEzZWVmNGQ0

OWIiDHVzZXJfaWRpBiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxh
c2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA 
==--277a32b6b2db5ee1edd55c5ca36ddde9749c6da3

 Parameters: {action=index, controller=admin/extensions}
Cookie set: session_token=c600a6cb231fb66f80fddf3a49be60c6baa22443;  
path=/;

expires=Fri, 24 Jul 2009 22:00:18 GMT
Rendering template within layouts/application
Rendering admin/extensions/index
Completed in 0.64189 (1 reqs/sec) | Rendering: 0.44538 (69%) | DB:  
0.02168

(3%) | 200 OK [http://rcba.com/admin/extensions]
DEPRECATION WARNING: 'Admin::AbstractModelController' has been  
deprecated.

Please update 'Admin::TextAssetController' to use
Admin::ResourceController.  See http://www.rubyonrails.org/ 
deprecation for

details. (called from inherited at
/usr/local/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/controllers/ 
admin/abstract_model_controller.rb:5)

/!\ FAILSAFE /!\  Sat Jul 11 03:00:32 +0500 2009
 Status: 500 Internal Server Error

Can somebody explain me the problem? And, if possible, the model of  
problem.


Regards,
Mamed Mamedov
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Using old versions of radiant and rails

2009-07-11 Thread Michael Kessler
I usually stick a Radiant project to the actual Radiant Version by  
adding


RADIANT_GEM_VERSION='0.8.0'

to the environment.rb

This enables me to put all my project with different Radiant versions  
on a single server. When I update the server and a new version of  
Radiant will be installed, all the 'old' projects use a previous  
Radiant version and are still running fine, while I can develop and  
deploy new projects with the latest Radiant version.


Michael


On 10 Jul 2009, at 9:23 PM, Mamed Mamedov wrote:


Hi All!

What do you think about: if I can install previous versions of radiant
v0.7.1 and rails v2.1.2.

gem install radiant --version '0.7.1'
gem install radiant --version '2.1.2'

?
I think it still will work with old versions of extensions. And  
then, when
most of extensions is updated, radiant v0.8 will more popularized  
between

developers I'll just upgrade my installation :) ha?

Regards,
Mamed Mamedov
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] sns-extension version compability

2009-07-11 Thread Michael Kessler
It seems that the tag is somehow not pointing to the last compatible  
commit for 0.7.1.


I have some Radiant 0.7.1 installation and reseted the sns extension  
to this http://github.com/radiant/radiant-sns-extension/commit/1f7ab41c872302cf5dcf0bc6effde4aad2b38158



On Jul 11, 2009, at 2:13 PM, Mamed Mamedov wrote:


Michael,


Thank you for your help! It works, I have loaded tags and reverted  
version
to which is needed. I tried to use 0.7.1., 0.7, 0.6.1, 0.6.2, 0.6,  
0.5 - but

is does not working with my radiant :(

tornado# rails --version
Rails 2.1.2
tornado# radiant --version
Radiant 0.7.1
*Is ot okay?*

Also, I'have done the following things:

rake development db:bootstrap
cd vendor/extensions/sns
git tag
git reset --hard v0.7.1
cd ../../..
rake development db:extensions:migrate
== 4 RenameTextAssetFilenameAndDependencyListColumns: migrating
===
-- rename_column(:text_assets, :filename, :name)
  - 0.0063s
-- rename_column(:text_asset_dependencies, :list, :names)
  - 0.0410s
== 4 RenameTextAssetFilenameAndDependencyListColumns: migrated  
(0.0509s)

==


Then restarted mongrel. But:
Processing SiteController#show_page (for XX.XX.XX.XX at 2009-07-11  
17:00:51)

[GET]
 Session ID:  
BAh7CToMY3NyZl9pZCIlYmRiMGJkYWU4MmU2YTMzMjRmNzQzY2MzZTM0ZTA4

MDciDHVzZXJfaWRpBjoOcmV0dXJuX3RvMCIKZmxhc2hJQzonQWN0aW9uQ29u
dHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA==-- 
e07d96601216e6070fb6ffa24fa5ce28f7d40a68

 Parameters: {url=/, action=show_page, controller=site}


NoMethodError (undefined method `no_login_required?' for
#SiteController:0x29f43868):
   /vendor/extensions/sns/lib/sns/site_controller_ext.rb:24:in
`ensure_no_login_required'



Regards,
Mamed Mamedov

Gilda Radner http://www.brainyquote.com/quotes/authors/g/gilda_radner.html 


- Adopted kids are such a pain - you have to teach them how to look
like
you.

On Sat, Jul 11, 2009 at 1:07 PM, Michael Kessler  
mi...@netzpiraten.chwrote:



Mamed,

Use the git repo from the Radiant dev team at
http://github.com/radiant/radiant-sns-extension/tree/master

If you've already installed another version, change the origin and  
pull it

again:

cd vendor/extension/sns
git remote rm origin
git remote add origin git://github.com/radiant/radiant-sns- 
extension.git

git pull --tags origin master

Now you can have a look at the tags with:

git tag

Pre-Release
v0.2
v0.2.1
v0.3
v0.3.1
v0.4
v0.4.1
v0.5
v0.6
v0.6.1
v0.6.2
v0.7
v0.7.1

and reset to the matching tag, since head is actually for Radiant  
0.8.0


git reset --hard v0.7.1

Michael



On 11 Jul 2009, at 12:05 AM, Mamed Mamedov wrote:

Hi! Who knows some information about sns extension and his author.

http://ext.radiantcms.org/extensions/53-sns

Which is current version of this extension? With is current  
compatible

radiant version for this extension?
On my radiant0.7.1 with rails2.1.2 - it fails on migrate with:
** Execute radiant:extensions:sns:migrate
== 2 AddDependenciesToTextAssets: migrating
===
rake aborted!
PGError: ERROR:  relation text_assets does not exist
: SELECT a.attname, format_type(a.atttypid,  
a.atttypmod),

d.adsrc, a.attnotnull
   FROM pg_attribute a LEFT JOIN pg_attrdef d
 ON a.attrelid = d.adrelid AND a.attnum = d.adnum
  WHERE a.attrelid = 'text_assets'::regclass
AND a.attnum  0 AND NOT a.attisdropped
  ORDER BY a.attnum

And with 500 error when trying to access it:
Processing Admin::ExtensionsController#index (for XX.XX.XX.XX at
2009-07-11
03:00:18) [GET]
Session ID:  
BAh7CDoMY3NyZl9pZCIlN2Q4ZjA2MzJmYzVlZDNjMmE1OTYxNjEzZWVmNGQ0

OWIiDHVzZXJfaWRpBiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxh

c2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA 
==--277a32b6b2db5ee1edd55c5ca36ddde9749c6da3

Parameters: {action=index, controller=admin/extensions}
Cookie set: session_token=c600a6cb231fb66f80fddf3a49be60c6baa22443;
path=/;
expires=Fri, 24 Jul 2009 22:00:18 GMT
Rendering template within layouts/application
Rendering admin/extensions/index
Completed in 0.64189 (1 reqs/sec) | Rendering: 0.44538 (69%) | DB:  
0.02168

(3%) | 200 OK [http://rcba.com/admin/extensions]
DEPRECATION WARNING: 'Admin::AbstractModelController' has been  
deprecated.

Please update 'Admin::TextAssetController' to use
Admin::ResourceController.  See http://www.rubyonrails.org/deprecation
for
details. (called from inherited at

/usr/local/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/controllers/ 
admin/abstract_model_controller.rb:5)

/!\ FAILSAFE /!\  Sat Jul 11 03:00:32 +0500 2009
Status: 500 Internal Server Error

Can somebody explain me the problem? And, if possible, the model of
problem.

Regards,
Mamed Mamedov
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list

Re: [Radiant] Problem with sns extension

2009-07-07 Thread Michael Kessler
You've installed a version that isn't compatible with latest Radiant  
0.8 release. Christi from aissac has announced an update to the  
extension that runs on the latest Radiant version. Give it a try: http://github.com/Aissac/radiant-sns-extension


Michael

On 7 Jul 2009, at 11:26 PM, Wentao Wang wrote:

I tried to install the sns extension. It gave me the following  
error. Any

idea?

C:\Ruby\InstantRails-2.0-win\rails_apps\edwardrake
radiant:extensions:sns:migra
te
(in C:/Ruby/InstantRails-2.0-win/rails_apps/edward)
Could not load extension from file: sns_extension.
#MissingSourceFile: no such file to load -- application.rb
rake aborted!
no such file to load -- application.rb

--
Thank you for your time and patience!

Best,

Wentao Wang
MSI Candidate '10
School of Information,
University of Michigan-Ann Arbor
Tel: 1-734-277-1992
E-mail: wentw...@umich.edu
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Anyone have SNS extension working correctly in 0.8.0

2009-06-29 Thread Michael Kessler

Daniel,

I haven't had the time to migrate the sns extension, because we're  
moving at the moment and it takes a lot of time and I have no Internet  
connection at the moment :(


There is a migrated fork here: http://github.com/dko/radiant-sns-extension/tree/mastera 
 but I haven't tried it.


Michael


On Jun 24, 2009, at 10:51 PM, Daniel O'Connell wrote:


Does anyone have the sns extension working in 0.8.0?


-Daniel

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] [ANN] chronicle extension: versioning, diffs, and drafts for pages

2009-05-20 Thread Michael Kessler

Jason,

The extension looks very, very nice! It's also a very good idea to  
present the extension with a video - this makes it very easy to gain  
an idea about the functionality. Many thanks for the hard work...


Michael

On May 19, 2009, at 10:01 PM, Jason Garber wrote:


Introducing the chronicle extension: 
http://www.youtube.com/watch?v=QDxX73eOlXsfmt=22

It's the realization of something we talked about on this list back  
in September (http://lists.radiantcms.org/pipermail/radiant/2008-September/thread.html#10312 
).  It just versions/drafts pages for now, but snippets and layouts  
will come soon.


I'd really appreciate your feedback, bug reports, and code  
contributions!

--Jason

= Chronicle

In an enterprise production environment, it's critical that content  
editors,
designers, and developers be able to edit pages and preview their  
changes
without affecting the live version and that site administrators be  
able to see

who changed what and roll back if necessary.

This extension adds versioning to pages and uses a page's status to  
determine
its visibility. The most recent published or hidden version is  
visible in live
mode and the most recent version, a.k.a. the current version, is  
visible in
dev mode regardless of its status. Thus, you can work on a draft in  
dev mode,
preview exactly how it will look, and then make it live when you are  
ready by

changing its status to published.

== An example

Look at the revision history of the home page of example.com:

...22  23  24  25
---*---*---*---@
  ^   ^
  Published   Draft
 (live mode)  (dev mode)

If you went to example.com/ you would see version 24. If you went to
dev.example.com/ you would see version 25.

Many people overlook the dev mode feature of Radiant. If you don't  
know about
it, see http://wiki.radiantcms.org/How_To_Setup_Dev_Mode. You can  
also set a
live.host configuration option if you don't access Radiant admin at  
the live

host.

Some terminology used in the specs:
* The current version is the highest-numbered version, a.k.a. the  
current

 dev version.
* The current live version is the most recent Published or Hidden  
page.

* A page is a draft when its status is set to Draft.
* A page has a draft when its current version is a draft.
* When a page's current version is Published, the page does not  
have a

 draft.

== Features:

* Simple graph showing the change history
* Check a box to view the page in a new window/tab after saving
* TODO Roll back to a previous version by creating a new one based  
on it

* See what changed in a given version
* TODO Integration with the Dashboard extension so you can see what  
has
  changed recently and what pages have unpublished changes  
(drafts ahead

  of published versions)
* TODO Lines in the change graph showing ancestry when a page is  
rolled back

* TODO Versioning for snippets and layouts as well
* TODO Versioning including page attachments
* Should be compatible with (and version the extra page attributes  
of) most

 extensions!

Someday/maybe:
* Git interface

== Installation

(from the radiant application root)

 git clone git://github.com/jgarber/radiant-chronicle-extension.git  
vendor/extensions/chronicle

 rake RAILS_ENV=production db:migrate:extensions
 rake RAILS_ENV=production radiant:update

== Reporting bugs

http://github.com/jgarber/radiant-chronicle-extension/issues
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Big Thanks for Ray

2009-05-07 Thread Michael Kessler
John is the one who put his passion into ray (and also the Radiant  
Github wiki). Big thanks to him!


On 7 May 2009, at 5:37 PM, N. Turnage wrote:

I just want to thank everyone involved in putting Ray together. It  
really is amazing. I don't have to install my submodules by hand  
anymore.


You guys rock:

* John Muhl
* Michael Kessler
* Arik Jones
* Benny Degezelle




~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] How do I get published date fields back on admin pages?

2009-04-14 Thread Michael Kessler
Did you mean the page.edit.published_date? Radiant setting that is  
mentioned here http://wiki.github.com/radiant/radiant/additional-configuration-options


Michael

On 14 Apr 2009, at 8:41 PM, N. Turnage wrote:

This was answered my moons ago, but I cannot remember how to get the  
published date fields back on the admin pages. Could somebody list  
the magic spell to make that happen?



~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] WymEditor on Radiant

2009-04-14 Thread Michael Kessler
I personally also prefer textile or plain XHTML. But our customers  
wants some kind of WYSIWY... editing. I don't like WYSIWYG editors,  
but I like the WYSIWYM idea.


The WymEditor extension is far away from complete, but I have a vision  
about this extension. We made some good experiences in our last two  
projects with Blueprint CSS, and there is a Sass port called Compass.  
If we could make a Compass extension that would integrate nicely into  
the SnS extension, the WymEditor could use the Compass grid for a nice  
positioning of the elements and with a nice WymEditor mixin for  
Compass (for example +wym('Address Box'))  we could add classes from  
our Sass file to the WymEditor with a single line, the WymEditor would  
then automatically be adjusted to the Sass.


Michael

On 14 Apr 2009, at 8:51 PM, Steven Southard wrote:


I just installed this extension on 7.1.  It works fine.

Then I'm looking at it in use and I can't understand why this is a  
helpful extension.  Is this extension meant to make something easier  
to write? Like perfectly structured xhtml? Maybe it's just me, I  
think humanly written xhtml is more beautiful and meaningful.


This kind of separation from the words in the code is kind of odd to  
me.  Seeing and reading the code connects a user to the meaning in  
the words.  I prefer the style of the textile or markdown filters.


I think textile is really fun and clever to read and write.  It's  a  
graceful start into code and integrates nicely with radiant tags and  
html.


If I was wanting to add some helpful buttons with attractive icons  
like you see in nice editors,  I'd install textile_editor.  It's  
much more helpful and it's a great assistant because it shows you  
what it writes and then you can edit it if it isn't exactly what you  
meant.


For adding images textile_editor doesn't even need to connect up  
with paperclipped because paperclipped works great on its own. If  
you happen to be using attachments the add image button works really  
well.


If you want to see what you have written looks like; well, what I do  
is just look at it in the browser.  On some sites, it's important to  
work in discreetly so when that is the case I'll work it out locally  
then copy and past the changes.  You could also make a dev page  
somewhere not connected to the rest of the site and work it out there.


I'm glad to have you with us Alexis.  I hope your site goes well.


Steven




On Apr 14, 2009, at 12:31 PM, Michael Kessler wrote:


Alexis,

I have the radiant-wym-editor-filter-extension working on several  
sites. What version of Radiant are you using? Did you notice that  
there is a branch pre_0.7 for Radiant versions prior 0.7, while the  
master branch is for the latest Radiant 0.7.x.?


The extension doesn't need any db migration, but the images and  
javascript files have to be copied to the Radiant projects public  
folder with the rake task  
radiant:extensions:wym_editor_filter:install


After that the Wym editor filter should be available...

Michael


On 14 Apr 2009, at 7:05 PM, Alexis Masters wrote:

Hello! I am enjoying getting to know Radiant, and have been  
searching and reading the archives as well as reading the digests  
when they arrive. Thank you all for all you have done to make this  
CMS so functional.


I came upon a wonderful XML editor that apparently has been used  
successfully on Radiant, but I am having trouble getting it to  
work, and my tech support folks have not been able to install it  
either. We managed to get the Wymeditor filter installed correctly  
but the editor itself never showed up in the admin edit pages.


Does anyone have this running on their Radiant sites, and if so,  
can you kindly share any tips you might have about installing it--- 
or better yet, may I hire you to install it for me?

~ Alexis
=
Alexis Masters, author
http://www.alexismasters.com
510 234-0027



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] WymEditor on Radiant

2009-04-14 Thread Michael Kessler
The difference is, that the install task copies all public files to  
the projects public directory, whereas the update task skips the wym.css


The wym.css file styles the elements in the editor that have classes  
from the class selector box on the right assigned.


On 14 Apr 2009, at 10:07 PM, Bjorn Michelsen wrote:

Excerpts from Steven Southard's message of ti. april 14 21:52:59  
+0200 2009:



Did you miss:

rake radiant:extensions:wym_editor_filter:install


It worked with

rake radiant:extensions:wym_editor_filter:update


..so I didn't even notice there was an install option. :-)

--
Mvh.
Bjørn Michelsen
MOB: +47 934 55 474
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Radiant and regexp

2009-04-14 Thread Michael Kessler

Have a look here: http://www.regular-expressions.info/repeat.html

.+ is called greedy and means it will try to repeat as much as possible
.+? is called lazy and means it  will try to repeat as few as possible

The same works for .*

On 14 Apr 2009, at 11:37 PM, N. Turnage wrote:

Is there any good reference to the way that Radiant uses regular  
expressions for page links? For example, this kind of thing:  
r:if_url matches=^/.+  I don't know how deep /.+ will work, etc.




~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] 500 Internal server errors with Radiant 0.7.1 and SNS

2009-04-09 Thread Michael Kessler

Nate,

The SnS extension ist not officially migrated to Radiant  0.6.9 and  
is broken. I've migrated the code and it runs well, but I haven't had  
enough time to get all the specs passing, so the migration is not  
ready yet and thus it has not been merged into the main repository  
from Chris.


Since I'm really, really short on time at the moment and I'm also not  
very used to rspec, that may take some more weeks until finished. So  
if someone want to help out getting the specs migrated, grab the  
latest development SnS extension here: http://github.com/netzpirat/radiant-sns-extension/tree/master


Michael


On 9 Apr 2009, at 6:30 AM, N. Turnage wrote:


I am running into the same problems with SNS that were mentioned here:
http://www.ruby-forum.com/topic/176102

And just like the original person having problems, the info here was  
not the fix for it:

http://www.nabble.com/SnS-Extension---500-Error-td21486070.html

This is the error:

Status: 500 Internal Server Error Content-Type: text/html
500 Internal Server Error

Anybody have a fix for it? I have 5 stylesheets that I would really  
rather not bring into the main admin area.




Thanks,

~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] New Radiant site for Ignite Social Media

2009-03-18 Thread Michael Kessler
Great work. Thanks for sharing your work on the extensions with the  
community!


On Mar 17, 2009, at 2:41 PM, Jim Gay wrote:

We've just helped Ignite Social Media relaunch their website on  
Radiant

http://www.ignitesocialmedia.com/

They've sponsored a lot of development for extensions for the  
Radiant community in the past and we continued to release more with  
this development effort.


The site is using a big group of extensions which include:
Blog http://ext.radiantcms.org/extensions/30-blog
Change Author http://ext.radiantcms.org/extensions/93-change-author
Dashboard http://ext.radiantcms.org/extensions/40-dashboard
File System http://ext.radiantcms.org/extensions/67-file-system
Help http://ext.radiantcms.org/extensions/5-help
Mailer http://github.com/saturnflyer/radiant-mailer-extension/tree/master
Page Preview http://github.com/saturnflyer/radiant_page_preview_extension/
Paginate http://github.com/saturnflyer/radiant-paginate-extension/
Paperclipped http://ext.radiantcms.org/extensions/20-paperclipped
Settings http://ext.radiantcms.org/extensions/102-settings
Shortcut http://ext.radiantcms.org/extensions/104-shortcut
Site Watcher http://ext.radiantcms.org/extensions/41-site-watcher
Twitter http://ext.radiantcms.org/extensions/49-twitter
Vapor http://ext.radiantcms.org/extensions/26-vapor
... and others

We migrated data from WordPress and moved to Disqus for commenting (http://disqus.com/ 
)

Let 'em know what you think 
http://www.ignitesocialmedia.com/your-input-welcome-on-our-site-redesign/

Jim Gay
http://www.saturnflyer.com



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] [ANN] Paperclipped Extension improvements

2009-03-17 Thread Michael Kessler

This problem has been fixed: 
http://github.com/kbingman/paperclipped/commit/ded568b82f219799da98f826f45cdda6a51387fc

On Mar 16, 2009, at 11:18 PM, michael starke wrote:

Nice feature, better thant the litte if_attachment hack i added  
for my projects ;)


but i got one problme, wich is not quite related to your  
improcements, but maybe someone has a clue:


when i run

rake radiant:extensions:migrate:paperclipped

i get an error stating this:

== 20090316132151 DisableFileTypes: migrating  
=

-- Setting default content types in Radiant::Config
rake aborted!
undefined method `find' for Config:Module

hope it's a dump error on my side ;)

greetings and thanks for the improvements!

___m i c h a e l   s t a r k e
  co-founder of
  HicknHack Software GbR
  www.hicknhack.com
  Graphics

___c o n t a c t
  +49 (170) 3686136
  +49 (351) 4045428
  cont...@hicknhack.com

___H i c k n H a c k   S o f t w a r e   G b R
  maik lathan - andreas reischuck - michael starke
  hübnerstraße 8
  01069 dresden - germany

On 16.03.2009, at 20:04, Istvan Hoka wrote:


Hi everyone!

We have made some changes to Paperclipped we thought you might like:

* r:assets:each enhanced with limit, offset, order, by, extension  
filtering;

* r:if_assets and r:unless_assets tags for conditional rendering;
* r:assets:width and r:assets:height via imagesize gem;
* better migration compatibility with PageAttachments extension  
when they have title and description fields (degrades gracefully).


Fork is at: http://github.com/Aissac/paperclipped/tree/master. Pull  
requests have been sent out.


Cheers!

--
Istvan Hoka

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Re: Multiple Sites with seperate users

2009-02-15 Thread Michael Kessler

Nick Plate has done user scoping for the multi_site extension: 
http://github.com/zapnap/radiant-multi-site-extension/commit/46a035d00126be51a49f431e4838f3968d156486
but unfortunately he did it just before josh french converted the  
official tests to specs. So you have either the official multi_site  
with specs and no user scoping, or the user scoped multi_site with no  
specs. I planned to convert Nicks enhanced version with tests to  
specs, but I didn't found any free time until now.


Michael


On 14 Feb 2009, at 11:13 PM, Troy Mac Neil wrote:



On 14-Feb-09, at 5:30 PM, Bartee Lamar wrote:


Mr Magpie wrote:

Jeffrey Jones wrote:

There is an extension for the first part, running sites separately:

http://ext.radiantcms.org/extensions/3-multi-site

Not sure on its compatibility with radiant 0.7 nor running two  
separate

sites while sharing content.


Thanks for that. Does anyone know how seperate the sites are from  
each

other ?

Or is it mainly useful for a single user running multiple sites ?

Also, if I run each client as a seperate install of Radiant, would  
any
Ruby interpreter manage memory eficiently by only keeping one copy  
of

Rails and Radiant in memory ?

And how hard would it be for Radiant to support multiple independant
sites from a single install ?


I am trying to do the same thing.  I installed multi_site.  It does
provide for multiple sites, but from what I can determine does not
provide user scope.  That is each user is assigned to a site and the
user can ONLY see their pages/snippets/layouts.  So without that it
really does not do me any good to have all of my clients using one
radiant code base.


I'm in a similar situation and have found some code that gives the  
appearance of user scope for many of the more common extensions. The  
standard approach seems to be to hide the content from other users  
rather than deny them access which is not ideal but works well  
enough for my users.


I'd love to see a little more support for multi-site deployments.  
Ruby deployments are still quite resource intensive and running  
multiple sites on a single codebase is the best way to minimize  
resource usage right now.


Here are the two I have bookmarked though I also found similar  
projects for other extensions at github.

http://github.com/netzpirat/radiant-search-multi-site-extension/tree/master
http://github.com/netzpirat/radiant-paperclipped-multisite-extension/tree/master

Troy
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] WebDav extension refactored

2009-02-06 Thread Michael Kessler
I just want to inform you that the WebDav extension has been  
refactored and the missing features like authentication and a proper  
page tree have been implemented. The extension is now also aware of  
the SnS and LanguageRedirect extensions and will handle those content  
properly.


So if you ever wanted to edit your pages, page parts, snippets,  
layouts, javascripts and stylesheets remotely with your favorite  
editor, you should give http://github.com/willcodeforfoo/radiant-dav-extension/tree/master 
 a try...


Michael
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] WebDav extension refactored

2009-02-06 Thread Michael Kessler
I just want to inform you that the WebDav extension has been  
refactored and the missing features like authentication and a proper  
page tree have been implemented. The extension is now also aware of  
the SnS and LanguageRedirect extensions and will handle those content  
properly.


So if you ever wanted to edit your pages, page parts, snippets,  
layouts, javascripts and stylesheets remotely with your favorite  
editor, you should givehttp://github.com/willcodeforfoo/radiant-dav-extension/tree/master 
 a try...


Michael

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] what extensions do you have installed?

2009-01-28 Thread Michael Kessler

Here are mine:

admin_breadcrumbs (heads/master)
copy_move (heads/master)
dashboard (heads/master)
gallery (heads/master)
help (v1-20-gc14a55e)
import_export (heads/master)
iphone (heads/master)
multi_site (heads/master)
navigation_tags (heads/master)
page_preview
paperclipped (heads/master)
paperclipped_multisite (heads/master)
ray (heads/experimental)
reorder (heads/master)
search (heads/master)
search_multi_site (heads/master)
settings (heads/master)
share_layouts (heads/master)
sns (v0.7.1-11-g7dc898f)
tags (heads/master)
tags_multi_site (heads/master)
wym_editor_filter (heads/master)
attachment_fu (heads/master)

On 28 Jan 2009, at 4:38 AM, john muhl wrote:


I'd like to get some kind of idea what the most popular extensions
are. I'll start, my personal site has (minus the ones packaged with
radiant)

* Bluecloth Filter
* Default Page Parts
* Mailer
* Page Attachments
* RDiscount Markdown Filter
* Shards

I guess Shards gives away that my instance is sort of out of date.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Editing Styles in Radiant CMS

2009-01-09 Thread Michael Kessler
I'm using the 'It's All Text!' Firefox extension, which you'll find  
here: https://addons.mozilla.org/el/firefox/addon/4125?lang=de
I configured Command-E as shortcut to start editing a textarea and  
configured Textmate as editor. Whenever I edit some content Textmate  
will be opened, and Command-S will write back the changed to the  
textarea. This allows comfortable editing but the workflow is not the  
best if you have to edit a lot.


I planned to have a closer look at the dav extension, this would  
enable content editing in the database like a local project. But I  
haven't had time to test it.


Michael

On 9 Jan 2009, at 4:26 AM, Mark Muskardin wrote:


Hello,

I'm a newb to Radiant CMS :)

I'd like to edit the HTML structure of my Radiant CMS entries.   
Inside of
the Articles parent page, I've added a div around r:content.   
But
after I click save, this new markup does not display in source.  I  
would
prefer to edit the markup from my text-editor instead of the admin  
browser

interface, but I can't locate the files in my Rails project.

Can you use a text editor to directly edit the files instead of  
using the
browser interface?  This would be a boon to productivity.  Where are  
these

files located in the file-system?

Also, am I correct in assuming that you can only create Controllers  
and

Models by creating Extensions?

Thanks so much!

//M
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Editing Styles in Radiant CMS

2009-01-09 Thread Michael Kessler
The DAV extension (http://github.com/willcodeforfoo/radiant-dav-extension/tree/master 
) would allow us to edit the content in any IDE or editor, not just  
Eclipse. The code in the extension isn't complicated and the TODO file  
lists:


* Authentication
* Figure out why you get the directory inside of the directory
* Page hierarchy

So I guess there won't be much work to make the extension usable for  
my need. I planned to modify that extension within the next weeks and  
add those features, since I think it will boost the productivity of  
our team.


On 9 Jan 2009, at 7:37 PM, Adam van den Hoven wrote:

+1 for Its All Text!  Textmate. Thanks for the reminder about the  
short cut; I hate looking for that little icon.


I suppose, though, if you wanted a real IDE, one could write an  
Eclipse extension... (ouch my brain hurts)


On 9-Jan-09, at 10:31 AM, Michael Kessler wrote:

I'm using the 'It's All Text!' Firefox extension, which you'll find  
here: https://addons.mozilla.org/el/firefox/addon/4125?lang=de
I configured Command-E as shortcut to start editing a textarea and  
configured Textmate as editor. Whenever I edit some content  
Textmate will be opened, and Command-S will write back the changed  
to the textarea. This allows comfortable editing but the workflow  
is not the best if you have to edit a lot.


I planned to have a closer look at the dav extension, this would  
enable content editing in the database like a local project. But I  
haven't had time to test it.


Michael

On 9 Jan 2009, at 4:26 AM, Mark Muskardin wrote:


Hello,

I'm a newb to Radiant CMS :)

I'd like to edit the HTML structure of my Radiant CMS entries.   
Inside of
the Articles parent page, I've added a div around  
r:content.  But
after I click save, this new markup does not display in source.  I  
would
prefer to edit the markup from my text-editor instead of the admin  
browser

interface, but I can't locate the files in my Rails project.

Can you use a text editor to directly edit the files instead of  
using the
browser interface?  This would be a boon to productivity.  Where  
are these

files located in the file-system?

Also, am I correct in assuming that you can only create  
Controllers and

Models by creating Extensions?

Thanks so much!

//M
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] error after install

2008-12-13 Thread Michael Kessler

Good idea Mohit

I added this page to the wiki: 
http://wiki.radiantcms.org/undefined_method_for_enumerable

It would be nice if a native English speaking person will have a look  
at it, just to keep the quality high ;-)


Michael


On 13 Dec 2008, at 2:03 AM, Mohit Sindhwani wrote:


Robert Calco wrote:
Adding this to environment.rb before the Radiant::Initializer.run  
do line

makes it work on 1.8.7:

unless '1.9'.respond_to?(:force_encoding)
String.class_eval do
  begin
remove_method :chars
  rescue NameError
# OK
  end
end
end

I don't remember who gave me that from this list but whoever it  
was, thank

you again!

- Bob



Hi!  A request but could someone please add this to the Reboot wiki  
as a frequently asked question.  With 1.8.7 becoming more common,  
this will be asked more frequently.


The wiki is at:  http://wiki.radiantcms.org/Summer_Reboot
A sample FAQ that you could use as a base is: 
http://wiki.radiantcms.org/Intermittent_Errors_with_SQLite_on_Windows

Thanks
Mohit.

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] Language Redirect Extension

2008-12-09 Thread Michael Kessler

Hi everyone,

I'm looking for the Language Redirect extension, but unfortunately  
the subversion repository that is linked from the third-party  
extension page on the radiant wiki has been deleted. Can someone who  
has this extension installed kindly provide me a copy, or better share  
it on github so that we can update the wiki?


Thanks a lot
Michael
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Language Redirect Extension

2008-12-09 Thread Michael Kessler

John,

I had a look at those extensions, but I feel that the simplicity and  
independency of the different language trees are exactly what I've  
looked for.


Anyway thanks for all the responses.

Michael

On 9 Dec 2008, at 10:11 PM, john wrote:


On 2008/12/09, at 14:03, Michael Kessler wrote:


Hi everyone,

I'm looking for the Language Redirect extension, but  
unfortunately the subversion repository that is linked from the  
third-party extension page on the radiant wiki has been deleted.  
Can someone who has this extension installed kindly provide me a  
copy, or better share it on github so that we can update the wiki?


Maybe one of these 3 extensions on GitHub provide a similar  
solution. I haven't personally investigated any of the options.


= 
= 
= 
= 
= 
= 
= 
= 
==

   url: http://github.com/lorenjohnson/radiant-language-switch
description: A basic internationalization extension for Radiant CMS  
which

 allows simple template switching based upon language.
= 
= 
= 
= 
= 
= 
= 
= 
==

   url: http://github.com/DefV/site_language
description: Radiant Extension for multiple language support
= 
= 
= 
= 
= 
= 
= 
= 
==

   url: http://github.com/peburrows/translator
description: Radiant extension for simple, elegant language  
localization
= 
= 
= 
= 
= 
= 
= 
= 
==



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Using Git with Radiant Extensions

2008-10-17 Thread Michael Kessler

Chris,

You may want to have a look at the ray extension. It enables you to  
manage your extension also as git submodules. I just discovered this  
extension and enhanced my fork to accept a 'remote' variable either on  
the command line or within the bundles extensions.yml (to install a  
bunch of extension), so you can add git remotes automatically with the  
installation of the extension. There is also a new rake task ray:pull  
that pulls all remote sources to the submodule. This comes handy when  
you're developing an extension that you have forked.


Michi

On 17 Oct 2008, at 5:03 PM, Chris Parrish wrote:


So, to make sure I understand...

If I have an extension of mine in a submodule of a project, I can  
develop within that extension:


  * make changes in that copy of the extension (testing its behavior
as part of the project)
  * commit those changes to the submodule's repo
  * manage branching (gitk, etc) from within that submodule

If so, that helps me a lot.  Everything I'd read made it sound like  
submodules don't behave like a working git repo which is why I  
thought you couldn't push changes back to the original -- that  
submodules only permitted data transfer one-way (from source to your  
local copy).


-Chris

Sean Cribbs wrote:
Like svn:externals, you can maintain a submodule in a project,  
commit to it and push it while maintaining the parent project.   
However, whenever you've changed something in the submodule, it's  
necessary to go back up to the parent project, commit the submodule  
directory, and possibly do `git submodule init` and `git submodule  
update` (I don't know if that's strictly necessary, but I like to  
do it to be certain).  That will make sure that the next time your  
parent project is checked out, it will get the latest submodule  
version.


Sean

Chris Parrish wrote:
Trying to get up to speed with a Git workflow and I have some  
questions about working with extensions.


If I have a radiant project A that uses someone else's extensions  
B, C, and D.  I understand that I can create a repo for radiant  
project A set up all the extensions as submodules (if they're all  
in git repos).


If, on the other hand, I'm developing extension B, I could set up  
a dummy project A (no repo), and set up B, C, and D as  
independent, parallel repos. No submodules. With B being the one  
I'm working on, managing, branching, etc. of course.


But what if I'm developing extension B along with project A?  If  
you edit code within a submodule B, there's no way to send those  
changes back to the original B repo (or use branching, or other  
git tools) on B is there?  Git isn't really tracking your changes  
on B is it?


Is there some way to handle this development situation or am I  
just going about this wrong?


Is piston or braid an option here and if so, is anyone using it  
successfully?


Thanks,


-Chris Parrish


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant