Mephisto uses a lot of gems currently, but packages up the current versions in vendor to make installation easier. There are only two gems that aren’t included; RMagick, and TZInfo. RMagick is a pain to install, but not actually required for Mephisto to operate. TZInfo, however, is required. I didn’t include it because it seemed like a rather large gem. But don’t despair, Mephisto has a simple way to freeze gems.
# local copy
gem install tzinfo
# saves to vendor/tzinfo-0.2.2
rake gems:freeze GEM=tzinfoNow, upload this directory to your server and restart. If you’re using capistrano, you’ll need to throw it in shared and write some after_update_code task to copy it over. I’ll detail this more in a future Tips post.
‘users’ tab is broken in Admin. Where do I file bugs?
Mailing list, comment forms, etc (for now). What’s broken about the user’s tab?
I don’t know what Sam’s problem is, but for me, if you make any changes they are saved correctly, but when you go back to the Users tab, it automatically loads the defaults instead. For example, I changed my admin name to Gwyn. Login with that username works, articles display the correct author, etc., but if I load the Users tab, ‘admin’ is in the text box.
This is nowhere near ready for release by the looks of it. Follow the instructions exactly, and you get as far as clicking on the account link to get:
NoMethodError in Admin/users#show
Showing app/views/admin/users/_form.rhtml where line #8 raised:
undefined method `default_filters’ for FilteredColumn:Module Extracted source (around line #8):
5:
Application Trace | Framework Trace | Full Trace app/models/resource.rb:3 app/models/theme.rb:3:in `find_theme_files’ app/controllers/admin/base_controller.rb:7:in `find_templates_and_resources’ This error occurred while loading the following files: script/../config/../app/models/resource.rb
So, I think there’s a bit of work to be done before this goes prime-time. It has potential, but I think you need to write up a few tests to check releases before throwing them out to the World otherwise you’re just going to get lots more bug tickets. Where do we go to open bug tickets by the way?
I would offer patches, but I can’t see why there is a problem with a superclass mismatch, and I don’t know what your default_filters code is supposed to look like…
Will keep an eye on the blog, and once you’ve got the basics ironed out, I’ll be happy to jump on board and see if I can help bash a few more bugs for you…
I’ve worked out the problem people are seeing with the ‘default_filters’ message and occasionally the weird superclass mismatch on Resource
You should make sure that rails is frozen to 4727:
rake rails:freeze:edge REVISION=4727
I got a problem when I missed out the second I in REVISION and therefore it defaulted to the latest edge version which breaks lots of things.
Sorry about that edge weirdness. The new auto class loading code was committed to Rails last night, and it’s causing some weird issues in some of my plugins. 4727 is safe until it’s all sorted out.