similar to: i18n routes and resource names problem

Hello i have an domain in .рф (РФ is the first TLD, where domain names are put in Cyrillic script only.) (see also http://teimos.ru/x/punycode/) i''m trying to get working routes in cyrillic like http://теймос.рф/привет (XN--E1AIJIPB.XN--P1AI/XN--B1AGH1AFP) to welcome#index (for example) i tryed different ways but no luck with them all... in Gemfile ---------------\ gem

Hi, when trying to migrate Signal to Rails 3 I tried to use the shorthand route for: match ''/projects/status(.:format)'' but it thrown an error because the controller was not specified. This happend because actually the shorthand routes only work with routes without optional parameters. The modification to support routes ending with a optional parameters is very simple, as can

SUMMARY: -------- I tried to identify the general and root causes for these problems with 1.9, by taking into account non-utf encoding, current patches, comments and ideas. I used ticket #2188 as base for explanations. This is a long read. I wanted to include all the relevant information in one place. I also included information about related tickets in LH and their status. I decided that adding

On Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote: > Anything interesting in the logs? > > sudo journalctl -xf _SYSTEMD_UNIT=crond.service Don't know. [root at kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service -- Logs begin at ?ro 2015-12-02 22:34:16 CET. -- kwi 22 23:11:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:13:01

Hi all, While reworking my application from Rails 2.3 to 3.0beta I found a small bug in route naming. When nesting singular routes it doesn''t prefix the nested resource with the first resource in naming. I did some debugging and came up with a patch: https://rails.lighthouseapp.com/projects/8994/tickets/3911-naming-problem-in-nested-singular-resource#ticket-3911-2 regards, Jan De

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.

On 23 April 2016 at 10:25, Marcin Trendota <moonwolf.rh at gmail.com> wrote: > Anything interesting in the logs? > > > > sudo journalctl -xf _SYSTEMD_UNIT=crond.service > > Don't know. > > [root at kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service > ?...? > (/etc/cron.d/osticket-cron) > kwi 22 23:28:01 vz471 crond[30534]: (*system*)

hi, i using rails 2.3.8, i have setting this on my view: <%=h l(@banner.expire, :format => :long) %> (when "@banner.expire" is a Date ) and this on the my localized yml locale: date: formats: long: "%d %B %Y" but wheel i load the page, i have this error: I18n::MissingInterpolationArgument in Admin/banners#show missing interpolation

I''ve submitted a couple of patches in Ligththouse. Provide NoStore implementation of ActiveSupport::Cache::Store This patch provides a NoStore implementation of ActiveSupport::Cache::Store suitable for use in development and test environments where the code need to use the cache interface, but actually caching data is not desired.

Hi, I am new to ROR and this group. I would like to install a ROR environment able to generate full localized applications, always in the same language (Italian for example), without having to edit by hand all templates, scaffolded HTML and standard error messages. I searched Internet and this group, but I was no able to get information about. Is there a way to do that ? Thanks Nellinux

The way Rails handles root nodes in JSON and XML serialization is inconsistent. This has been discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/2584-232-activeresource-json-doesnt-send-parameters-with-root-node This seems mostly taken care of with ActiveModel::Base.include_root_in_json, especially if/when it ends up in ActiveResource. However, there is also the issue of how

The jist: by avoiding "MyApp::Application" in config/routes.rb generator template, those generated config/routes.rb work out-of-box when turning the app into an engine. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4400-patch-avoid-app_const-when-drawing-routes-in-app-generator Thanks! --phil-- -- You received this message because you are subscribed to the

In my work with a simple localization plugin, i''m running into a lot of places in the Rails core, where text and other localization specific information is hardcoded. I''ve included some examples in the bottom of this post. It''s hard for an outsider to know, if the hardcoded values are a result of inconsistency in code, or "by design". I hope that we can have

ActiveRecord validation messages are currently not I18N-friendly. Specifically, I''m referring to the fact that it enforces a certain grammar, namely the beginning of the message must consist of the field name. For example: validates_presence_of :name, :message => "can''t be blank." ...generates the message "Name can''t be blank". This grammar

I just upgraded to 2.1 and attempted to log in to my application and when this line is reached in my login action: redirect_to(index_url) I get the error "wrong number of arguments (0 for 1)" [stack trace below]. Here''s my route: map.index ''index'', :controller => ''e_simply'', :action => ''index'' I found

ZOMG HAPPY TUESDAY (UTC-7)!!! <3<3<3<3<3 I am happy to announce that the first release candidate for Rails 3.0.6 has been pushed to rubygems.org. ## Release Candidate: What does it mean? The release candidate is very similar to what we will actually release for version 3.0.6. The reason that we release an RC is so that the community can have a chance to postpone or veto commits

Hi, I noticed that 2 days ago that this ticket was marked "stale". https://rails.lighthouseapp.com/projects/8994/tickets/6171 But the issue is still here (I checked just now), and it reminded me I had a patch for it I forgot to submit, so I attached the patch file to the ticket. Since I''m still new on this, can someone please point me the right procedure ? Should I have

Hello! Could someone review the patch attached to [1] and provide feedback? Briefly, it targets rails 3, and fixes "rails g model admin/post". The generated migration creates a "admin_posts" table while the model expects a table simply named "posts". With the patch, the migration creates "posts". Thank you! --phil-- [1]

Can somebody please review my ticket: https://rails.lighthouseapp.com/projects/8994/tickets/4879 It''s a trivial bugfix ("option_groups_from_collection_for_select should produce an HTML-safe string") before RC, I think. Cheers, Wincent -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group,

I believe I have fixed the issue Trever noted with has_one (http://rails.lighthouseapp.com/projects/8994/tickets/64-eager-loading-inconsistency ) if people would like o have a look. Fred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to