{15} Possible Tickets with Spam (45 matches)

Add ability to scope sites/pages and layouts to users See: http://groups.google.com/group/radiantcms-dev/browse_thread/thread/cbc3f0f77fe89db8 and: http://blog.zerosum.org/2008/4/3/radiant-super-multi

Could also spin this out as a separate extension if this functionality isn't desired in the core multi_site extension.

Hi,

I don't know where to post this error, so I put it here :

When I wanted ti add an attachment to a bug I had this error :

blablabla...
OSError: [Errno 13] Permission denied: '/var/www/vhosts/radiantcms.org/subdomains/trac/httpdocs/attachments/ticket/627'

The current 0.6.4 gem contains an invalid SVN URL which produces a 302. This is quite nasty when unfreezing and then edge-freezing an existing install as the second step will fail. Any subsequent rake commands will fail as well, because boot.rb has been altered for frozen Radiant already.

I guess the following has to be changed.

gems/radiant-0.6.4/lib/tasks/framework.rake:

- svn_root = "http://dev.radiantcms.org/svn/radiant/"
+ svn_root = "http://svn.radiantcms.org/radiant/"

I installed the new 0.6.5RC1 gem, created a new project, bootstrapped the database and started a few mongrels. Everything works fine at this point.

Then svn co http...trunk/shards vendor/extensions/shards and rake radiant:extensions:shards:migrate. Restart the mongrels and the new "Published at" area is missing along with the the "More" button that allows access to slug, breadcrumb etc. No errors or warning are produced by the rake task. However after logging back into the to the admin area and clicking a page to enter the edit view Webkit Web Inspector throws the error,

Null value - http://example.com/javascripts/admin.js?1204010503 (line 54)

and Firebug throws

$("publication-date") has no properties (no name)(select#page_status_id)admin.js (line 54) when(select#page_status_id, function())admin.js (line 82) (no name)()admin.js (line 52) wrapper(dataavailable )prototype.js (line 3842) fire(Document 1, "dom:loaded", undefined)prototype.js (line 3936) _methodized()prototype.js (line 247) fireContentLoadedEvent()prototype.js (line 3969) [Break on this error] $('publication-date').show().select('select').invoke('enable');

rake radiant:extensions:shards:migrate VERSION=0, deleting the shards folder and restarting the mongrels gets rid of all the problems.

I am running a MySQL database under Ubuntu 7.10 server.

There was a failing unit test and the reason it was failing was because there were cache files that were not cleaned up before the test.

/opt/local/bin/ruby -S script/spec -O spec/spec.opts  spec/lib/login_system_spec.rb spec/models/page_part_spec.rb spec/controllers/admin/user_controller_spec.rb spec/lib/radiant/extension_spec.rb spec/lib/radiant/admin_ui_spec.rb spec/models/page_context_spec.rb spec/lib/radiant_spec.rb spec/lib/local_time_spec.rb spec/models/user_spec.rb spec/models/user_action_observer_spec.rb spec/controllers/admin/page_controller_spec.rb spec/lib/radiant/initializer_spec.rb spec/controllers/site_controller_spec.rb spec/lib/radiant/extension_migrator_spec.rb spec/lib/simpleton_spec.rb spec/lib/annotatable_spec.rb spec/models/text_filter_spec.rb spec/models/response_cache_spec.rb spec/models/file_not_found_page_spec.rb spec/models/standard_tags_spec.rb spec/models/status_spec.rb spec/lib/method_observer_spec.rb spec/models/page_spec.rb spec/lib/radiant/taggable_spec.rb spec/models/snippet_spec.rb spec/models/layout_spec.rb spec/controllers/application_controller_spec.rb spec/controllers/admin/welcome_controller_spec.rb spec/lib/inheritable_class_attributes_spec.rb spec/lib/radiant/extension_loader_spec.rb
..................................................................................................................................................................................................................................................................................................................................................PP........................................................................................................F....

Pending:
Admin::PageController should index__with_mangled_cookie (Not Yet Implemented)
Admin::PageController should show the tree partially expanded on the index according to the expanded_rows cookie (Not Yet Implemented)

1)
'SiteController routes page requests should redirect to admin if missing root' FAILED
expected redirect to "http://test.host/admin/welcome", got no redirect
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/expectations.rb:52:in `fail_with'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/expectations/handler.rb:21:in `handle_matcher'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/expectations/extensions/object.rb:34:in `should'
./spec/controllers/site_controller_spec.rb:33:
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_methods.rb:78:in `instance_eval'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_methods.rb:78:in `run_with_description_capturing'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_methods.rb:19:in `execute'
/opt/local/lib/ruby/1.8/timeout.rb:48:in `timeout'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_methods.rb:16:in `execute'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_group_methods.rb:292:in `execute_examples'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_group_methods.rb:291:in `each'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_group_methods.rb:291:in `execute_examples'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/example/example_group_methods.rb:121:in `run'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/runner/example_group_runner.rb:22:in `run'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/runner/example_group_runner.rb:21:in `each'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/runner/example_group_runner.rb:21:in `run'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/runner/options.rb:90:in `run_examples'
/Users/matt/radiant/vendor/plugins/rspec/lib/spec/runner/command_line.rb:19:in `run'
script/spec:12:

