I’ve just added the over eager Mark Dagget to the Mephisto Core Team. He’s the author the open source project RAM (Ruby Asset Manager), as well as Pledgie. His main task is keep Mephisto on life support, starting with adding his unreleased but excellent Exception Notifier plugin.
Categories
Community
- Mephisto Google Group
- Theme Gallery [0]
- Theme Gallery [1]
- Step by Step Tutorial
- Wiki
- Say hi in #mephisto on irc.freenode.net
About Mephisto
Mephisto was baked to golden perfection by Rick Olson(Development) and Justin Palmer(UI/Design) with contributions from a bunch of cool people.
Excellent, welcome Mark! I hope you can keep Mephisto afloat. I’m looking forward to seeing it develop in the near future. Still using it as my blog engine and still loving it.
Fantastic! Wonderful! Welcome Mark!
It’s about time you posted an update on the mephisto blog.
WOOT! – How exciting – My feed reader said the Mephisto Blog Blog was updated :-)
Its great to hear that Mephisto is going to get another serge of activity – here’s hoping it continues longer term.
Congratulations to Mark Dagget!
Alex.
Finally! Mephisto is too good to be let to die! Congrats and thank God!
Excellent news! Welcome Mark. I’m looking forward to the progress.
Also excited to see this. Mephisto is fantastic!
Anyone know what happened to railsweenie.com ?
I am sorry to ask this at this point, but i don’ t have a google account to access the mephisto mailinglist and as a ASU member it is absolutely impossible for me to create a google account. Also i couldn’ t find a email on this website. This is what i mailed to the google group which looked to me at the first spot beeing a open group:
I am sick from setting up Mephisto on Debian Testing and Apache 2. I use the svn version. Needed nearly 4h to get it working. Setting up ruby server stuff is definetly for idiots or for people with much time. Sorry this is my conlusion after setting up 4 different blog softwares developed with ruby. Only Sam Ruby’s blog (which was highly experimental) was done in under 15 minutes and is the fastes blog software i have ever tested.
Today I red through 8 or 9 different Mephisto howtos. All are different. One of my big unanswered questions is: Do i use Apache, Wnrick or Mongrels as server platform, sorry, but i couldn’ t find a answer. Not even on the developers site. Nobody answers this question. In four or five of the howtos there is mentioned a .htaccess file. But i couldn’ t find this file in the public folder.
Coming to the point, i can’ t access the admin section. Get this error:
Processing OverviewController#index (for 192.168.4.2 at 2007-09-10 19:39:02) [GET] Session ID: 147b3f63f94884ed457ae6ef00db7cd7 Parameters: {“action”=>”index”, “controller”=>”admin/overview”}
NoMethodError (undefined method `extract_options!’ for #):
/vendor/plugins/acts_as_paranoid/lib/caboose/acts/paranoid.rb:75:in `find_with_deleted’ /app/models/user.rb:45:in `find_by_site_with_deleted’ /app/models/user.rb:41:in `find_by_site’
/vendor/rails/activerecord/lib/active_record/base.rb:946:in `with_scope’
/vendor/plugins/acts_as_paranoid/lib/caboose/acts/paranoid.rb:109:in `with_deleted_scope’ /app/models/user.rb:41:in `find_by_site’ /lib/authenticated_system.rb:9:in `current_user’ /lib/authenticated_system.rb:4:in `logged_in?’ /lib/authenticated_system.rb:25:in `login_required’
/vendor/rails/actionpack/lib/action_controller/filters.rb:456:in `send’
/vendor/rails/actionpack/lib/action_controller/filters.rb:456:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:435:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:637:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:438:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:637:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:438:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:637:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:438:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:637:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:449:in `call’
/vendor/rails/actionpack/lib/action_controller/filters.rb:637:in `call_filter’
/vendor/rails/actionpack/lib/action_controller/filters.rb:619:in `perform_action_without_benchmark’
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue’ /usr/lib/ruby/1.8/benchmark.rb:293:in `measure’
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue’
/vendor/rails/actionpack/lib/action_controller/rescue.rb:83:in `perform_action’
/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `send’
/vendor/rails/actionpack/lib/action_controller/base.rb:430:in `process_without_filters’
/vendor/rails/actionpack/lib/action_controller/filters.rb:624:in `process_without_session_management_support’
/vendor/rails/actionpack/lib/action_controller/session_management.rb:114:in `process’
/vendor/rails/actionpack/lib/action_controller/base.rb:330:in `process’ /vendor/rails/railties/lib/dispatcher.rb:41:in `dispatch’ /vendor/rails/railties/lib/fcgi_handler.rb:168:in `process_request’ /vendor/rails/railties/lib/fcgi_handler.rb:143:in `process_each_request!’ /vendor/rails/railties/lib/fcgi_handler.rb:109:in `with_signal_handler’ /vendor/rails/railties/lib/fcgi_handler.rb:142:in `process_each_request!’ /usr/lib/ruby/1.8/fcgi.rb:612:in `each_cgi’ /usr/lib/ruby/1.8/fcgi.rb:609:in `each’ /usr/lib/ruby/1.8/fcgi.rb:609:in `each_cgi’ /vendor/rails/railties/lib/fcgi_handler.rb:141:in `process_each_request!’ /vendor/rails/railties/lib/fcgi_handler.rb:55:in `process!’ /vendor/rails/railties/lib/fcgi_handler.rb:25:in `process!’ /var/www/mephisto/htdocs/public/dispatch.fcgi:24
Rendering /var/www/mephisto/htdocs/public/../config/../public/500.html (internal_server_error)
Via google i found this entry
http://groups.google.com/group/MephistoBlog/browse_thread/thread/9d15304b451916ad
but this seems to be fixed.
Who can help with my problem?
This makes me wondering! Is nobody testing mephisto anymore or is it a dead project? Or i am stupid?
Again, i am sorry for asking this at this point! Dieter
Induced coma…./\.../\.../\.../\.................. flat line
mephisto blog is great and want to live… Good luck guys
@Dieter Zinke:
The problem you are having is due to mismatches between Mephisto edge and Rails edge. The following variation of something I found on the Mephisto Blog Google Group worked for me:
$ cd appDirectory $ rake rails:freeze:edge REVISION=7472 $ ./script/plugin install http://dev.rubyonrails.org/svn/rails/plugins/acts_as_list/ $ rake db:bootstrap RAILS_ENV=production $ .script/server
I now have Mephisto Edge working with Rails edge Rev 7472. Apparently the latest Mephisto and Rails edge builds don’t play nice; but Mephisto edge and Rails edge Rev 7472 do.
Welcome Mark!! I just spent several hours getting Mephisto working on my Slicehost VPS and I am looking forward to getting years of use out of this promising application.
My vote for something to put atop the priority list is fixing the Theme Import problem. I am experiencing this with every theme I try to add to my stock install. All themes are from Mephisto Themes Gallery so they should by structurally sound. However, with each import I get the following error:
“Invalid theme uploaded: [ThemeError] No such file or directory – templates”
I have searched for hours but found no answer; however, I did find countless others with this problem. This has to be the most prevalent and pervasive Mephisto problem since it is encountered when performing such a basic function.
Welcome aboard Mark, and please help!