http://blog.gmane.org/gmane.comp.web.typo.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.web.typo.user/4665 _______________________________________________ Typo-list mailing list Typo-list< at >rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list Chet Farmer 2008-09-05T18:25:48 http://comments.gmane.org/gmane.comp.web.typo.user/4662 I am trying to run rspec for the latest release of Typo and am running into a lot of errors (which could be self-inflicted). So before I dive too deep into this, should we expect Typo 5.1.3 to pass all the tests? And by the way, what is the current test coverage number from rcov? Thanks, Pat. Pat Cappelaere 2008-09-03T12:19:29 http://comments.gmane.org/gmane.comp.web.typo.user/4661 Hello list, I've just released Typo 5.1.3, which is the fourth release of the "Cartier-Bresson" series and released on sunday August the 31th. It is mostly a bugfix and behaviour fix version, so don't expect many visible changes, except for people having problems with the closed bugs (thank you Captain Obvious). Typo 5.1.3 is avaliable as a gem with installer or sources. Following some discussion here, I've removed the database dependencies from the Typo installer. We now assume that you have the bindings for any supported databases and won't force you to install them anymore. Complete CHANGELOG here: Bug #1244: error with postgresql database on admin/content Bug #1251: Documentation on dashboard is 404 Bug #1252: migrations alter updated_at timestamps of articles and comments, affects RSS feeds Bug #1253: Twice redirect in admin/user#list if no admin Bug #1254: Fix little error when you use bad id in AdminUser#edit Bug #1255: Doesn't autosave if no define title Bug #1256: /article/ 301 redirect hits the default buffer which is not the expected behaviour Bug #1257: Articles redirect doesn't work with non-nil relative_url_root Rev #1784: Fixed requirements and added our official Typo mascot Rev #1786: Fixes a stupid behaviour that forces tags display name to be the same as the name in the url. IE : "web 2.0" would display on a page as web2-0 after transformation, which is stupid. Adds a migration that changes '.' into '-' in tag already in the database. Otherwise, it makes typo crash when accessing that tag. Allows edition of tag display name in the admin. Rev #1787:Removes database dependencies from installer. Now we assume you already have MySQL, PgSQL or SQLLite adater installed. Deletes 2 themes from FCKEditor, about 300k lighter now. Suppress caching from development environment Rev #1789: Fixes a stupid bug that allows a non administrative user to change his profile Rev #1792: Removing tmcode textfilter. It now has its own life at http://svn.typosphere.org/plugins/typo_textfilter_tmcode/ . Removing amazon textfilter. It now has its own life at http://svn.typosphere.org/plugins/typo_textfilter_amazon/ . Removing sparkline textfilter. It now has its own life at http://svn.typosphere.org/plugins/typo_textfilter_sparkline/ Rev #1795: Fixes 2 nasty bugs with autosave. The first one broke autosave when no title was set. We now set a default title. The second one was overriding permalink with a void string when post was autosaved because the permalink field was empty after autosave. For autosave: If no title is given, Typo gives it a title like "Article Draft + post_id". When publishing, every article-draft-something permalink is just replaced with the article title crafted permalink. Rev #1796: Enables in admin database migration back, gets rid of the old pre 4.1 general controller, sets the CHANGELOG for 5.1.3. Many thanks to Cyril Mougel, Matijs van Zuijlen and Frédéric Logier for submitting patches. Cheers, Frédéric de Villamil Frédéric 2008-08-31T15:56:21 http://comments.gmane.org/gmane.comp.web.typo.user/4660 Hello everybody, I search about it, but found nothing. How we can change url rules to make blog post url format like "http://myblog.tld/my-post-title" instead of "http://myblog.tld/year/month/day/my-post-title" ? Thanks a lot -- Yannick Francois <yannick.francois< at >elsif.fr> yannick.francois< at >elsif.fr 2008-08-28T10:06:15 http://comments.gmane.org/gmane.comp.web.typo.user/4658 Installing Typo gem using JRuby gives: Arun Gupta 2008-08-27T00:46:45 http://comments.gmane.org/gmane.comp.web.typo.user/4657 _______________________________________________ Typo-list mailing list Typo-list< at >rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list Warner Onstine 2008-08-22T22:39:20 http://comments.gmane.org/gmane.comp.web.typo.user/4636 I've been scouring the code (Typo 5.1.2) and trying to find the intent for the accounts/signup feature (other that setting the first user as administrator). The default profile is set to "contributor" in user.rb model and I see how the profile.modules seem to work. However, whenever I test a new additional user "signup" I am presented with the login screen after I have successfully "signed up". Then, the login does not work, the system keeps rendering a new login screen and the new user is unable to do anything other than go back to the general typo blog viewer via the link "Back to Your Blog" (or whatever the link says at the bottom of the login screen. Is this the appropriate behavior or is this portion not yet finished? I want contributors to be able to submit "draft" articles so I can review and then use my administrator rights to edit and publish/approve their articles. Any help is greatly appreciated! Tim Tim Prentis 2008-08-09T20:41:55 http://comments.gmane.org/gmane.comp.web.typo.user/4626 _______________________________________________ Typo-list mailing list Typo-list< at >rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list Sanjay Bisht 2008-08-08T13:55:34 http://comments.gmane.org/gmane.comp.web.typo.user/4610 Hi folks, I've been running http://gridengine.info off of Typo for a while now, thanks for a nice package! Because my site tracks a particular open source software product I sometimes need to put version numbers into article tags for easy characterizing. Prior to the most recent Typo upgrade, tags like "6.3" did not work at all, something about Rails or Typo can't handle the "." character. Now running the latest Typo I see something odd ... Tags that use multiple "." characters get remapped to "-": 6.2.0 becomes a tag called "6-2-0" on Typo But a tag named "6.2" is left unmodified, with no funky rewriting. As a test that proves the issue I added tags for "6.2.0" and "6.2" to the following post: http://gridengine.info/2008/08/06/t-shirt-contest ... the "6.2.0" tag is handled via changing "." to "-" but the "6.2" tag is left unchanged and does not work. Is the use of "." chars in tags an issue with Rails in general or should I write up an Issue against the Typo issue tracker? -Chris Chris Dagdigian 2008-08-06T17:23:03 http://comments.gmane.org/gmane.comp.web.typo.user/4601 Does anyone have Typo running with a version of Ruby more recent than 1.8.6-p114? This version has known vulnerabilities, as reported here: http://www.ruby-lang.org/en/news/2008/06/20/arbitrary-code-execution-vulnerabilities/ I've tried with all the most recent versions of Ruby 1.8 -- 1.8.7-p22, 1.8.6-p230 and 1.8.5-p231 -- but these all seem to cause Typo to crash in one place or another (the crash with 1.8.7-p22 is documented as Issue 1243 [1]). I'm using Rails 2.0.2 and mysql gem 2.7. I'd really like to use Typo, but am reluctant to do so if it can only be run insecurely. [1] http://typosphere.org/projects/typo/issues Geoffrey Sisson 2008-08-05T00:25:50 http://comments.gmane.org/gmane.comp.web.typo.user/4599 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've been trying to get Typo's redmine to email me instructions for resetting the password for the trac account that got converted to a redmine account and now won't accept my password. Redmine obediently tells me it sent an email, but no email actually arrives. I tried registering again, but then redmine complains there's already a user with my email address. Any suggestions? Regards, Matijs. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFIlk8sh3TgaXYDPEERAt3mAJ4kaWBiRoaaQ76siQLmRgEzfTJ4EgCfXt2o kR3fC8+Wo0aqa10eFVEQ8eI= =9dem -----END PGP SIGNATURE----- Matijs van Zuijlen 2008-08-04T00:37:08 http://comments.gmane.org/gmane.comp.web.typo.user/4597 Before my upgrade, I could write an article in Textile and see it rendered in the automatically generated preview. That no longer appears to be the case, either with the rich or simple editors. How do I verify the formatting will be correct before posting with the Textile filter turned on? Thanks, Ben Ben Armstrong 2008-08-02T13:06:34 http://comments.gmane.org/gmane.comp.web.typo.user/4595 My typo site had not been updated in a while, but the host it runs on has undergone upgrades recently. Some time over the past month or two, suddenly I couldn't access vital admin areas (to write a post, review/confirm feedback, etc.) Being somewhat impatient, without investigating the cause of the errors, I upgraded in-place using svn update and rake db:migrate. Things seemed to go well. The blog itself looks fine, but I still can't access the same parts of the admin interface. Here's a sample error after upgrading. How do I proceed from here to get my blog functioning properly again? Processing ContentController#new (for 71.7.237.23 at 2008-08-01 09:14:07) [GET] Session ID: 001b43dc4ab82bfc495e757edeed72d3 Parameters: {"action"=>"new", "controller"=>"admin/content"} NoMethodError (undefined method `[]' for #<Enumerable::Enumerator:0x7f0bd90cb340>): /vendor/rails/activerecord/lib/../../activesupport/lib/active_support/core_ext/string/access.rb:53:in `last' /lib/stateful.rb:21:in `method_missing' (__DELEGATION__):2:in `__send__' (__DELEGATION__):2:in `published?' /app/models/article.rb:301:in `allow_comments=' /vendor/rails/activerecord/lib/../../activesupport/lib/active_support/core_ext/object/misc.rb:28:in `returning' /app/models/article.rb:299:in `allow_comments=' /app/controllers/admin/content_controller.rb:214:in `get_or_build_article' /vendor/rails/activerecord/lib/../../activesupport/lib/active_support/core_ext/object/misc.rb:28:in `returning' /app/controllers/admin/content_controller.rb:213:in `get_or_build_article' /app/controllers/admin/content_controller.rb:145:in `new_or_edit' /app/controllers/admin/content_controller.rb:55:in `new' /vendor/rails/actionpack/lib/action_controller/base.rb:1159:in `send' /vendor/rails/actionpack/lib/action_controller/base.rb:1159:in `perform_action_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:699:in `call_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:727:in `run_before_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:666:in `call' /vendor/rails/actionpack/lib/action_controller/filters.rb:666:in `proxy_before_and_after_filter' /vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call' /vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call' /vendor/rails/actionpack/lib/action_controller/filters.rb:724:in `run_before_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:697:in `call_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:691:in `perform_action_without_benchmark' /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /vendor/rails/actionpack/lib/action_controller/rescue.rb:199:in `perform_action_without_caching' /vendor/rails/actionpack/lib/action_controller/caching.rb:678:in `perform_action' /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache' /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache' /vendor/rails/actionpack/lib/action_controller/caching.rb:677:in `perform_action' /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send' /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:687:in `process_without_session_management_support' /vendor/rails/actionpack/lib/action_controller/session_management.rb:123:in `process' /vendor/rails/actionpack/lib/action_controller/base.rb:388:in `process' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:171:in `handle_request' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:115:in `dispatch' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi' /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in `dispatch' /vendor/rails/railties/lib/fcgi_handler.rb:101:in `process_request' /vendor/rails/railties/lib/fcgi_handler.rb:149:in `with_signal_handler' /vendor/rails/railties/lib/fcgi_handler.rb:99:in `process_request' /vendor/rails/railties/lib/fcgi_handler.rb:77: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:76:in `process_each_request' /vendor/rails/railties/lib/fcgi_handler.rb:50:in `process!' /vendor/rails/railties/lib/fcgi_handler.rb:24:in `process!' /public/dispatch.fcgi:24 Rendering /var/www/vir/syn.theti.ca/typo/public/500.html (500 Internal Server Error) Thanks, Ben Ben Armstrong 2008-08-01T17:58:33 http://comments.gmane.org/gmane.comp.web.typo.user/4593 Hi, Until I can get the 5.1 series to run, I'm trying to retreat to 5.0.2, which had been working for me. I dropped my old db and removed the install directory, created new of each, installed using the gem/installer, stop mongrel, and get a clean restore of the database (at least no complaints) and I can see all of the data in both the yaml file and the database itself, but typo says, "No posts found..." on the blog's page and the admin interface agrees about no posts. Usernames, passwords, categories, files, all work. The only logged message is: Processing ArticlesController#index (for 172.16.134.244 at 2008-07-31 03:00:40) [GET] Session ID: 807e93eef31ec4b2fabcfcffe3c4f654 Parameters: {"action"=>"index", "controller"=>"articles"} Filter chain halted as [#<ActionController::Caching::ActionParams::ActionParamCacheFilter: 0xb69a8c2c < at >actions=[:index, :read, :show, :archives, :view_page]>] rendered_or_redirected. Filter chain halted as [#<ActionController::Filters::ClassMethods::ProcWithCallFilter: 0xb69a8a24 < at >filter=#<Proc:0xb6f28f80< at >/opt/typo/vendor/rails/ actionpack/lib/action_controller/filters.rb:657>>] did_not_yield. Completed in 0.00263 (379 reqs/sec) | Rendering: 0.00021 (7%) | DB: 0.00000 (0%) | 200 OK [http://example.com/bill/blog] Before I attempted an upgrade I remove the sidebar plug-ins. Any thoughts on how to convince typo that articles are there or where to look next? Thanks, -Bill ----- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 bill< at >bfccomputing.comCell: 603.252.2606 http://www.bfccomputing.com/ Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf For fastest support contact, please follow: http://bfccomputing.com/support_contact.html Bill McGonigle 2008-07-31T07:24:28 http://comments.gmane.org/gmane.comp.web.typo.user/4592 My environment is Rails 2.0.2, TYPO 5.1.1. running at RailsPlayground using the Victor Persson's Dirtylicious theme Can someone steer me in the correct direction? I can upload files/attachments and see them in the admin "manage uploads" feature. I can also associate uploads with articles when I edit articles(i.e. posts). The problem: I cannot figure out how to make these 'uploads' visible as attachments with the articles(i.e. posts) by simply using the TYPO administration features. Do I need to modify the default layout or one of the views? Any ideas are greatly appreciated. Tim Prentis 2008-07-30T18:11:33 http://comments.gmane.org/gmane.comp.web.typo.user/4590 Upgrading Typo with the instructions at http://typosphere.org/wiki/typo/Upgrade_Typo_with_Typo_installer and a ~/gems repository fails. Some stuff can deal with but this one defeats me. This is the error I get ..... Checking database Database exists, preparing for upgrade expanding apache13.conf.example template expanding apache20.conf.example template expanding lighttpd.conf.example template Migrating Typo's database to newest release /home/antonaylward/gems/gems/typo-5.1.2/bin/typo:59:in `migrate': Migration failed (RailsInstaller::InstallFailed) from /home/antonaylward/gems/gems/rails-app-installer-0.2.0/lib/rails-installer.rb:689:in `in_directory' from /home/antonaylward/gems/gems/typo-5.1.2/bin/typo:57:in `migrate' from /home/antonaylward/gems/gems/rails-app-installer-0.2.0/lib/rails-installer.rb:217:in `install_sequence' from /home/antonaylward/gems/gems/rails-app-installer-0.2.0/lib/rails-installer.rb:192:in `install' from /home/antonaylward/gems/gems/rails-app-installer-0.2.0/lib/rails-installer/commands.rb:95:in `command' from /home/antonaylward/gems/gems/rails-app-installer-0.2.0/lib/rails-installer.rb:646:in `execute_command' from /home/antonaylward/gems/gems/typo-5.1.2/bin/typo:93 from /home/antonaylward/gems/bin/typo:19:in `load' from /home/antonaylward/gems/bin/typo:19 A manual "rake db:migrate" completes OK. Anton J Aylward 2008-07-29T14:42:44 http://comments.gmane.org/gmane.comp.web.typo.user/4588 Good evening, I've just released a new Typo bugfix version for the 5.1 series. Unless something really critical appears, it will be the last release before the Rails 2.1 based 5.2 release, which will happen in september. There may be a few hours for the gem to propagate on the different mirrors. Here's a quick CHANGELOG – Fix a draft + autosave behavior bug: if I save an autosaved article as a draft, it is duplicated as the autosaved article id is not taken into account in the draft saving process. – Moves the autosave delay to 30 seconds to cut the server a little slack – Removes comments creation from protect_from_forgery to avoid crash with caches_page when adding comments – Fixes a bug with the contributor role tha prevents contributors to access anything in the admin – Adds draft deletion (useful heh ?) – Fixes the missing en_US.js file Cheers, Frédéric de Villamil Frédéric 2008-07-26T20:11:21 http://comments.gmane.org/gmane.comp.web.typo.user/4578 Hello, After a long time of development, Typo 5.1 "Cartier-Bresson" was released on monday July the 21th at around 8PM GMT and can be considered as a major Typo Version. It contains : ** Multiple users and roles. This point actually makes Typo 5.1 a major version. This release introduces 3 roles, coming along with various privileges : – Administrator, who owns full administrative and publishing power. – Publisher, who owns full publishing power on his own contents. – Contributors, who only have the right to login and edit their profile. There is now an option to allow new users to register by themselves or not. If not, the administrator will just have to add them himself in the admin. ** Improved admin The admin has been heavily refactored to be lighter, easier to use, and offer more capabilities. – You can now save your posts as drafts. Drafts now appear in a separate area of your administration to separarte them from offline posts. – New editing interface. – Tag autocompletion. – A new dashboard that makes daily administration easier. – Save as draft capabilities – Autosave capabilities (only with simple visual editor) – Revamped UI – Many more... ** New default theme After leaving the too much long used Azure theme for some templates found on open source design websites, we realized Typo needed a new default theme. We asked O2Source a French web Agency involved in many free and open source templates, and they came up with Typographic. We wanted something new, far from the classic white and blue fixed width wordpressish thing, something with its own personnality, that would take the whole screen and adapt many resolutions, and we've been quite delighted with what Hélène produced. ** Come back of the gem and the installer After fixing numerous bugs happening with Typo installed through our installer, we were able to provide the gem again, making Typo installation easier than ever. MySQL is now the default database and SQLITE dependency has been removed. ** Lots of code improvement and refactoring The code have been improved and refactored, maing Typo lighter than ever. This is a guarantee of less errors. ** New migrators We've included new migrators, allowing easy import from Wordpress and Dotclear 1.2 and 2. Typepad and Textpattern may follow soon. ** New site with up to date documentation The bugtracker has been moved from Trac to Redmine, so has the documentation, which has been rewriten in many ways. Access to the doc has also been made easier by merging redmine.typosphere.org with trac.typosphere.org. Lots of bugfixes, too much to say here. de Villamil Frédéric 2008-07-21T18:13:40 http://comments.gmane.org/gmane.comp.web.typo.user/4576 _______________________________________________ Typo-list mailing list Typo-list< at >rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list Anirudha Jadhav 2008-07-18T20:52:48 http://comments.gmane.org/gmane.comp.web.typo.user/4572 _______________________________________________ Typo-list mailing list Typo-list< at >rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list joy ride 2008-07-18T04:13:21 http://comments.gmane.org/gmane.comp.web.typo.user/4560 is there anyway to write a ruby page that uses the selected sidebars/theme in typo ? Lin Wj 2008-07-17T04:52:25 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.typo.user