Finished in 19.751113 seconds

Sorry guy... It seems my ticket from yesterday disappeared. In the meantime the problem changed a bit, as well as your web site about extensions.

This is what I have done: - checked out and run radiant 0.6.4 successfully - checkout reorder extension (svn export http://dev.radiantcms.org/svn/radiant/tags/rel_0-6-4/extensions/reorder) into the vendor/extension directory successfully - rake db:migrate:extensions and rake radiant:extensions:reorder:update:public - no problem

But then I get this when I access http://localhost:3000/admin/pages:

Mysql::Error: Unknown column 'position' in 'order clause': SELECT * FROM `pages`   WHERE (pages.parent_id = 1)  ORDER BY position ASC

19:     </tr>
20: <%
21: if expanded
22:   page.children.each do |child|
23: -%>
24: <%= render_node child, :level => level + 1, :simple => simple -%>
25: <%

What is wrong here? Something the rake command missed? Any hint?

Thanks a lot!

In the current version of Radiant (0.6.4), there are cases where trying to save a page with invalid entries results in a re-displaying of the edit-page form (good) but without the error messages attached to the fields (not good).

The message: "Validation errors occurred while processing this form. Please take a moment to review the form and correct any input errors before continuing." does show at the top of the page -- but with no field specific messages (or anything to let you know which field is the offender).

In my tests, the bug seems tied to whether or not Radiant is running from the gem or as a local copy within the application. Running from the gem (0.6.4) displays error messages just fine, Radiant installed in the /vendor/ directory (instance mode?) doesn't.

This bug is visible at http://demo.radiantcms.org (which appears to be in instance mode, version 0.6.4). To reproduce:

1. Create a new page (I added a child to the home page).
2. Don't add anything, just click "create page" or "save and continue editing" with your empty form.
3. It chokes on the empty fields (rightly) and tells you so -- but doesn't provide any info about which fields have errors nor what their errors were.

By the way, this split-personality behavior is not limited to admin/pages/edit, but also affects snippets, layouts, and users (all forms, basically).

This patch adds a tag to the standard_tag library, called <r:meta />. The tag description follows:

Creates a meta tag, whose content attribute is populated from a page part. By default, the tag <r:meta /> expands to <meta name="description" content="Taken from page part called description"/>. You can override the @name@ attribute, e.g. name="keywords", and can specify any page part to be used. The content from the specified page part is stripped of all HTML tags before insertion, which is necessary to produce validating code. Anything after 200 characters of content is discarded, although this number can also be modified.

Usage is similar to the <r:content /> tag, with inherit causing the parent page part to be used if this page does not have one. By default, this is set to true.

Only suitable for use in <head> section of a document.

*Usage:* <r:meta [part="part_name"] [inherit="true|false"] [name="description"] [limit="200"] />

The patch also includes conditional children tags from another ticket.

I have taken the liberty of upgrading Radiant JS to be compatible with and leverage the new features of Prototype 1.6.0 and Scriptaculous 1.8.

The patch doesn't contain these libraries - they should be downloaded from their respective trunks: http://svn.rubyonrails.org/rails/spinoffs/scriptaculous/src and http://svn.rubyonrails.org/rails/spinoffs/prototype/trunk

There is a problem when you try to import previously exported data using import_export plugin. I have been getting "User expected, got Fixnum" exception. After some investigation I have found at http://www.railsweenie.com/forums/1/topics/25 comments about similar problem. I have not tried to fix this but instead at the time of export I have just commented out belong_to in app\models\page.rb and app\models\layout.rb.

Most links in the admin interface do not work when a Radiant site is run from a prefix different from the document root '/'. Also, the "breadcrumbs" Radiant tag displays incorrect links. Way to reproduce:

mongrel_rails start  -p 3000 -e development --prefix=/myprefix

Then browse the administration interface at http://localhost:3000/myprefix/admin

Defects:

• Navigation links (Pages, Snippets, Layouts) point to wrong URLs
• In the Pages administration view the expanding children lists point to wrong URLs, again

If a page uses the <r:breadcrumbs/> tag, all of the links point to URLs which disregard the prefix used when starting mongrel.

The two buttons, "Save" and "Save and Continue Editing" really represen two parts of a workflow: First, you make a series of changes, saving each time (and possibly view the page to see the effects), and then you're satisfied and you go on to something else. (see "Saving your work" on http://dev.radiantcms.org/radiant/wiki/UsingRadiant)

The problem is that if the page is published, visitors see those intermediate changes when they shouldn't, but if you change the status to 'Draft', visitors won't see the page all (404)!

This patch changes the two buttons to "Publish" and "Save" and makes them do just that. If you're working with a published page and you Save, you can continue editing and the public won't see your changes until you Publish. You, however, can see them by going to the dev site. The same goes for snippets and layouts.

This seems like a pretty important (and unobtrusive) change, so I'm recommending it be a patch and not an extension. I'd also like a tab that shows you a list of drafts with checkboxes to mass-publish, but this seems like an optional feature best suited for an extension.

http://dev.radiantcms.org/svn/radiant/branches/mental/radiant/app/helpers/admin/extension_helper.rb

In helpers/admin/extension_helper.rb, the extension is named

module Admin::ExtensionControllerHelper?

but should be

module Admin::ExtensionHelper?

This leads to an error due to an issue in Rails where if the default helper is missing, you get something like this: NoMethodError? (undefined method `is_missing?' for #<LoadError:0x377a7c4>):

The code in http://dev.radiantcms.org/radiant/browser/branches/mental/radiant/public/javascripts/pngfix.js was pasted in twice.

When installing Radiant to be served by CGI or FastCGI through Apache stylesheets will not appear when Radiant is in a subdirectory.

for example:

http://example.com/my_radiant/

The stylesheets for the admin section still show up since they're appropriately found through a tag:

    <%= stylesheet_link_tag 'admin' %>

however these guys:

db/templates/styled-blog.yml: <link rel="stylesheet" type="text/css" href="/styles.css" />

db/templates/simple-blog.yml: <link rel="stylesheet" type="text/css" href="/styles.css" />

get lost in the mix. My temporary fix was to go into the database entry and change /styles.css to /my_radiant/styles.css .

Here's a patch for the following tags:

* parent * if_parent * unless_parent

Inspired by http://lists.radiantcms.org/pipermail/radiant/2006-August/001190.html, so this includes unit tests.

I'm new to Radiant, but am very happy with what I see here, and hope to contribute much more in the future. :) Keep up the good work.

Patch for Dror Tirosh's "Page Parts as Attachments"

http://lists.radiantcms.org/pipermail/radiant/2006-July/001002.html

(I didnt write it, just putting it here so other people can access it easily)

I tweaked Dror's code slightly and added a migration (to create the needed page_part_type_id column). I also included the example attachment part type.

SmartyPants? turns straight quotes into smart quotes in HTML source code. E.g.,

<h1 class="headline">Radiant's "filters" rock!</h1>

becomes

<h1 class="headline">Radiant&#8217;s &#8220;filters&#8221; rock!</h1>

Typography geeks love this sort of thing, and there are MovableType? plugins for this, so why not a couple of Radiant filters?

I've also included a Markdown+SmartyPants? filter, which takes something like

# Radiant's "filters" rock!

and turns it into

<h1>Radiant&#8217;s &#8220;filters&#8221; rock!</h1>

This patch uses Chris Neukirchen's RubyPants, which is a Ruby port of John Gruber's SmartyPants. I've included unit tests modeled on the existing ones for the Markdown and Textile filters.

The introduction of validations broke migrations where the validated columns do not exist. Adding in very simple model objects to the migrations allows them to use those models to create and manipulate objects.

It's now possible to do a rake migrate from an empty database.

(note that the there is an activerecord bug (http://dev.rubyonrails.org/ticket/5215) that causes the migrate to fail under sqlite).

As per some | Mailing List discussion, I've added in the ability to modify the published date - mainly to ease the ability to migrate data from an existing system / offline sources.

The published date is hidden away in the same section as the slug and breadcrumb, and has an "automatic" checkbox if the item has not yet been published.

It shouldn't be too hard to take this a step further and add in a 'publish later' status.

We're currently using RSS-aggregators on a community portal-page, pumping feeds from local and global sites (http://gentooguiden.dk). Would it possible to make some SimpleRSS (which I prefer over FeedTools?) tags? Another way is to include rhtml, so it could be done directly.

• Tag for RSS-source
• Subtags for outputs (title, description ..)
• Cache RSS for a period set (have yet to see this done in rails, I am using cron)

To reproduce:

1. Start a fresh Radiant install.
2. Add a child to the root page.
3. Add a grandchild (child of the child).
4. Add a great grandchild (GGC).
5. Click the +/- button of the grandchild repeatedly.

This makes the GGC node get cloned with each "- then +" click.

(screenshot of problem)

My opera:about page data:

Version	8.52 	
Build	1631 	
Platform	Linux 	
System	i686, 2.6.15-gentoo-r1 	
Qt library	3.3.4

Postgres does not seem to like doing change_column from integers to booleans, i had to do this:

def self.up

remove_column "users", "admin" add_column "users", "admin", :boolean, :default => false, :null => false remove_column "users", "developer" add_column "users", "developer", :boolean, :default => false, :null => false end

This ofcourse drops the information stored, so another method might be better.

This is an issue in migration: http://dev.radiantcms.org/radiant/browser/trunk/radiant/db/migrate/006_integer_columns_to_boolean.rb