cloverinteractive / cms Goto Github PK

We have some deprecation warnings in our logs we need to fix those

Travis should run specs and README should reflect the fact that we use rspec now.

We need to use attr_accessible or attr_protected in all models.

We are switching from test/unit to RSpec for more behavior oriented, self documenting and more readable tests.

We need to pass the rails_best_practices test.

Currently not possible because acl9 does not work with rails 3.1 and there is no work around yet. I have forked the project inside cloverinteractive however I was unable to run their tests, we need to:

• Figure out a way to run their tests to make our own fix that will work with rails 3.1 ( That should be a ticket in that project )
• Second option is wait until acl9 reaches that point (which might take some time therefore making it an undesirable solution)
• Talk to the guys involved in the project, figure how to contribute, and migrate the app to rails 3.1

We have neglected acceptance test, we need to write some cukes for the dashboard side of the application.

We need to figure out why does our build fails with travis an fix it.

Aside of the README file this project has no documentation whatsoever, we need to start the wiki, current topics we should discuss:

• Deployment
• jRuby
• Creating themes
• Extending the CMS

I believe we're not using that lib anyways, but we must check.

Started GET "/javascripts/fancybox/jquery.fancybox-1.3.1.js" for 127.0.0.1 at Wed Sep 07 10:32:25 -0700 2011

ActionController::RoutingError (No route matches "/javascripts/fancybox/jquery.fancybox-1.3.1.js"):

Implement layout designed by Diego Negrete

We need to move to the latest 3.0.x

We are not testing javascript, lets add Jasmine to the mix

Even though the dashboard theme look familiar to us, we need to improve it for anyone else outside of cloverinteractive to understand what the interface is actually for.

• Look at the clovercms-dashboard gem.
• We could take some ideas (and hopefully provide some) to the rails_admin project.

ie. lets be nice to the users :)

When I start bundle install. It is returning this error

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb 

Gem files will remain installed in /var/lib/gems/1.9.1/gems/capybara-webkit-0.12.1 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/capybara-webkit-0.12.1/./gem_make.out
An error occurred while installing capybara-webkit (0.12.1), and Bundler cannot continue.
Make sure that gem install capybara-webkit -v '0.12.1' succeeds before bundling.

It's probably a good idea to include the output of Jasmine specs along with all our other tests, so there is no need to run two test suites every time we want to make sure something didn't break.

We use assets (uploads) to render pages with photos (for now, possibly other type of content in the future), but we currently do not provide the possibility to delete already uploaded assets, plus we depend on flash to do the upload, we need to improve this by:

• Use backbone.js to create a nicer interface that will allow us to add/delete
• Try uploading files using an iframe instead of flash (not-key but would definitely remove the CMS dependency on flash in 100%)
• Abstract the asset's and have different type of objects inherit from them like (photo, video, etc) and create a polymorphic association on asset to relate it to other objects like (page), etc.
• If possible put the whole asset functionality in an external page.