kbingman / paperclipped

Radiant extension for managing assets and images with the Paperclip plugin — Read more

Sort by: Priority | Votes | Last Updated

Loading…

5.

5 votes

0.8.0 Branch - edit page conflicts experienced with multiple extensions present
3 comments Created 7 months ago by tricycle

Title

Body
We have an extension that gets run before the paperclipped extension which does the following during activation: admin.page.edit.add :form_bottom, "/preview/show", :after => 'edit_buttons' admin.page.edit.add :form_bottom, "/preview/preview_iframe", :after => 'edit_buttons' It appears that when the paperclipped extension is activated that it changes the edit page in paperclipped/lib/assets_admin_ui.rb line 32 which does: page.edit = Radiant::AdminUI::RegionSet.new do |edit| edit.main.concat %w{edit_header edit_form edit_popups } edit.form.concat %w{edit_title edit_extended_metadata edit_page_parts} edit.form_bottom.concat %w{edit_buttons} edit.parts_bottom.concat %w{edit_layout_and_type edit_timestamp} edit.asset_tabs.concat %w{attachment_tab upload_tab bucket_tab search_tab} edit.bucket_pane.concat %w{bucket_notes bucket bucket_bottom} edit.asset_panes.concat %w{page_attachments upload search} If the assignment to page.edit is commented out then we can observe that the preview button added by the first extension is present and works. Is it possible that the paperclipped extension is somehow overwriting the existing page.edit? Is there a way to do this without interfering with other extension (if indeed that is what's happening here?)
or cancel
We have an extension that gets run before the paperclipped extension which does the following during activation:
```
admin.page.edit.add :form_bottom, "/preview/show", :after => 'edit_buttons'
admin.page.edit.add :form_bottom, "/preview/preview_iframe", :after => 'edit_buttons'
```
It appears that when the paperclipped extension is activated that it changes the edit page in paperclipped/lib/assets_admin_ui.rb line 32 which does:
```
        page.edit = Radiant::AdminUI::RegionSet.new do |edit|
          edit.main.concat %w{edit_header edit_form edit_popups }
          edit.form.concat %w{edit_title edit_extended_metadata edit_page_parts}
          edit.form_bottom.concat %w{edit_buttons}
          edit.parts_bottom.concat %w{edit_layout_and_type edit_timestamp}
          edit.asset_tabs.concat %w{attachment_tab upload_tab bucket_tab search_tab}
          edit.bucket_pane.concat %w{bucket_notes bucket bucket_bottom}
          edit.asset_panes.concat %w{page_attachments upload search}
```
If the assignment to page.edit is commented out then we can observe that the preview button added by the first extension is present and works. Is it possible that the paperclipped extension is somehow overwriting the existing page.edit? Is there a way to do this without interfering with other extension (if indeed that is what's happening here?)
Comments

kbingman Wed May 27 07:26:32 -0700 2009 | link

Can you let know which extension that is. The preview (with an iFrame) extension? I have used that successfully with 0.7.1 but have not tried it out with the newer version (which btw is not ready for primetime...!)

Keith

Comment
Can you let know which extension that is. The preview (with an iFrame) extension? I have used that successfully with 0.7.1 but have not tried it out with the newer version (which btw is _not_ ready for primetime...!) Keith
or cancel

jgoggles Thu May 28 01:16:17 -0700 2009 | link

I'm having the same problem with Paperclipped 0.7.1 - it seems it's conflicting with the featured_pages extension which does this during activation:

admin.page.edit.add :form, "featured_page_meta"

Comment
I'm having the same problem with Paperclipped 0.7.1 - it seems it's conflicting with the featured_pages extension which does this during activation: admin.page.edit.add :form, "featured_page_meta"
or cancel

kbingman Thu Jun 04 13:53:26 -0700 2009 | link

this should now be fixed

Comment
this should now be fixed
or cancel

Parsed with GitHub Flavored Markdown
4.

2 votes

0.8.0 Branch - missing assets bucket when creating new page
1 comment Created 7 months ago by tricycle

Title

Body
When adding a new page the asset button is missing. However for the edit page the asset button is present.
or cancel

When adding a new page the asset button is missing.

However for the edit page the asset button is present.

Comments

kbingman Wed May 27 07:29:24 -0700 2009 | link

This is not a bug, but a limitation... the assets cannot be attached until the page is created. Feel free to look into it, patches are always welcome, but for now you will need to save the page first.

Comment
This is not a bug, but a limitation... the assets cannot be attached until the page is created. Feel free to look into it, patches are always welcome, but for now you will need to save the page first.
or cancel

Parsed with GitHub Flavored Markdown
3.

0 votes

SQLException: no such table
2 comments Created 7 months ago by pipewriter

Title

Body
Hi Keith! When I try migrating - it used to work but now - I get the following: <pre><code> rake production db:migrate:extensions --trace (in /deploy/radiant) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke db:migrate:extensions (first_time) ** Invoke environment ** Execute db:migrate:extensions rake aborted! SQLite3::SQLException: no such table: extension_meta: SELECT schema_version FROM extension_meta WHERE name = 'Paperclipped' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:372:in `catch_schema_changes' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:275:in `select' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:61:in `select_all' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in `select_one' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in `select_value' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:42:in `initialize_extension_schema_migrations' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:25:in `initialize' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:373:in `new' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:373:in `up' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:356:in `migrate' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:7:in `migrate' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:12:in `migrate_extensions' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:11:in `each' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:11:in `migrate_extensions' /opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/tasks/extensions.rake:8 /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `execute' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `each' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `execute' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:578:in `invoke_with_call_chain' /opt/ree/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in `invoke_with_call_chain' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:564:in `invoke' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2027:in `invoke_task' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run' /opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31 /opt/ree/bin/rake:19:in `load' /opt/ree/bin/rake:19 </code></pre> Any idea? Greetings from Berlin by Benedikt
or cancel
Hi Keith!

When I try migrating - it used to work but now - I get the following:
```
rake production db:migrate:extensions --trace
(in /deploy/radiant)
** Invoke production (first_time)
** Execute production
** Invoke environment (first_time)
** Execute environment
** Invoke db:migrate:extensions (first_time)
** Invoke environment
** Execute db:migrate:extensions
rake aborted!
SQLite3::SQLException: no such table: extension_meta: SELECT schema_version FROM extension_meta WHERE name = 'Paperclipped'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:372:in `catch_schema_changes'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:275:in `select'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:61:in `select_all'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in `select_one'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in `select_value'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:42:in `initialize_extension_schema_migrations'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:25:in `initialize'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:373:in `new'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:373:in `up'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activerecord/lib/active_record/migration.rb:356:in `migrate'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:7:in `migrate'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:12:in `migrate_extensions'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:11:in `each'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/radiant/extension_migrator.rb:11:in `migrate_extensions'
/opt/ree/lib/ruby/gems/1.8/gems/radiant-0.7.1/lib/tasks/extensions.rake:8
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `call'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `execute'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `each'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `execute'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:578:in `invoke_with_call_chain'
/opt/ree/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in `invoke_with_call_chain'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:564:in `invoke'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2027:in `invoke_task'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run'
/opt/ree/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31
/opt/ree/bin/rake:19:in `load'
/opt/ree/bin/rake:19
```
Any idea?

Greetings from Berlin by
Benedikt
Comments

kbingman Wed May 27 07:30:21 -0700 2009 | link

Hmm. weird. That is the old table from pre 0.7 radiant. which version of radiant are you using?

Comment
Hmm. weird. That is the old table from pre 0.7 radiant. which version of radiant are you using?
or cancel

pipewriter Wed May 27 07:41:21 -0700 2009 | link

Hi Keith,

Radiant 0.7.1 - the biggest problem is that extension migration is impossible now ... any idea?

Thanx and greetings from Berlin

Bene

Comment
Hi Keith, Radiant 0.7.1 - the biggest problem is that extension migration is impossible now ... any idea? Thanx and greetings from Berlin Bene
or cancel

Parsed with GitHub Flavored Markdown
2.

0 votes

template_name method undefined
2 comments Created 8 months ago by halan

Title

Body
I have this problem since e20a79d0 in this file http://github.com/kbingman/paperclipped/tree/e20a79d0ccbd289b7e3fc38695952215ad29c469/app/views/assets/index.html.haml I return to before it, and just work. The problem is with the regions.
or cancel

I have this problem since e20a79d0 in this file http://github.com/kbingman/paperclipped/tree/e20a79d0ccbd289b7e3fc38695952215ad29c469/app/views/assets/index.html.haml

I return to before it, and just work. The problem is with the regions.

Comments

kbingman Sun May 10 15:11:43 -0700 2009 | link

This is a known problem. at the moment it does not work with edge, but I am in the process of refactoring the regions. it should work with edge soon.

Comment
This is a known problem. at the moment it does not work with edge, but I am in the process of refactoring the regions. it should work with edge soon.
or cancel

kbingman Wed May 27 07:31:13 -0700 2009 | link

The 0.8.0 version should work with the current 0.8.0 RC1 gem. Let me know if it doesn't

Comment
The 0.8.0 version should work with the current 0.8.0 RC1 gem. Let me know if it doesn't
or cancel

Parsed with GitHub Flavored Markdown

Labels

kbingman / paperclipped

Pledgie Donations

0.8.0 Branch - edit page conflicts experienced with multiple extensions present

Comments

0.8.0 Branch - missing assets bucket when creating new page

Comments

SQLException: no such table

Comments

template_name method undefined

Comments