[Radiant] Search patch (global tags)
I have been following this guide to add search to radiant. http://wiki.radiantcms.org/Using_the_Search_Extension I would like to add search globally - not only on a specific search page. And to do that I have to apply the search_extension.diff patch, but when I run it it says: [EMAIL PROTECTED] radapp]$ patch -p0 search_extension.diff patching file vendor/extensions/search/test/unit/search_page_test.rb patching file vendor/extensions/search/test/unit/search_tags_test.rb patching file vendor/extensions/search/test/functional/search_extension_test.rb patching file vendor/extensions/search/test/fixtures/pages.yml patching file vendor/extensions/search/test/fixtures/page_parts.yml patching file vendor/extensions/search/app/models/search_page.rb Hunk #2 succeeded at 72 (offset 8 lines). patching file vendor/extensions/search/app/models/search_tags.rb patching file vendor/extensions/search/search_extension.rb Hunk #1 FAILED at 9. 1 out of 1 hunk FAILED -- saving rejects to file vendor/extensions/search/search_extension.rb.rej I kind of hoped it did not matter, but when i add the search tag on a page it displays: undefined tag `search' (I also ran rake production db:migrate:extensions after the patch was applied) -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Haml and textareas in custom extension
I have looked at the extension tutorial again and the controller there extends the ApplicationController like I do. Any ideas about what I could try and look at? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Search patch (global tags)
Now suddenly it is even more broken - it now says: undefined tag `form' I then deleted the search extension folder. Re-unpacked the tar.gz file - renamed the folder to search and ran rake, but it still says: undefined tag `form' -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Search patch (global tags)
Jan frederik Poulsen wrote: Now suddenly it is even more broken - it now says: undefined tag `form' I then deleted the search extension folder. Re-unpacked the tar.gz file - renamed the folder to search and ran rake, but it still says: undefined tag `form' Okay now the basic search is working again. It seems some time has to pass before it kind of resets. But I would still like global search and live search, what seems to be the issue with the search_extension.diff patch? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Will Paginate and radiant-paginate-extension?
I seem to have some issues with installing pagination in Radiant too:
I want to use radiant-paginate-extension:
http://github.com/ihoka/radiant-paginate-extension/tree/master
But when I rake I get:
rake production db:migrate:extensions
(in /home/chainrea/radapp)
rake aborted!
Expected
/home/chainrea/radapp/vendor/extensions/paginate/app/models/paginate_tags.rb
to define PaginateTags
I suspect the issue to be related to the requirement of the gem Will
Paginate.
http://github.com/mislav/will_paginate/tree/master
And I have installed it prior to installing radiant-paginate, but
maybe it isn't configured properly?
It is installed in my gems folder and I have edited the environment.rb
in myradiant/config/ adding the line:
require 'will_paginate'
at the bottom like this:
--
# Be sure to restart your server when you modify this file
# Uncomment below to force Rails into production mode when
# you don't control web/app server and can't set it the proper way
ENV['RAILS_ENV'] ||= 'production'
ENV['GEM_PATH'] = '/home/chainrea/gems:/usr/lib/ruby/gems/1.8'
# Specifies gem version of Rails to use when vendor/rails is not present
require File.join(File.dirname(__FILE__), 'boot')
require 'radius'
Radiant::Initializer.run do |config|
# Settings in config/environments/* take precedence over those
specified here.
# Application configuration should go into files in
config/initializers
# -- all .rb files in that directory are automatically loaded.
# See Rails::Configuration for more options.
# Skip frameworks you're not going to use (only works if using
vendor/rails).
# To use Rails without a database, you must remove the Active Record
framework
config.frameworks -= [ :action_mailer ]
# Only load the plugins named here, in the order given. By default,
all plugins
# in vendor/plugins are loaded in alphabetical order.
# :all can be used as a placeholder for all plugins not explicitly
named
# config.plugins = [ :exception_notification, :ssl_requirement, :all ]
# Only load the extensions named here, in the order given. By default
all
# extensions in vendor/extensions are loaded, in alphabetical order.
:all
# can be used as a placeholder for all extensions not explicitly
named.
# config.extensions = [ :all ]
# Force all environments to use the same logger level
# (by default production uses :info, the others :debug)
# config.log_level = :debug
# Your secret key for verifying cookie session data integrity.
# If you change this key, all old sessions will become invalid!
# Make sure the secret is at least 30 characters and all random,
# no regular words or you'll be exposed to dictionary attacks.
config.action_controller.session = {
:session_key = '_radiant_session',
:secret = 'asdfqwerfxcoivswqenadfasdfqewpfioutyqwel'
}
# Use the database for sessions instead of the cookie-based default,
# which shouldn't be used to store highly confidential information
# (create the session table with 'rake db:sessions:create')
config.action_controller.session_store = :active_record_store
# Use SQL instead of Active Record's schema dumper when creating the
test database.
# This is necessary if your schema can't be completely dumped by the
schema dumper,
# like if you have constraints or database-specific column types
# config.active_record.schema_format = :sql
# Enable page/fragment caching by setting a file-based store
# (remember to create the caching directory and make it readable to
the application)
# config.action_controller.fragment_cache_store = :file_store,
#{RAILS_ROOT}/fragment_cache
config.action_controller.page_cache_directory = #{RAILS_ROOT}/cache
# Activate observers that should always be running
config.active_record.observers = :user_action_observer
# Make Active Record use UTC-base instead of local time
config.active_record.default_timezone = :utc
# Set the default field error proc
config.action_view.field_error_proc = Proc.new do |html, instance|
%{div class=error-with-field#{html} small class=errorbull;
#{[instance.error_message].flatten.first}/small/div}
end
config.after_initialize do
# Add new inflection rules using the following format:
Inflector.inflections do |inflect|
inflect.uncountable 'config'
inflect.uncountable 'meta'
end
# Auto-require text filters
Dir[#{RADIANT_ROOT}/app/models/*_filter.rb].each do |filter|
require_dependency File.basename(filter).sub(/\.rb$/, '')
end
# Response Caching Defaults
ResponseCache.defaults[:directory] =
ActionController::Base.page_cache_directory
ResponseCache.defaults[:logger]= ActionController::Base.logger
end
end
require 'will_paginate'
--
So will_paginate should be working? or am i doing something wrong
here?
I've just installed comments, and it seems to work 50 % it gets
installed but doesn't work - probeably becuse will_paginate doesn't
work?
--
Posted via
[Radiant] Syntax Highlighting
Is anyone using the syntax_highlighting extension? http://github.com/marcoow/syntax_highlighting/tree/master It seems to be doing the parsing, but when it renders in a page, it's strictly as code html, so all the span tags that input as part of it are rendered as well. For example, r:code language=python import pygments foo = bar /r:code renders as: span class=kimport/span span class=nnpygments/span span class=nfoo/span span class=o=/span span class=nbar/ span Any ideas? There is currently no filter set on the page, and if I set it to textile all theget turned to lt; gt;, respectively. Is there another option for syntax highlighting? I would like to have more languages than code_ray currently supports. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Will Paginate and radiant-paginate-extension?
I don't know what the standard radiant practice is for gem plugins,
but for will_paginate I think you have to install it as a plugin in
vendor/plugins. I don't know if the version of Rails vendor'd in
Radiant uses the new 'gem' syntax.
I would love to hear differently. :)
On Jul 15, 2008, at 9:45 AM, Jan frederik Poulsen wrote:
I seem to have some issues with installing pagination in Radiant too:
I want to use radiant-paginate-extension:
http://github.com/ihoka/radiant-paginate-extension/tree/master
But when I rake I get:
rake production db:migrate:extensions
(in /home/chainrea/radapp)
rake aborted!
Expected
/home/chainrea/radapp/vendor/extensions/paginate/app/models/
paginate_tags.rb
to define PaginateTags
I suspect the issue to be related to the requirement of the gem Will
Paginate.
http://github.com/mislav/will_paginate/tree/master
And I have installed it prior to installing radiant-paginate, but
maybe it isn't configured properly?
It is installed in my gems folder and I have edited the
environment.rb
in myradiant/config/ adding the line:
require 'will_paginate'
at the bottom like this:
--
# Be sure to restart your server when you modify this file
# Uncomment below to force Rails into production mode when
# you don't control web/app server and can't set it the proper way
ENV['RAILS_ENV'] ||= 'production'
ENV['GEM_PATH'] = '/home/chainrea/gems:/usr/lib/ruby/gems/1.8'
# Specifies gem version of Rails to use when vendor/rails is not
present
require File.join(File.dirname(__FILE__), 'boot')
require 'radius'
Radiant::Initializer.run do |config|
# Settings in config/environments/* take precedence over those
specified here.
# Application configuration should go into files in
config/initializers
# -- all .rb files in that directory are automatically loaded.
# See Rails::Configuration for more options.
# Skip frameworks you're not going to use (only works if using
vendor/rails).
# To use Rails without a database, you must remove the Active Record
framework
config.frameworks -= [ :action_mailer ]
# Only load the plugins named here, in the order given. By default,
all plugins
# in vendor/plugins are loaded in alphabetical order.
# :all can be used as a placeholder for all plugins not explicitly
named
# config.plugins =
[ :exception_notification, :ssl_requirement, :all ]
# Only load the extensions named here, in the order given. By default
all
# extensions in vendor/extensions are loaded, in alphabetical order.
:all
# can be used as a placeholder for all extensions not explicitly
named.
# config.extensions = [ :all ]
# Force all environments to use the same logger level
# (by default production uses :info, the others :debug)
# config.log_level = :debug
# Your secret key for verifying cookie session data integrity.
# If you change this key, all old sessions will become invalid!
# Make sure the secret is at least 30 characters and all random,
# no regular words or you'll be exposed to dictionary attacks.
config.action_controller.session = {
:session_key = '_radiant_session',
:secret = 'asdfqwerfxcoivswqenadfasdfqewpfioutyqwel'
}
# Use the database for sessions instead of the cookie-based default,
# which shouldn't be used to store highly confidential information
# (create the session table with 'rake db:sessions:create')
config.action_controller.session_store = :active_record_store
# Use SQL instead of Active Record's schema dumper when creating the
test database.
# This is necessary if your schema can't be completely dumped by the
schema dumper,
# like if you have constraints or database-specific column types
# config.active_record.schema_format = :sql
# Enable page/fragment caching by setting a file-based store
# (remember to create the caching directory and make it readable to
the application)
# config.action_controller.fragment_cache_store = :file_store,
#{RAILS_ROOT}/fragment_cache
config.action_controller.page_cache_directory = #{RAILS_ROOT}/cache
# Activate observers that should always be running
config.active_record.observers = :user_action_observer
# Make Active Record use UTC-base instead of local time
config.active_record.default_timezone = :utc
# Set the default field error proc
config.action_view.field_error_proc = Proc.new do |html, instance|
%{div class=error-with-field#{html} small class=errorbull;
#{[instance.error_message].flatten.first}/small/div}
end
config.after_initialize do
# Add new inflection rules using the following format:
Inflector.inflections do |inflect|
inflect.uncountable 'config'
inflect.uncountable 'meta'
end
# Auto-require text filters
Dir[#{RADIANT_ROOT}/app/models/*_filter.rb].each do |filter|
require_dependency File.basename(filter).sub(/\.rb$/, '')
end
# Response Caching Defaults
ResponseCache.defaults[:directory] =
ActionController::Base.page_cache_directory
ResponseCache.defaults[:logger]=
Re: [Radiant] Syntax Highlighting
It's not perfect, but I like using Dan Webb's Syntax Highlighter (JavaScript). Just put your source code inside code tags with the class of the language you want, like so: code class=rubyputs Hello, World!/code You can download it at http://danwebb.net. Sean Josh Schairbaum wrote: Is anyone using the syntax_highlighting extension? http://github.com/marcoow/syntax_highlighting/tree/master It seems to be doing the parsing, but when it renders in a page, it's strictly as code html, so all the span tags that input as part of it are rendered as well. For example, r:code language=python import pygments foo = bar /r:code renders as: span class=kimport/span span class=nnpygments/span span class=nfoo/span span class=o=/span span class=nbar/span Any ideas? There is currently no filter set on the page, and if I set it to textile all theget turned to lt; gt;, respectively. Is there another option for syntax highlighting? I would like to have more languages than code_ray currently supports. ___ 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] Syntax Highlighting
Sean, That's sharp. I love the fact that it's unobtrusive and seems much more accessible for customization than some of the others. Thanks for pointing it out. Have you written a regex for anything? Regards, Josh On Jul 15, 2008, at 10:01 AM, Sean Cribbs wrote: It's not perfect, but I like using Dan Webb's Syntax Highlighter (JavaScript). Just put your source code inside code tags with the class of the language you want, like so: code class=rubyputs Hello, World!/code You can download it at http://danwebb.net. Sean Josh Schairbaum wrote: Is anyone using the syntax_highlighting extension? http://github.com/marcoow/syntax_highlighting/tree/master It seems to be doing the parsing, but when it renders in a page, it's strictly as code html, so all the span tags that input as part of it are rendered as well. For example, r:code language=python import pygments foo = bar /r:code renders as: span class=kimport/span span class=nnpygments/span span class=nfoo/span span class=o=/span span class=nbar/span Any ideas? There is currently no filter set on the page, and if I set it to textile all theget turned to lt; gt;, respectively. Is there another option for syntax highlighting? I would like to have more languages than code_ray currently supports. ___ 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] Syntax Highlighting
Josh, No, but you can steal my CSS styles: http://seancribbs.com/stylesheets/code.css Sean Josh Schairbaum wrote: Sean, That's sharp. I love the fact that it's unobtrusive and seems much more accessible for customization than some of the others. Thanks for pointing it out. Have you written a regex for anything? Regards, Josh On Jul 15, 2008, at 10:01 AM, Sean Cribbs wrote: It's not perfect, but I like using Dan Webb's Syntax Highlighter (JavaScript). Just put your source code inside code tags with the class of the language you want, like so: code class=rubyputs Hello, World!/code You can download it at http://danwebb.net. Sean Josh Schairbaum wrote: Is anyone using the syntax_highlighting extension? http://github.com/marcoow/syntax_highlighting/tree/master It seems to be doing the parsing, but when it renders in a page, it's strictly as code html, so all the span tags that input as part of it are rendered as well. For example, r:code language=python import pygments foo = bar /r:code renders as: span class=kimport/span span class=nnpygments/span span class=nfoo/span span class=o=/span span class=nbar/span Any ideas? There is currently no filter set on the page, and if I set it to textile all theget turned to lt; gt;, respectively. Is there another option for syntax highlighting? I would like to have more languages than code_ray currently supports. ___ 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
[Radiant] radiant-help-extension
Heads up! Help is moving: http://github.com/saturnflyer/radiant-help-extension/tree It was formerly named radiant-help but the convention seems to be to include '-extension' on github. Help will now fall in line with others and you can use it with extensions like Ray: http://github.com/johnmuhl/radiant-ray-extension/tree/master/ What is Help? It provides role-based user information for the features of Radiant AND allows extension developers to provide documentation for their extensions within the Radiant interface. The best part: no dependencies. Developers can create documentation for their extensions without worry that something will break if Help isn't loaded. More help documentation for Radiant features is coming, including screenshots (which you will, of course, be able to override). See more at http://github.com/saturnflyer/radiant-help-extension/tree ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Styles 'n Scripts v0.6 Styles 'n Scripts Sass Filter v0.2
Minor changes here... https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_sass_filter/tags/latest Styles 'n Scripts now belongs in a directory named sns like: [your radiant project]/vendor/extensions/sns No changes to your db, no changes to the UI, no rake updating -- just this directory name change. Everything else is the same to you and your users. (Except all the rake tasks use sns instead of styles_n_scripts but that should be a welcome change). The new SnS Sass Filter version is required to work with the new Sns release. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content multiple parts (was if_content with inherit)
I'm eager to see these additions in the core, but rather than just bugging them with pull requests would anyone like to give it a +/- 1 for adding in for 0.6.8? The changes in my repo add: 1) inherit = true to r:if_content and r:unless_content to work just like the r:content tag. 2) allow a list of parts to find such as r:if_content part=this, that, other 3) add a find=any or find=all to change the condition when listing multiple parts On Jul 10, 2008, at 3:05 PM, Jim Gay wrote: I ended up going with find=any | all because it just made more sense when applied to unless_content. My additions are here: http://github.com/saturnflyer/radiant/tree ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content multiple parts (was if_content with inherit)
Jim, I'm working on the core this week so I'll pull in those changes. Sean Jim Gay wrote: I'm eager to see these additions in the core, but rather than just bugging them with pull requests would anyone like to give it a +/- 1 for adding in for 0.6.8? The changes in my repo add: 1) inherit = true to r:if_content and r:unless_content to work just like the r:content tag. 2) allow a list of parts to find such as r:if_content part=this, that, other 3) add a find=any or find=all to change the condition when listing multiple parts On Jul 10, 2008, at 3:05 PM, Jim Gay wrote: I ended up going with find=any | all because it just made more sense when applied to unless_content. My additions are here: http://github.com/saturnflyer/radiant/tree ___ 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] Styles n Scripts feature request
On Tue, Jul 15, 2008 at 12:43 AM, Chris Parrish [EMAIL PROTECTED] wrote: Jim Gay wrote: I haven't yet looked at it. I haven't used Sass much. I like some of the features that it adds, but it removes some control and I'm not ready to tackle it yet since I've run into trouble with Haml and the Help extension (it has some lines that are completely ignored by Haml... but they shouldn't be). I too have struggled with Haml. It has some very nice benefits but can also be a real pain too. I've had the same experience with Markaby... I'd love to use it, but there are too many hurdles. ERB usually ends up being s much easier (and there's no processing cost with ERB). That said, I think I like Sass much more than both Haml and regular CSS (I still haven't used it enough to have a firm conclusion). It's much simpler than Haml and doesn't have to handle things like running ruby in the middle of your template. And it encourages some very good CSS behaviors. Worth trying for sure. Here, here. SASS actually provides more control than plain old CSS. Here's something I did with SASS when on a golden-ratio trip: // The golden ratio is (1 + sqrt(5)) / 2 // sqrt(5) ~= 2.23606798 !phi = 3.23606798 / 2 !phiinv = 1 / !phi !phiinvcom = 1 - !phiinv !fnt_size = 12 !line_height = !fnt_size * !phi !full_width = 960 !sidebar_width = !full_width * !phiinvcom !padding = 12 !content_width = !full_width - !sidebar_width - !padding*2 So later on in my Simply Awesome StyleSheet, I have #container :margin 0 auto :width = !full_width + px :position relative :display block hr :display none #content :padding :top = !padding * 2 + px :right = !padding + px :bottom = !padding + px :left = !padding + px :width = !content_width + px So the entire layout can scale by changing one variable. Neat, huh? -- Tim ___ 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] Styles 'n Scripts v0.6 Styles 'n Scripts Sass Filter v0.2
On Tue, Jul 15, 2008 at 12:56 PM, Chris Parrish [EMAIL PROTECTED] wrote: Minor changes here... https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_sass_filter/tags/latest Styles 'n Scripts now belongs in a directory named sns like: [your radiant project]/vendor/extensions/sns No changes to your db, no changes to the UI, no rake updating -- just this directory name change. Everything else is the same to you and your users. (Except all the rake tasks use sns instead of styles_n_scripts but that should be a welcome change). The new SnS Sass Filter version is required to work with the new Sns release. -Chris For you GitHub addicts out there: http://github.com/MrGossett/radiant_sns_extension/tree/master http://github.com/MrGossett/radiant_sns_sass_filter_extension/tree/master I'm still feeling my way along with git-svn, but I'm pretty sure I've got all of Chris's changes here. Any changes to sns_minifier, Chris? -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Developing Radiant site
Hi, I'm new to Radiant, but not Rails. So, I'm seeing that stuff like the layout and CSS is entered through forms and saved to the database, and aren't contained in version controlled files. So, how does that work? I mean, how do you deploy changes? Just by copy/pasting the updated snippets and css stuff to the live site and enter it into the form? How do you version control it? Seems a little weird to me, perhaps I'm missing something? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Has anyone added WMD to the admin interface?
Ooh, WMD's gone MIT licensing. Now this is nice to see. One more thing to play with... -Chris Oli Studholme wrote: Hi All, Has anyone added the WMD markdown editor to the admin interface yet? Or any WYSIWIG editor? I’m looking for some advice on the recommended way to do so. peace - oli ___ 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] Preview functionality
I've created a Staging extension. You create a staging instance of the radiant app that can either reside on the same server as the production instance or another server. The extension gives you a Staging tab, where you can click a button to migrate the staging db to the production db. The extension also disables the admin functions on the production instance. So, the idea is that you make all your changes on the staging instance and once you like the way staging looks, you stage the db to production. There is also the ability to easily revert to a previous stage by simply clicking on a previous stage. There are some caveats. In order to make sure that all the foreign keys between tables don't get out of whack, I am doing bulk exports and and imports, completely outside of ActiveRecord. Because my client uses MySQL for their radiant app, I have coded it using the mysqldump and mysql source commands. So, right now, the extension only works for MySQL databases. My client just started using this extension this week. So far so good. I have started discussions with them about letting me open-source the extension, and so far, their response has been positive. There are a few technical issues I need to clean up before I could release the extension, but I hope to get these resolved and get permission from them to release it within the next two weeks. This is definitely not the ultimate answer for the whole preview/versioning thing needed in radiant. Its what I came up with to meet a specific client request in a minimum amount of time. If this sounds like something others could use/improve/build-on then I would love to get it open sourced. Jamey On Tue, Jul 15, 2008 at 11:50 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: Hi, Say someone wants to edit the front page. It's been published. So they edit it. Ideally, they'd be able to make their changes (and save them) without updating the front page (so that another person could review and then choose to publish them). What's the best way to go about doing that in Radiant? Thanks, Joe ___ 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] .htaccess mod_rewrite woes
Hi All,
I just can’t seem to get redirects going in
Radiant’s .htaccess. Can someone enlighten me?
In the default .htaccess file after RewriteEngine On (shich should be
after the Options at the top btw) I tried these vavriants
RewriteRule from.html to.html
RewriteRule from.html http://domain/to.html [R=301,L]
RewriteCond %{REQUEST_URI} ^/from\.html
RewriteRule .* http://domain.com/to.html [R=301,L]
which all work on another domain on this server. Nothing happens. I
also tried adding the example ‘tell Rails to ignore this’
rules, but I’m probably doing it wrong.
RewriteRule from.html to.html
RewriteCond %{REQUEST_URI} ^/to\.html
RewriteRule .* - [L]
Any ideas? I actually want to redirect one file and map it to a
subdomain (eg http://domain.com/test to http://test.domain.com/), but
I can’t even get simple file redirection going. Finally
I’d like to know if it’s possible to use .htaccess to
generate canonical URLs. Specifically I want http://domain.com/ to
redirect to http://www.domain.com/, and all trailing slashes to be
stripped eg http://www.domain.com/news/ to http://www.domain.com/news
Thanks for your time
peace - oli
PS This is using Radiant 0.6.6, the last version that supports the
gettext interface localization plugin I’m using. Btw what needs
to be done to resurrect jargon’s gibberish i18n support?
I can’t even get jargon to install atm
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
